Hi The_Beam_Hero, We won’t be able to look into this directly as it’s a crash that’s likely only with your project, however I can support to help you find the cause of the problems on this one.
Are you able to connect visual studio to your editor in order to get a better idea of what asset is causing this? I’d suggest running with the commandline “-WaitForDebugger” as it sounds like the crash happens immediately. If you then look into the call stack you should eventually find a specific asset name which could be a cause.
Because you say deleting configs fixes this (not how you’d like ofc), it sounds like there’s at least 1 asset which your configs are pointing to that’s not working correctly. This can happen if it’s an old asset loaded into a new engine version, corrupted by an upgrade, or if it relied on some code or blueprint logic which was deleted without the asset registering or being saved with the redirects properly, especially for example if a base class has been removed or potentially an interface parent.