Been having issues with UE5 for a while now, currently on 5.3.2 and the engine keeps crashing. It happens only when trying to open the file browser, whether it’s opening an existing project, importing files or just browsing a file location to store a new project. However, it does seem inconsistent, sometimes it doesn’t crash the first or second time.
I have also never dealt with getting help with crashes so if I’m missing any context, let me know and I’ll send it. But this is what the crash reporter says when it pops up:
I have tried verifying, fresh installing and I tried an earlier version as well as Unreal 4.27.2. The only one which didn’t crash was 4.27.2 so the issue is with Unreal 5. I hope this helps somewhat
I am using a GTX 1660ti, not sure the specifics though.
If I’m honest, not exactly sure how to switch RHI but I will try and find out how.
I just tested on a blank project and it’s the same thing, the moment I click on import, it crashes. Same for if I try to open a new project from that window too.
Posted a GIF to show what I’m dealing with right now, I can load projects fine when they show up in the main window but the moment I do anything which requires opening the microsoft file explorer, it crashes. Sometimes it takes clicking the button working a few times before crashing though.
Okay just done the RHI switch, it appears to be working when in DX11 but when I switch back to DX12, the issues come back. I’ve at least narrowed it down to being a DX12 issues, thank you. Hopefully I can fix DX12 now
I will try this tonight. Sadly the DX12 wasn’t the issue, at least I don’t think. It kept crashing on DX11, just took a bit longer. I’ll keep you updated on if this is a fix!
I have found that Unreal 5.2 works fine for me, I don’t know what happened in 5.3.2 but it seems very incompatible with my PC at the moment so I will wait for a new version to roll out. Sorry I can’t be much help, I’m still lost for a solution myself
Yeah I think this is what I’m going to start doing from now on, I should’ve expected this much but I guess it was my mistake to jump straight into 5.3.2, hopefully a fix will be included in the next version (I know they got at least 30 crash reports from me alone ahah)
