Primordia - error/crash when going to 'junk' location

[razer]

In the beginning of Primordia, i did not have any problems whatsoever.  After successfully travelling to the 'junk' section on the map very early in the game, I come to the point where you use the telescope to find more locations.  After doing so, now when I need to go back to the 'Junk' section, as soon as I click on the 'Junk' marker on the map/data screen, the game crashes with the error below....

An internal error has occurred.  Please note down the following information.
If the problem persists, post the details on the AGS Techinical Forum
(ACI Version 3.21.1115)
Error:  room script data segment size has changed.

I am running the steam version of the game.  I have tried jumping to this location from different areas of the game, reboot multiple times, tried windowed mode and all other options/combinations under the winsetup.exe options, verified game integrity through steam options, all to no avail.  The game crashes everytime.  Any ideas of what it could be or potential fix?   

Windows 7 x64
12 GB DDR3 RAM
2x GTX 580 3GB
intel core i7 950

Any help is appreciated. Thanks.

[Crimson Wizard]

Any ideas of what it could be

If you visited a room at least once, game keeps information about it. This error is displayed when the remembered data does not match data, found in game file.

You mentioned, you have visited the crashing location very early in game. Did something happen with your game in between, like, have you applied any patches?
Unfortunately, I am unaware about how steam versions of the game work, what are differences from "normal" version. May it, for example, install updates automatically?
I hope one of the game's developers may give more info about that.

[Dave Gilbert]

The game was updated earlier this week. If you are playing the Steam version, that would have been updated automatically. Are you playing the new version of the game, but using a savefile from before the update? That's the only thing I can think of that would cause that error message. We tried to avoid corrupting savefiles when making the update, but it might have effected this one area.

Do you get the same error if you restart the game and try it again?

[razer]

Yes, unfortunately Steam does update automatically, and even if you set it to NOT update automatically, Steam usually does anyways, not something i've been very fond of with them! :/  The update would make more sense, as the save files I'm loading were before the update.  But I have saved since and then tried restarting the game, reloaded the recent save (post patch) and still get the exact same error when going to that specific 'room'.

I'm going to start a new game and see if i can access that same room, it shouldn't take too long to get back to that point. Will post results..

[Crimson Wizard]

But I have saved since and then tried restarting the game, reloaded the recent save (post patch) and still get the exact same error when going to that specific 'room'.

This does not really matter, I am afraid, because the "remembered part" will stay the same, it does not update, unless you re-visit same room.
To elaborate:
1. You enter the room A, and since then room A status is put into the memory.
2. You save game, and room A status is saved into file as it is.
3. The game is updated, and the room data changed. But the room A status in save file does not change.
4. You run the updated game and load save file. The room A status is loaded back as it was before the update. But since you are in the different room, program does not check that (yet).
5. You try to enter room A again. This is first time room A data loaded again after update, and is being tested against room status in memory. Program sees that the room data does not match status in memory, and shows error message.

[razer]

Started a new game, was able to access the 'Junk' room initially and after I got past where I left off, so I would say it's safe to assume that its as you mentioned, the save file probably got corrupted somehow during the update.  I would also assume that this has more than likely not happened with anyone else being that I haven't seen any other posts about this issue, so i may have just got the bad luck on my end.

Thanks for the assistance and info anyways, and at least it's posted in case anyone else comes across the same problem.

[Dave Gilbert]

It's happened to one other person that I know of (there's a thread about it on the WEG forum), so you're not the only one! We really bent over backwards to fix the bugs and not invalidate savefiles, but apparently we missed this one set of circumstances. Sorry about that!

-Dave

[razer]

No worries! No one's perfect, it's just a part of making games, and its worth dealing with to have great games such as this one! I do appreciate the replies in helping to work with the issue, you guys have a great community here.  Keep up the good work!