Keep getting a crash on starting project in UE 5.4

I am completely lost as to how to fix this issue, does anyone have ideas?

So when I run my project, it builds correctly and then crashes at 95% of loading with the error below every time. I’ve tried the following and had no luck in removing this issue:

  • Uninstalled and reinstalled
  • Deleted binaries, intermediate, saved, and DDC folders
  • Cleaned the solution
  • Regenerated the VS files
  • Restarted my PC
  • Opened a blank project in 5.4 and then tried to open my target project from inside the editor
  • Rolled back to previous (working) versions in gitlab

Error:
Assertion failed: UniformBufferStruct [File:D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Classes\Materials\MaterialParameterCollection.h] [Line: 172]

A breakpoint instruction (__debugbreak() statement or a similar call) was executed in UnrealEditor-Win64-DebugGame.exe.

Exception thrown at 0x00007FFE6E3FD74E (UnrealEditor-RenderCore.dll) in UnrealEditor-Win64-DebugGame.exe: 0xC0000005: Access violation reading location 0x0000000000000018.

The program ‘[25028] UnrealEditor-Win64-DebugGame.exe’ has exited with code 0 (0x0).

2 Likes

For anyone that stumbles along this, the issue was that we had UDS in the project and had set the “Allow Static Lighting” in project settings to false. Which meant the UDS instances that had the clouds set to “Static Clouds” caused the engine to crash when loaded

7 Likes

Thank you so much! It worked for me too!! :slight_smile:

In my case, I disabled this line +D3D12TargetedShaderFormats=PCD3D_SM6 in the DefaultEngine.ini file, so the project can load with Shared Model 6 disabled.

1 Like

Got the same issue. Tried all tips. And now I even cannot open previously worked level! I played on it right before trying to fix issue. Before applying changes to project config I got this issue only during seamless travel to problem level (but I could open this level in editor and start plying). After that I removed lighting built data and now I can’t build it - editor crashes when I try to open level.

Also, I still can package project, start this level and play on it.

I was able to open problem level by removing shaders cache. But now all shaders are prepared and Editor crashes again.

My current investigation results:

  1. UE crashes when I try to open problem level; Standalone crashes at start.
  2. From crash report: MaterialParameterCollection.h. I have three meterial parameter collections in my project. I just tried to remove them. Materials was broken, but I was able to open level and even test standalone.
  3. I found problem collection, tried to remove only it - all works fine.
  4. I don’t remove it - just open, close without saving and then check - world is opened without crash, but standalone still crashes. Tested many times.
    Will continue investigation, maybe will hardcode collection into all materials.
1 Like

Hi, i have the same crash but in my case the project opens fine but crashes when opening some character blueprints(i.e the paragon ones), the odd thing is that it was allgood last night and today it started crashing without any changes being done.I’ve tried all the above tips to no avail.Is ther any new info on this crash?

Best regards,

1 Like

I’ve removed the assets with the broken parameter collection from my project and it seems fine.Thanks for the hint @PazDim

Best regards

Yeah, I also got problem in Paragon’s character (Shinbi) from Marketplace. I was able to fix my issue by removing parameter collection and correct materials. Now all works fine (even other Paragon’s characters with parameter collections).

How did you fix the materials?When i delete the collection i can use the blueprints but the materials no longer work so i end up with the characters without them.

Best regards

Would love to know too! I’ve got this same problem - came out of nowhere, what a pain!

In my case, it’s definitely related to Paragon meshes. Looks like a marketplace developer has used the Paragon assets as a starting point, so even though I have no Paragon assets in my project, I’m still getting the error. I’ve fixed it by searching inside the project for - type=materialparametercollection - sort by alphabet and then look for ‘Orion’ this identifies the Paragon assets that are causing the problem. Then look at which one or ones relate to mesh assets - they will be the culprit - removing the ‘OrionGlobalGamplay’ file has fixed my problem.

1 Like

Yes, i did the same but i’m using the Paragon characters so if i remove those files it will break the materials, the strange thing is that the crashes only happen if i have multiple characters in the project.
If it’s the FX materials i can dump them.
Gonna try it tommorow,

Best regards,

Nah i’ts the one from the characters, only way i can get the crash to go away is by bricking the characters.

Best regards,

@twangydave
Sorry for delay - I didn’t receive notification.
I tried again with Wraith character, here are my steps. This is very dirty work, but I use these characters only for tests, so it is ok for me.

  1. Remove material parameter collection;
  2. Open Skeletal Mesh asset - all materials are broken;
  3. Open first material, try to compile - got errors like:
[SM6] Function MF_CharacterEffects: (Node CollectionParameter) CollectionParameter has invalid Collection!
[SM6] Function MF_CharacterEffects: (Node CollectionParameter) CollectionParameter has invalid Collection!
[SM6] Function MF_CharacterEffects: (Node CollectionParameter) CollectionParameter has invalid Collection!
  1. Click on each error - it opens place with unspecified material parameter, I hardcoded it by needed color. In one place Vector4 is used!
  2. That’s it - all materials are fixed (parameters were hardcoded in shared materials functions, so just recompile rest materials).
2 Likes

Thank you so much for this. This 100% works, though it’s kinda scary when everything breaks at first.

A better fix is selecting all Material Instances (and probably Materials too). Right click → Asset Options → Validate Assets.

That will fix the references that got broken for whatever reason. Now I can open the levels that had the problematic characters.

No need to delete the parameter collections.

1 Like

Hi everyone. I had the same problem. The solution was to completely remove the “ParagonAurora” folder that I had downloaded in the last session, before everything crashed. I hope it helps you.

I fixed this by Resaving all files in the folder of any paragon asset that has the error, which is the “Global” folder. Global → right click → Resave All. Thanks me later!. xd.