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

×
The game is one of my absolute favorites, and so far this version of it is running wonderfully... except when I try to save. Both "Save" and "Save as..." immediately crash the game to the desktop. Help please?
I'm on Windows XP Media Edition.
Post edited December 17, 2009 by DraconicDak
This question / problem has been solved by Namurimage
avatar
sethsez: I have another issue with saving, where rather than letting me enter a name to save, it opens up a box that looks as if it's for loading games instead. I have no idea what's causing it, but the end result is the same: no saving for me.

A browser window pops up, with '*.rvn' in the name field, right ? Just replace the '*' for something, for instance 'start', thus you'll end up with 'start.rvn' in the name field. After that just hit the Save button.
And now I just discovered Myst has the same issue.... and almost the same solution. For Myst, I had to disable EmulateHeap as well.
avatar
sethsez: I have another issue with saving, where rather than letting me enter a name to save, it opens up a box that looks as if it's for loading games instead. I have no idea what's causing it, but the end result is the same: no saving for me.
avatar
Namur: A browser window pops up, with '*.rvn' in the name field, right ? Just replace the '*' for something, for instance 'start', thus you'll end up with 'start.rvn' in the name field. After that just hit the Save button.

Yeah, that happened exactly once. Then I changed compatibility modes and I just got what looked like an explorer window with no field to write anything in and no button to save with. Changing everything back didn't fix it, either. It's really, really weird and I have no idea why it happened. I'm on Vista 32, for what it's worth.
avatar
sethsez: Yeah, that happened exactly once. Then I changed compatibility modes and I just got what looked like an explorer window with no field to write anything in and no button to save with. Changing everything back didn't fix it, either. It's really, really weird and I have no idea why it happened. I'm on Vista 32, for what it's worth.

Why did you change the compatibility settings ? Was it to fix some other problem you were having with the game ?
Maybe unistalling the game and re-installing it (without changing compatibility settings once it's installed) will fix that ?
Make sure you back up your saves if you do decide it's worth a shot.
Post edited December 20, 2009 by Namur
I changed the compatibility settings because nothing else would let me save without crashing.
I did wind up just reinstalling, and now I'm back to where I was before: clicking "Save" crashes the game immediately.
Combined with the missing button animations, it'd really be nice if GoG would release a fixed version.
Well, about the missing buttons animations, don't worry too much about them right now. The animations are apparently there, they're just not displaying. This may be happening due to some oversight or it may have been done for compatibility sake, we won't know untill we hear from support, but that will probably take a while considering the time of the year.
Regarding the save problem, did you install as admin and are you running the shortcut as admin ?
Or have you tried the fix that worked for DraconicDac ?
avatar
Namur: Well, about the missing buttons animations, don't worry too much about them right now. The animations are apparently there, they're just not displaying. This may be happening due to some oversight or it may have been done for compatibility sake, we won't know untill we hear from support, but that will probably take a while considering the time of the year.
Regarding the save problem, did you install as admin and are you running the shortcut as admin ?
Or have you tried the fix that worked for DraconicDac ?

The fix that worked for DraconicDrac lets me click Save, but actually saving still crashes it. And yeah, I'm running and installing it as an admin.
It's really just a shame that it's having so many issues considering it's one of my all time favorite games, and I've never had issues with it before this version.
Seeing how there are quite a few people experiencing this 'save' problem, you should definitely contact support about it, and also mention the missing animations issue.
It's odd, cause Win7 usually is touchy about this kind of thing and yet it installed and it's working fine at my end, while people on Vista and even XP seem to be the ones having trouble. If anything i'd expect it to be the other way around...
Post edited December 20, 2009 by Namur
Okay, so I fixed the issue by moving everything to another folder, and then editing mohawk.w32 to change fEnableAudioProxy=true to fEnableAudioProxy=false. Neither one worked individually, but combined it's now functioning properly.
It'd still be nice to have a copy that just works out of the box (so to speak) though.
avatar
sethsez: Okay, so I fixed the issue by moving everything to another folder, and then editing mohawk.w32 to change fEnableAudioProxy=true to fEnableAudioProxy=false. Neither one worked individually, but combined it's now functioning properly.
It'd still be nice to have a copy that just works out of the box (so to speak) though.

Great news mate, and thanks for posting the fix ;)
Well, that's 3 or 4 different fixes that work for people experiencing the problem. Hopefully anyone else having this problem will find a fix in this thread.
I have a feeling that the "move stuff" solution has nothing to do with read-only settings, and everything to do with compatibility settings. Compatibility settings are stored in the registry, and point to a hard path, so if you move the game's exe, the compatibility key will be pointing to the old location, and won't apply when you run the game from the new location. Simply renaming the folder should accomplish this as well.
avatar
ikantspelwurdz: I have a feeling that the "move stuff" solution has nothing to do with read-only settings, and everything to do with compatibility settings. Compatibility settings are stored in the registry, and point to a hard path, so if you move the game's exe, the compatibility key will be pointing to the old location, and won't apply when you run the game from the new location. Simply renaming the folder should accomplish this as well.

I don't know about that. Considering that the fix was posted on the ubi forums by someone using a version without 'forced' compatibiity settings, i'm leaning towards not agreeing with you.
Well, as it turns out, that fix did not, in fact, work. Nor have any of the others in this thread.
I'm redownloading a clean version in a different manner. We'll see what happens...
avatar
DraconicDak: Well, as it turns out, that fix did not, in fact, work. Nor have any of the others in this thread.
I'm redownloading a clean version in a different manner. We'll see what happens...

I don't understand.
Did it worked when you tried it and then stopped working again or exactly what happened ?
And you guys are taking into consideration that the 'carried over' install can't be launched with the shortcut from the original install, right ? Because that one still points to the original installation path...
And everybody experiencing this issue, even those of you who got it to work somehow, should definitely contact gog support about this with a clear description of the problem and a dxdiag.
Post edited December 22, 2009 by Namur
avatar
DraconicDak: Well, as it turns out, that fix did not, in fact, work. Nor have any of the others in this thread.
I'm redownloading a clean version in a different manner. We'll see what happens...
avatar
Namur: I don't understand.
Did it worked when you tried it and then stopped working again or exactly what happened ?
And you guys are taking into consideration that the 'carried over' install can't be launched with the shortcut from the original install, right ? Because that one still points to the original installation path...
And everybody experiencing this issue, even those of you who got it to work somehow, should definitely contact gog support about this with a clear description of the problem and a dxdiag.

It worked once, but after that, opening the same directory, or a new directory, resulted in the same crashes as before. And then that one save that did work was corrupted.
I've already contacted support with my DxDiag. See what comes from it...