It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Tormentfan: I do appreciate you taking time with these issues, thank you very much for attempting to remedy this, but it's a pity you and thos ike you, instead of GOG, afterall they are the ones who have been paid for this and haven't seen fit to even comment on the broken nature of their newest release.
avatar
timeslip: Hehe. Actually, patch.dll is my code, and already contains fixes for the ai.dll crash I knew about. (For a bit of fun, there's a hidden config option you can turn on that makes it beep at you every time it prevents a crash. I normally get one or two each time I run from side to side of the madrigul town square.) If there's more crashes, it's partially my fault for missing them the first time round. You can't blame GOG for everything. :p (And since it is my code, I'm damn well going to try and fix it.)
That's a lot of unexpected info and you've broke my brain. :oO

So where do you fit in? Are you freelance for GOG.. part of the original design team.. or just a very smart cookie, who's coding work gets picked up by the corporates??
avatar
Tormentfan: That's a lot of unexpected info and you've broke my brain. :oO
Careful; you need that. :p

avatar
Tormentfan: So where do you fit in? Are you freelance for GOG.. part of the original design team.. or just a very smart cookie, who's coding work gets picked up by the corporates??
I have some code I've written that apparently doesn't do what it's supposed to do for some people, so now I want to find out why and if possible fix it. That's all.
Post edited February 20, 2012 by timeslip
Why publish a game that crashes constantly?
The game kept on crashing on my Windows 7 64bit rig. The error message was Bex error on SoubringVCnoeax. Through some web search, I found that Bex error is sometimes related to Data Execution Prevention in Windows 7. I tried add SoudbringeVC and SoulbringVCnoeax to the list for 'Turn on DEP for all programs and services except thous I select' in Data Execution Prevention menu. To my surprise, this fixed the problem immediately. The game is running smoothly without any problems so far. You can go to DEP menu from Advanced system settings in System.
Yeah, been having crashing problems as well. Have one that is consistent, early on in game.


:spoiler:


When you got your uncles house, there is a spot where badnits can ambush you. I bypassed them, went to uncles house, slept. When I go to the bandit camp where they were before, nothings there. I open the chest nearby and few seconds later it crashes. Consistently occurs at the exact same time in the exact same sequence.
avatar
kotokimura: The game kept on crashing on my Windows 7 64bit rig. The error message was Bex error on SoubringVCnoeax. Through some web search, I found that Bex error is sometimes related to Data Execution Prevention in Windows 7. I tried add SoudbringeVC and SoulbringVCnoeax to the list for 'Turn on DEP for all programs and services except thous I select' in Data Execution Prevention menu. To my surprise, this fixed the problem immediately. The game is running smoothly without any problems so far. You can go to DEP menu from Advanced system settings in System.
How far are you into it? Current quest?

avatar
PanzerLoco: Why publish a game that crashes constantly?
I'm pretty sure it wouldn't have crashed as it does now when it was first released on the OS it was designed for.
Post edited February 28, 2012 by Tormentfan
I haven't played Soulbringer yet, but I did a bit of research regarding the crashes and found something interesting about a retail version of the game.

Apparently, some user fixed his problems on Windows VIsta by choosing DirectX 6 in the game setup instead of DirectX 7. It seems that DX7 T&L causes crashes in some maps, including Madrigal Town Center. I don't know if DirectX 6 can be selected in Gog's version, but if it's possible, I think it's worth a try.

Here is the full post.
avatar
yavornn: I haven't played Soulbringer yet, but I did a bit of research regarding the crashes and found something interesting about a retail version of the game.

Apparently, some user fixed his problems on Windows VIsta by choosing DirectX 6 in the game setup instead of DirectX 7. It seems that DX7 T&L causes crashes in some maps, including Madrigal Town Center. I don't know if DirectX 6 can be selected in Gog's version, but if it's possible, I think it's worth a try.

Here is the full post.
Most, if not all, of us are already using the Noeax.exe so there doesn't seem much more that can't be done by the end user from that standpoint, as for installing it 'as' DX6.. I've no idea how one would go about doing that.
There should be a launcher window before you start the game, and in that launcher you should click on video options, and select DX6 if available. If you don't have that launcher, you can go to the game's folder and look for that launcher .exe file. You should also look for those video options in-game.
Post edited February 28, 2012 by yavornn
avatar
yavornn: There should be a launcher window before you start the game, and in that launcher you should click on video options, and select DX6 if available. If you don't have that launcher, you can go to the game's folder and look for that launcher .exe file. You should also look for those video options in-game.
Ah that...

I thought you mean actually installing it as a DX6 application using DX6 framework... The launcher for this verison only gives DX7 options.
That's a pity. So it seems that the retail version offers the DirectX 6 option. It could also be missing because you are running Windows 7.

I wonder if Windows XP/Vista gog users can choose Dx6.
avatar
yavornn: That's a pity. So it seems that the retail version offers the DirectX 6 option. It could also be missing because you are running Windows 7.

I wonder if Windows XP/Vista gog users can choose Dx6.
No idea.. but XP users do have the same trouble, if it was available I would have thought someone would have come across it as a 'fix'.
avatar
olnorton: If anyone who is crashing a lot wants to try something.
This fix has got me past a point that had previously crashed twice & run for an hour after that without crashing. I don't have time to keep testing it tonight.

Download & install the Compatibility Administrator from here http://www.microsoft.com/download/en/details.aspx?id=7352
Run the 32bit version.
It will start with New database(1) [Untitled_1] highlighted.
At the top, click on Fix.
Name the file to be fixed. Then browse to your SoulbringeVCnoeax.exe file.
Click next, to the compatibility mode screen. Ignore that & next again.
At Compatability Fixes, tick HeapValidateFrees
Click Test Run & see if it makes a difference.
Then next, then Finish.
Then Save.
Then right click on New Database(1) & install.
This has helped here a lot! I was getting crashes very early on - entering Andrus' house for the first time or talking to Elric for the first time. Rerunning the same save with different settings sometimes helped... but not for long. With this fix, the crashes seem to have disappeared... I'll see how it goes further.

EDIT: So I got to the Temple of Shadows and it started crashing consistently. I tried different compatibility settings without success. The most recent Fault Offsets are:

0x0003817f
0x0003333b
0x00032b54
0x000383af

I also have a save near the temple gate, it suffices to enter and walk a bit around and the game crashes within 2 minutes. It's the save called "27" in this archive:

http://slotik.info/sites/slotik.info/files/save.zip
Post edited March 03, 2012 by slotk
Have you tried (or any of the others who experience crashes) Directx 6 graphic mode?Although I have used this with disc version, it worked for me. Directx 7 graphic mode for this game is unstable as far as I can tell.

And believe me there's no graphical differences between 6&7. Only advantage of the 7 was T&L back then., which is using to offload the graphical chores from CPU to GPU. Which is pointless according to our way too fast CPUs today.
avatar
Gokyabgu: Have you tried (or any of the others who experience crashes) Directx 6 graphic mode?Although I have used this with disc version, it worked for me. Directx 7 graphic mode for this game is unstable as far as I can tell.

And believe me there's no graphical differences between 6&7. Only advantage of the 7 was T&L back then., which is using to offload the graphical chores from CPU to GPU. Which is pointless according to our way too fast CPUs today.
There does not seem to be any way to use DirectX 6 mode in the configuration window. Has anyone managed to enable it?