Game Crash while travelling or map change

[Kjeldoran]

everytime in some savegames the game crashes while traveling or map change.

someone have the same problem ?

[Andy(CZE)]

This pretty much looks as the 32bit OS transition - loading screen problem. I'm experiencing the same thing since the day one but unfortunately developers haven't deal with this yet. They really should make it a priority in next patch(es) because this is really annoying and in my case game-breaking problem (can't proceed in main storyline because I can't enter one essential location.)

[LIncal]

Hi,

After playing seven hours, I encountered the same crashes when loading a saved game or changing area (for example, from the Black Hound Inn to the Gilded Vale). I must admit that my processor is a 32 bit, which does not match the game requirements. My most recent savegames are concerned (note: my first run was started after the release of the 1.03 patch), so I have no alternative but to start a new game, probably after upgrading my pc in a few months . So far, it's a great game!!!

[Kriber22]

Yes, I have this problem quite frequently (also on a 32-bit system). It happens most often when transitioning to "content-intensive" areas like Gilded Vale, Caed Nua and the Copperbridge (?) district in Defiance Bay. Also, the more transitions I've had the greater the chance of a crash becomes. After 4-5 transitions it's pretty much inevitable. I've tried reducing the resolutions, tuning down graphics to the minimum, closing background applications and so on, but nothing helps.

 

However, it's not completely stuck. I can usually get to where I want to go so long as I have the patience to try over and over and over again. It's also worth trying to travel to another, smaller area first (if possible) and then going from there to your original destination.

 

It's incredibly annoying, especially since the system requirements were well within my computer's capabilities until launch day when they suddenly changed, but until I get a new computer over the summer sometime there's not much to do except hope that a future patch at least alleviates the problem.

[DocDoomII]

It should be the 32bit SO problem.

• For 32-Bit Machines
  There are reports of reporting crashing when transitioning on 32-bit machines.  We are aware of the issue and attempting to fix it.  This issue did come up on Wasteland 2, which is another Unity project, and a workaround was discovered by their fans: here
   
  You can change your system settings on your computer to increase RAM used by a single application.  However, there are inherent risks involved when changing settings involving your operating system and any attempts to change your system settings will be at your own risk.  Obsidian is not liable for any issues that might occur with those settings.

[deathcube]

I have had this problem since the 1.03 patch came out, but on a 64-bit system

[kaspergyselinck]

I have a similar issue but so far the crash has only occurred when I leave an inn in Defiance Bay and immediately after entering the newly loaded map open my map.

This has corrupted my savegame it seems.

 

My corrupted savegame: https://www.dropbox.com/s/6v9q0buox2gohse/bf8d51c55e94495095fdec3ded0d320a%2018055752%20Brackenbury.savegame?dl=0

[Andy(CZE)]

Yes, I have this problem quite frequently (also on a 32-bit system). It happens most often when transitioning to "content-intensive" areas like Gilded Vale, Caed Nua and the Copperbridge (?) district in Defiance Bay. Also, the more transitions I've had the greater the chance of a crash becomes. After 4-5 transitions it's pretty much inevitable. I've tried reducing the resolutions, tuning down graphics to the minimum, closing background applications and so on, but nothing helps.

 

However, it's not completely stuck. I can usually get to where I want to go so long as I have the patience to try over and over and over again. It's also worth trying to travel to another, smaller area first (if possible) and then going from there to your original destination.

 

It's incredibly annoying, especially since the system requirements were well within my computer's capabilities until launch day when they suddenly changed, but until I get a new computer over the summer sometime there's not much to do except hope that a future patch at least alleviates the problem.

 

I wasn't completely stuck either but after the patch 1.03 I can't enter the Catacombs in Copperlane, Defiance Bay which are essential for progress in the main storyline. So now I'm utterly screwed and really dissapointed cause the game is broken. Basically the more I play the more problematic locations I find (Skaen Temple, ruins in Dyrford Crossing, Catacombs in DB, Woodend Plains, plus I'm rather avoiding Gilded Vale and Radric's Hold..). I seriously hope this issue will be adressed as soon as possible. Giving hats to bears and cats or new icons for weapons are nice but this is game-breaking and serious problem.