Crash to desktop with new .NET runtime 4.7.2 (SOLVED - corrupt savegame)

vool
Posts: 3
Joined: Wed Jan 09, 2019 4:31 pm

Crash to desktop with new .NET runtime 4.7.2 (SOLVED - corrupt savegame)

Postby vool » Wed Jan 09, 2019 5:34 pm

Since yesterday I get a reproducable crash to the desktop when I enter the Geoscape. Before that everything was fine. The crash comes with this error:
Pure virtual function being called while application was running (GIsRunning == 1)

So far I believe that LW2 has an issue with the .NET Framework 3.5. and 4.7.2 update that came on Patch Tuesday yesterday (01/08/2019) with Windows Update, because the only mod I'm using is LW2, and if I deactivate it and load a vanilla savegame, everything works fine. Granted, I can't rule out savegame corruption (can't try an earlier save of this campaign due to Iron Man), but IMO that's unlikely because before the new .NET runtime I had no problems. Also, I never had savegame corruption so far.

I tried verifying the local Steam files, but no reinstall yet.

I noticed that the 4.5.1 folder in Program Files (x86)\._._.\XCOM2\_CommonRedist\DotNet is empty now, and there's a new 4.5.2 folder with the date of this recent Windows Update. That new folder has the new runtime files. Maybe I could find the old files, copy them back to the 4.5.1 folder, and then delete the new 4.5.2 folder? Would that force XCOM2 to use the old .NET runtime again?

EDIT: Because of the different version number of the .NET update I tried renaming the new 4.5.2 folder to 4.7.2, thinking that maybe the update was bungled. Didn't change anything, though.

I'm using:
- LW2 1.5 with latest hotfix
- Windows 10 (1809, Build 17763.253)
- No mods (other than LW2)

Does anyone else have the same problem, and maybe found a solution?

Thanks in advance!
Last edited by vool on Fri Jan 11, 2019 1:49 am, edited 1 time in total.

johnnylump
Site Admin
Posts: 941
Joined: Wed Nov 11, 2015 4:12 am
Location: Colorado
Contact:

Re: Crash to desktop with new .NET runtime 4.7.2

Postby johnnylump » Wed Jan 09, 2019 10:28 pm

A pure virtual function crash can be lots of things; you'd probably want to find the game logs to see what's going on.

I don't have any immediate suggestions but will be keeping an eye on this thread.

vool
Posts: 3
Joined: Wed Jan 09, 2019 4:31 pm

Re: Crash to desktop with new .NET runtime 4.7.2

Postby vool » Thu Jan 10, 2019 1:08 pm

Thanks for replying. Unfortunately I didn't find any information on how to interpret the game logs. The launch.log doesn't even contain the pure virtual function error, but lots of "duplicate NetIndex" errors.

In any case, the launch.log is in the attachments, if someone is willing to take a look.
Attachments
Launch.zip
Launch.log
(33.56 KiB) Downloaded 4 times

johnnylump
Site Admin
Posts: 941
Joined: Wed Nov 11, 2015 4:12 am
Location: Colorado
Contact:

Re: Crash to desktop with new .NET runtime 4.7.2

Postby johnnylump » Thu Jan 10, 2019 10:50 pm

The last thing in there says something about autosave issues. Have you tried a new campaign?

vool
Posts: 3
Joined: Wed Jan 09, 2019 4:31 pm

Re: Crash to desktop with new .NET runtime 4.7.2

Postby vool » Fri Jan 11, 2019 1:15 am

Good call, sir. I started a new LW2 campaign, entered the Geoscape after Gatecrasher, and had no issues. Looks like the runtime stuff was just a coincidence and I had my first corrupt savegame.

No more Iron Man for me from now on, I guess.. because I couldn't even go back to an older save from my backup, because when I start the game the local file is overwritten with the corrupt one from the Steam cloud. :(

Thanks for the help!

EDIT: Ha! I managed to revert to an uncorrupted savegame from my backup by starting Steam, waiting for the cloud sync to finish, and *then* overwriting the savegame again.


Return to “Long War 2: Bug Reports”

Who is online

Users browsing this forum: No registered users and 4 guests