Solved Game freezing on conquer 4.0.9 update

[Choochoo1]

The game was running stable before the update, I updated workshop framework, and the 3-in-1, saving and closing after each update as was suggested in another post. but when I updated conqueror the game started to freeze on load in, even on older saves. I have a descent mod list, but like stated, it was running fine before the update. when I rolled Conqueror back to 4.0.8 it started working again, even with the 3-in-1 on 4.0.9.
Any help would be appreciated.

 

[1ae0bfb8]

hi, theres been a couple of reports of this, and i experienced it myself. the fix is curious and it is as follows;

1. update workshop framework - start your game, save, exit.
2. update conqueror - start your game, save, exit.
3. update simsettlements - start your game, save, exit

i have no idea why staggering the install in this way remediates the issue - but it works. if you search these forums you will see this advice repeated in a couple of posts. try it, and report back with your findings.

 

[bullyrook]

The game was running stable before the update, I updated workshop framework, and the 3-in-1, saving and closing after each update as was suggested in another post. but when I updated conqueror the game started to freeze on load in, even on older saves.

the fix is curious and it is as follows;

1. update workshop framework - start your game, save, exit.
2. update conqueror - start your game, save, exit.
3. update simsettlements - start your game, save, exit

i have no idea why staggering the install in this way remediates the issue - but it works.

So staggering the updates is necessary but the key to success is doing it in the precise order @1ae0bfb8 has listed?

 

[1ae0bfb8]

i still have no idea why staggering the updates makes this work, but i guess - and it is a guess - the order also plays a part?
makes no sense at all.

 

[Choochoo1]

I tried this but I framework, then 3 in one, then conquerer. but I did save and exit between each update. I got the framework and 3 in 1 updated fine like this, but then when I do Conqueror, instant freeze on load.

 

[1ae0bfb8]

yeah, i am wondering if the order of how they are loaded matters? no clue because it makes no sense to me that doing this works, while installing them together doesn't.

 

[bullyrook]

I tried this but I framework, then 3 in one, then conquerer. but I did save and exit between each update. I got the framework and 3 in 1 updated fine like this, but then when I do Conqueror, instant freeze on load.

This is why I wondered if the order of updates was the key, not just the staggering.

@Choochoo1 updated WSFW, then SS/3in1, then conqueror = freeze on load.

@1ae0bfb8 's post lists the order as WSFW then Conqueror then SS/3in1. @Choochoo1 have you tried doing it in this order?

I'd test for myself but I'm on an Xbox and if updating shits the fan then there's no rolling back for me.

 

[Choochoo1]

I tries this order and no luck, still a freeze on load.

Edit: So I was able to get it to work but I had to rollback to an old save and lost about 3 hours, better than all 10 thought. still not sure what caused it though.

 

[bullyrook]

I tries this order and no luck, still a freeze on load.

Edit: So I was able to get it to work but I had to rollback to an old save and lost about 3 hours, better than all 10 thought. still not sure what caused it though.

Well, I tried the order I mentioned above, too. WSFW-Conqueror-SS. Since Conqueror depends on WSFW and SS, an in game prompt highly suggests you don't continue the save until you also update SS. Makes total sense in hindsight and should have been apparent to me before I suggested it. If staggering updates and loading/saving game before each is necessary then the order WSFW-Conqueror-SS seems problematic.

Anyway, the update worked for me. No problems. However, before I decided to finally do it, I was dealing with a problem that developed in my 4.0.7 game where I could no longer autosave or hard save. I had to roll back more than 36 hours of saves just to get a game that would let me reliably save again. And I spent three full days trying to root out the problem. Still haven't figured out exactly what was causing it (only where and when it would start) It's entirely possible 4.0.9 just quashed it for me.

Rolling back always reminds me of my favorite joke. Guy walks into a bar one afternoon and says to the bartender: "Hey, did I come in here last night and put $100 bill on the bar and then proceed to drink through it all?" Bartender replies, "Yes, you did!". Guy: "Whew, that's good. I thought I lost it."