Hi, I’ve upgraded a 5.1.1 BP project to 5.2.1 using the clone method but when I try to open the upgraded project I get a Message popup saying “Pure virtual function being called while application was running (GIsRunning == 1)”. Hitting OK on this crashes the editor. I can see the UI / UE logo at the top left of the editor looks a bit wonk:
I’ve tried updating a number of times, and sometimes this error shows up immeditately, sometimes it shows up after closing and reopening the project a couple times.
I tried deleting the config folder, and this appeared to be a durable fix - but it is not ideal as I have a number of custom collision channels and such that I would need to manually re-do.
I’ve stripped out plugins.
Any help greatly appreciated. I was wondering if the glitchy UI is a clue to what may be corrupted?
A similar error popped up in x-com 2 (made in UE but older). Some poster pointed towards reinstall of .net others say that it has to do with virtual memory being set too low.
If the ui is wonky then resetting graphics drivers to default settings and reloading default layout in unreal usually fixes that.
Also try running an integrity test on your engine => Epic Launcher => Unreal => You version of the engine => verify.
You could try deleting temp folders
Intermediate
DerivedDataCache
Saved
Binaries (if c++)
Grasping a bit at straws, but who knows maybe it will work.
Thanks for all of that! Tried all of your suggestions but sadly still seeing the error after re-opening. The only thing that gives me a durable fix is deleting the config folder. I believe it is something in the DefaultEngine.ini file - slowly cut and paste the pertinent settings from the 5.1.1 project and it appears I’m back in action with my custom collisions etc working as expected.
Perhaps archive your current project to a zip file and create a fresh one in 5.2 with the same name. It should have all of the correct naming conventions in the ini files then unzip the old project and replace the config (ofc paths would have to be the same).
It might work if it’s pure 5.2 config (keep the backup just in case though)
Oh thats a good idea too. Thanks! Seems like my method is holding up so far - delete and regenerate all .ini’s in the config folder > copy pertinent code (just my controls, collision, physical mats, etc) from 5.1 .ini’s into the 5.2. Multiple re-opens and I am not seeing the error.
