[FIX] How to fix startup crash

[WickedManXD]

For a pretty version of the following text please visit the following Steam Guide:
http://steamcommunity.com/sharedfiles/filedetails/?id=631856742


If you suffer from the following two error messages at startup (or a general black screen followed by a message "Game has crashed"):
---------------------------
NXSys2DApp::CDDDisplay::l_DoesInitDDrawErrorOccure

Directdraw init failed (001)
---------------------------

---------------------------
NXSysMisc: DirectDraw error occured at D:\Dev\Projects\FunaticsOld\ProjectD\BaseLibs\XSystem\X2DApp\X2DDDDisplay.cpp - 586: <DDERR_UNSUPPORTED>
---------------------------

Then try the following:
Go to your Steamfolder (usually C:\Program Files (x86)\Steam\) and rename the following files:
GameOverlayRenderer.dll -> GameOverlayRenderer1.dll
GameOverlayRenderer64.dll -> GameOverlayRenderer641.dll
(Depending on your settings the .dll part might be invisible, just ignore it then)

After that try to run the game in Win XP 2 compatibility mode, go to your cultures folder (usually C:\Program Files (x86)\Steam\steamapps\common\Cultures 8th Wonder or C:\Program Files (x86)\Steam\steamapps\common\Cultures Northland), right click on the Game.exe and go the compatibility tab. Make a check in the first box and select "Windows XP (Service Pack 2)". Then click on ok and run the game.

If you still face problems try to create an opt_glob.ini file in your save folder (usually C:\Program Files (x86)\Steam\steamapps\common\Cultures 8th Wonder\Saves or C:\Program Files (x86)\Steam\steamapps\common\Cultures Northland\Saves) with the following content:
gfx_screen_width 1920
gfx_screen_height 1080
gfx_screen_depth 16

If you have an older monitor you might want to try those settings instead:
gfx_screen_width 1024
gfx_screen_height 768
gfx_screen_depth 16

If you have an even older monitor you might want to try the following:
gfx_screen_width 800
gfx_screen_height 600
gfx_screen_depth 16


As a side node: This will disable the Steam Overlay that is causing the problems. If you want to use it again (e.g. in other games) then you'll have to reverse the renaming.

[WickedManXD]

Originally posted by MKSKORP:

I have that game on GOG. But changing the resolution fixed the issue for me.
I had
gfx_screen_width 1920
gfx_screen_height 1200
gfx_screen_depth 32

before and just changed the high to 1080. I guess its because my older screen had a 1200 while my current one only has 1080.

Thanks for sharing Unsupported monitor resolutions is indeed a good point to look after

[Skybax]

I don't have any of these issues, mine says that Direct X7 is required to run this game.
Direct X7 does not run on Windows 10, and I've played this game for 6 hours already on this computer with no issues. So I'm not really sure what to do

[WickedManXD]

Originally posted by Skybax:

I don't have any of these issues, mine says that Direct X7 is required to run this game.
Direct X7 does not run on Windows 10, and I've played this game for 6 hours already on this computer with no issues. So I'm not really sure what to do

