SoA 2.0.1.0 update 1: immediate CTD on selecting raised levies

[zijistark]

Checksum: GFTG (did a full reinstall to be sure)
Platform: Windows 7
DLCs: All major but sunset, some of the portrait packs (incl. Celtic), plus the customizer and EU converter.

Issue: Immediate CTD when selecting any raised levies.

How to reproduce:

1. Start as the "King" of Munster (Ua Briain) in Ireland at the Stamford Bridge start.
2. Either unpause or don't. It doesn't matter.
3. Declare war on the Earl of Desmond, de jure claim.
4. Raise all levies (demesne + vassals) or only raise your demesne levies-- same either way-- from the Military View.
5. Once you either drag-select or simply click on a unit, you will experience a totally reliable CTD.

I also tried this as King Konan of Brittany at the Stamford Bridge start. Declare war on France for your claim on Normandy. Once you try to select any of your levies, instant CTD.

Update: Um, even trying to select the already-raised levies of William the Bastard at the Stamford Bridge results in an instant CTD.

Update: This also happens in exactly the described fashion for regular 2.0 (WGPN). I've been totally locked out of playing this game since 2.0.

 

[AndrewT]

Please try a full clean re-install:

STEAM
- move any valued save games elsewhere
- "delete local files" in Steam
- manually delete all files left under Steam/CK2 AND Documents/CK2
- re-install game in Steam, run a verify when done.

GAMERSGATE
- move any valued save games elsewhere
- uninstall the game from Windows
- manually delete all files left under the GG CK2 AND Documents/CK2 folders
- re-install game from GG but point it to a new location outside the system path, such as c:\games\ck2\
- apply the latest patch (only)

 

[zijistark]

Wow. Fast. So fast that I couldn't delete my post, as I just resolved the issue. I'd deleted all local content, reinstalled, etc., but my old settings.txt, gfx/, etc. in My Documents was still intact. Deleting them (and manually editing the new settings.txt to have the proper refresh rate-- the game doesn't detect or allow me to change it to the correct value and forces an unsupported video mode on the GPU) solved the problem. Note, I reverted back to 2.0 in the interim, but I'm sure the issue's independent of the changes between 2.0 and the 2.0.1.0 beta.

Case closed. Feel like a dolt. Thanks for the fast reply!