Having a realy hard time here using a custom RamaSaveEngine class.
The issue: Can’t start the editor any more. Getting a crash during editor loading at 71%.
Here the log from VisualStudio:
'UE4Editor.exe' (Win32): Loaded 'C:\Program Files\Epic Games\UE_4.16\Engine\Plugins\Editor\FacialAnimation\Binaries\Win64\UE4Editor-FacialAnimation.dll'. Symbols loaded.
'UE4Editor.exe' (Win32): Loaded 'C:\Program Files\Epic Games\UE_4.16\Engine\Plugins\Editor\FacialAnimation\Binaries\Win64\UE4Editor-FacialAnimationEditor.dll'. Symbols loaded.
'UE4Editor.exe' (Win32): Loaded 'C:\Program Files\Epic Games\UE_4.16\Engine\Plugins\Editor\GameplayTagsEditor\Binaries\Win64\UE4Editor-GameplayTagsEditor.dll'. Symbols loaded.
'UE4Editor.exe' (Win32): Loaded 'C:\Program Files\Epic Games\UE_4.16\Engine\Plugins\Marketplace\RamaSaveSystem\Binaries\Win64\UE4Editor-RamaSaveSystem.dll'. Symbols loaded.
[2018.02.23-19.25.28:387] 0]LogLinker: Can't find file '/Script/AdvancedSessions'
[2018.02.23-19.25.28:387] 0]LogLinker: Can't find file for asset '/Script/AdvancedSessions' while loading ...
...
The log goes on and on and on. Tons of Can’t find file and stuff. As you can see the issues first start occouring after UE4Editor-RamaSaveSystem.dll was loaded.
Removing the line from the DefaultGame.ini that specifies my custom RamaSaveClass, I can load the project as usual.
At some point visual studio has a null access, allways at the same codeline, always the same class PropertyTag.cpp line 58. It wants to save a property of a class that is not related to the custom RamaSaveEngine class. But after tons of errors with loading, that error is telling nothing.
It took me a long time to narrow the cause down. At this point it seems to crash when the custom RamaSaveEngine class references another custom class IN ANY KIND OF WAY. Even an empty custom RamaSaveEngine with ONLY a CreateWidget node in it that references another custom class, will cause the crash. The node is not even connected to anything. No variables.
Unfortunately I was not able to recreate the issue in a fresh project (UE4.16).