At the Gates > AtG - Bug Reports

enemy settlement takeover crash

<< < (2/2)

sunako911:

--- Quote from: sunako911 on February 27, 2019, 02:23:54 PM ---
--- Quote from: sunako911 on February 06, 2019, 04:01:14 AM ---i try to capture an enemy settlement.. it says captured if i wait a turn it goes back to the enemy.. if i then attempt to pillage instead the game will crash upon attempting to end the turn.

--- End quote ---

Fix Attempts:
Reloading from a previous save prior to conquering - (Failed - Ends in inevitable crash upon capture or pillage end turn)

Destroy/Capture all surrounding enemy structures then proceed to park troops on enemy settlement - (Failed - Ends in inevitable crash upon capture or pillage end turn)

Reloading from a previous save prior to conquering and instead of leading to attack/conquer abstain from battle - (Failed - Crashes on End of Turn)

Start a Clean Save - (Failed - Ends in inevitable crash upon capture or pillage when conquering at end turn)

Verify File Integrity - (Failed - Makes no Change still results in inevitable crash)

Fresh Reinstall of game - (Failed - Makes no Change still results in inevitable crash)

Updated hardware drivers - (Failed - Makes no Change still results in inevitable crash)

Full System Virus Scans - (Failed - Makes no Change still results in inevitable crash)

[Progress Report]
Issue Status: Unresolved
Current Date: 2/27/2019

--- End quote ---

[Progress Report]
Issue Status: Unresolved
Current Date: 3/01/2019

Jon Shafer:
Is this still a problem with v1.0.1? If so please upload a save file and I'll take a look. :)

- Jon

sunako911:

--- Quote from: Jon Shafer on March 06, 2019, 11:42:13 AM ---Is this still a problem with v1.0.1? If so please upload a save file and I'll take a look. :)

- Jon

--- End quote ---

after further investigation, i believe its a problem with the update being applied to old version saves.

to fix the issue for everything except my Pre v1.0.1 save i had to fully erase all things relating to the game (uninstall + remove all game files in steam folder) and reinstall.

the old save file that i backed up still has constant crash problem and i cannot proceed with the "gamesave at said point"
im not sure if im entirely accurate on the diagnosis of the problem but perhaps im in the right area

here is the broken save...

sunako911:

--- Quote from: sunako911 on March 06, 2019, 05:35:57 PM ---
--- Quote from: Jon Shafer on March 06, 2019, 11:42:13 AM ---Is this still a problem with v1.0.1? If so please upload a save file and I'll take a look. :)

- Jon

--- End quote ---

after further investigation, i believe its a problem with the update being applied to old version saves.

to fix the issue for everything except my Pre v1.0.1 save i had to fully erase all things relating to the game (uninstall + remove all game files in steam folder) and reinstall.

the old save file that i backed up still has constant crash problem and i cannot proceed with the "gamesave at said point"
im not sure if im entirely accurate on the diagnosis of the problem but perhaps im in the right area

here is the broken save...

--- End quote ---

i just got back to a "conquering point" in my new save post v1.0.1 i attempted to capture "the Huns" while playing as "alemanni" it said the Huns' were unlocked upon doing so however the settlement swapped back to the Huns' color (yellow) from my color (orange) out of curiosity to see if the crash would repeat as it did in my pre v1.0.1 gamesave i tried to load a earlier save 1 turn prior to that decision and i received the same error i posted before. i then relaunched the game loaded up the save and attempted to pillage this time.. oddly every time i pillage it refuses to acknowledge their defeat and destroy their building permanently causing them to endlessly rebuild the settlement. this is a bit different from pre v1.0.1 gamesave's problem however this doesn't force crash the game. i attached a post v1.0.1 gamesave below of the aforementioned game 1 turn before (capture/pillaging) test for you to examine should you wish to do so.

Navigation

[0] Message Index

[*] Previous page

Go to full version