I just had this also, nothing to do with Paragon in my case, I had three instances of the same parameter collection that I’d migrated from an older version of UE, each migrated at different times, and each ending up in different folders. I was able to load my project without loading the map, then I did a search for parameter collections, did a backup, then deleted the first one from the explorer folder, then loaded the project and it worked fine, checked materials that were using it in the level and they appear to be using one of the other ones (one that wasn’t migrated for use in that level!) So, I’m guessing it’s because it’s getting them mixed up or something.
Weird thing is that although the material looked fine, the material had an error in the output log saying that it had reverted to default material, also the thumbnail was grey even though it looked fine inside the material. So, I deleted all parameter collection nodes in the material and re-added them, after that it fixed everything.
If you’re having an issue with the project not loading because the default level is crashing it, try this from chatgpt-
- Disable Auto-loading of Problematic Level:
- Navigate to the
DefaultEngine.inifile in your project’sConfigfolder. - Look for the line that specifies the default level under the
[/Script/EngineSettings.GameMapsSettings]section, like this:
javascript
Copy code
GameDefaultMap=/Game/Levels/YourLevel
- Change it to a different level (e.g.,
/Game/Levels/EmptyLevel) or comment it out temporarily.
If you only have one map in the project and it’s the one crashing it then you’ll have to locate the parameter collections from the project in Windows explorer and move each parameter collection out of the folder one by one, testing it each time till you find the culprit.