I think I ran into this too, did you actually try the compatibility mode/as administrator? I think that fixed it for me (but I'm so not sure - I wrote this guide ages ago).

It is indeed not possible to run DX 7 on Win 10. But I can confirm that I had the game running on Win 10 at some point.

[Grasshopper K]

Originally posted by Mike:

Originally posted by Skybax:

I don't have any of these issues, mine says that Direct X7 is required to run this game.
Direct X7 does not run on Windows 10, and I've played this game for 6 hours already on this computer with no issues. So I'm not really sure what to do

I think I ran into this too, did you actually try the compatibility mode/as administrator? I think that fixed it for me (but I'm so not sure - I wrote this guide ages ago).

It is indeed not possible to run DX 7 on Win 10. But I can confirm that I had the game running on Win 10 at some point.

Well... you hay have been using 32 bit EVERYwher I have looked in PAIN for the last 3 years... if you have 64 bit you have to use a virtual machine... I'm not paying for a buggy virtual machine just to play a 16bit game.... I have an anchient laptop that takes 10 mins to start vista... it has a sticker on it saying "brand new intel Centrino core inside". I have to have it plugged into the wall to use it at all, and remove the battery... I still have it for one single purpose.... to play all my cultures games and anything from DirectX7 or earlier :/

[Sluben1]

it isn´t worked for me. I have got windows 8

[Cozy Fawn]

This dopsent work I renamed the files and nothing. Change the mode to everything I could and nothing.


There is nothing in my save file so
"If you still face problems try to create an opt_glob.ini file in your save folder (usually C:\Program Files (x86)\Steam\steamapps\common\Cultures 8th Wonder\Saves or C:\Program Files (x86)\Steam\steamapps\common\Cultures Northland\Saves) with the following content:
gfx_screen_width 1920
gfx_screen_height 1080
gfx_screen_depth 16"

Means nothing to me. Guess I'll just kiss my money goodbay since it;s been 2 months since I bought these.

[Grasshopper K]

Look... As depressing as it is... WX 64 bit will NOT play it short of an OS emulator. Your (and my) options are, get an older laptop to use W7.
Microsoft simply don't care about supporting anything 16 bit on their 64 bit software.

[Elondrius]

Originally posted by Lego Grasshopper:

Look... As depressing as it is... WX 64 bit will NOT play it short of an OS emulator. Your (and my) options are, get an older laptop to use W7.
Microsoft simply don't care about supporting anything 16 bit on their 64 bit software.

That's interesting, because I play this game - and Northland - on a 64 bit Windows 10 machine. The only issue I had was the massive screen tears during scrolling, but enabling the morphological filtering in the Radeon settings solved that one, too.

[Grasshopper K]

Originally posted by Elondrius:

Originally posted by Lego Grasshopper:

Look... As depressing as it is... WX 64 bit will NOT play it short of an OS emulator. Your (and my) options are, get an older laptop to use W7.
Microsoft simply don't care about supporting anything 16 bit on their 64 bit software.

That's interesting, because I play this game - and Northland - on a 64 bit Windows 10 machine. The only issue I had was the massive screen tears during scrolling, but enabling the morphological filtering in the Radeon settings solved that one, too.

For the love of all that is Holy! Tell us your secrets!

[Grasshopper K]

Originally posted by Elondrius:

Originally posted by Lego Grasshopper:

Look... As depressing as it is... WX 64 bit will NOT play it short of an OS emulator. Your (and my) options are, get an older laptop to use W7.
Microsoft simply don't care about supporting anything 16 bit on their 64 bit software.

That's interesting, because I play this game - and Northland - on a 64 bit Windows 10 machine. The only issue I had was the massive screen tears during scrolling, but enabling the morphological filtering in the Radeon settings solved that one, too.

so it's been almost 18 months.... I take it you didn't get it to work, and have no advice...

[Adireael]

It does not work for Windows 8.1 or windows 10. Can steam make an update to solve this for these windows? It is just annoying that you paid for these two games and you can't run them. And nowadays is quite impossible to have windows XP or 7 in a computer... And virtual box just have lots of bugs also...

[Grasshopper K]

Originally posted by Adireael:

It does not work for Windows 8.1 or windows 10. Can steam make an update to solve this for these windows? It is just annoying that you paid for these two games and you can't run them. And nowadays is quite impossible to have windows XP or 7 in a computer... And virtual box just have lots of bugs also...

Head to this thread, I gave a small instructions on how I managed to get Windows 10 x64 with a large screen to finally operate All the 4 main Cultures games (One, Gates of Asgard, Northland, and 8th Wonder)

https://steamcommunity.com/profiles/76561198090549919/posthistory/

[Adireael]

Originally posted by Lego Grasshopper:

Originally posted by Adireael:

It does not work for Windows 8.1 or windows 10. Can steam make an update to solve this for these windows? It is just annoying that you paid for these two games and you can't run them. And nowadays is quite impossible to have windows XP or 7 in a computer... And virtual box just have lots of bugs also...

Head to this thread, I gave a small instructions on how I managed to get Windows 10 x64 with a large screen to finally operate All the 4 main Cultures games (One, Gates of Asgard, Northland, and 8th Wonder)

https://steamcommunity.com/profiles/76561198090549919/posthistory/

I will give it a try, thank you.

[ESound]

NXBasics::CFile::Read

file currentusermap\map.cif - errno 2: No such file or directory

(press Cancel to debug)

[hereandnowlive]

Hey so I fixed the major crash for my end beyond what the recommended fixes are. So what I am trying to say is that if you are on Windows 10 and you have created the opt_glob.ini file with the following resolutions:

gfx_screen_width 1920
gfx_screen_height 1080
gfx_screen_depth 16

and you changed your compatibility settings to xp service pack 2 and you still have a failure on start this fix should do the trick.

It all has to do with the intro video seemingly not loading correctly on windows 10. If you disable the intro video, you shouldn't have anymore issues getting to the main menu and from there I played the tutorial a bit and had no problems.

To do this you will need to access where the intro video is. This is likely going to be in the:

C:\Program Files (x86)\Steam\steamapps\common\Cultures 8th Wonder\DataX\FMV\Eng folder

In that folder you will see a file called intro.mpg. Now you will need to rename that file to literally anything else. In my case I just named it intro-true.mpg, and it should work. Unfortunately you will not have the intro when you start the game again but the game itself should work now.

Note that there is another file called Seq_0000.mpg as well. I think that's the victory cinematic which likely will crash the game as well if you beat it as a fyi. What you do on that is up to you since you might want to even just listen to the ending sequence as a reward when you finish the game rather then it just jerking to main menu, but it's up to you. It should be the exact same process to fix it if you want stability over some semblance of reward at the end of the game.