MachineId:
EpicAccountId:
Unknown exception - code 00000001 (first/second chance not available)
"Assertion failed: 0 [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.10\Engine\Source\Runtime\Engine\Private\LightMap.cpp] [Line: 2151]
"
Hey zmalsberg-
What were you compiling when the crash occurred? What happens when you attempt to launch the project? Have you removed the code that was added prior to the compile crash? Please provide as much information about the crash to help me investigate on my end.
Cheers
A custom subclass of pawn, created from the editor.
The project splash screen loads, then goes right to a crash window
I tried removing the Source and Binaries folder files, without Source I get the same crash error, and for binaries, it won’t build new binary modules on launch. Getting “…could not be compiled. Try rebuilding from source manually.”
Did you remove the Source folder (move to another location on the computer) or delete the folder entirely? Once a code project is created (or code is added to a blueprint project), the Source folder becomes necessary as that is where all of the code related to the project is located. If you moved the folder to another location you can move it back. If it has been deleted, you’ll need to bring it back from Recycling. If it has been completely removed from the computer you will need to start a new project. Let me know the state of the project after this and we can look at the original problem of opening the project.
I returned the project title files, then could recompile and load the project with errors.
In the problem Pawn subclass, I named a subobject ‘Root’, also refused was ‘RootComponent’, which seems to have caused the error.
In different class of Pawn, I named a subobject ‘RootComponent’ and compiled successfully.
Everything loads now except the problem subclass, which gives an error when opening it’s blueprint “Blueprint could not be loaded because it derives from an invalid class.” Even though I returned it’s file and fixed the naming error.
I’m glad that you were able to get back into the project. The problem with the blueprint is likely related to the blueprint loosing its reference to the parent class. Unfortunately the only solution is to remake the blueprint.
Cheers