Ensure is a coding thing. It’s used to “ensure” that a certain condition applies, but it’s not too hard to lead to a crash. It just logs to console and continues. It’s nothing you as a user should worry about because usually in a case like that the engine has enough options to handle the condition. It’s more like a “this shouldn’t happen, but if it happens, I know what to do” thing.
You can try 5.3, maybe it’s better, maybe it’s not. Sometimes developing is related with luck.
Regarding Metahumans, as far as I know they didn’t change from 5.2 to 5.3, only 5.2 was a big update. Also, the 5.0 Metahumans still “worked” on 5.2, just as buggy as they were and of course without the new features. Take all that with a grain of salt, as we didn’t update our project to 5.3 yet.
By the way, the forum software notified me that we could also send DMs to each other, which is something I’d recommend if it gets too offtopic.
took one day from me because I thought my own plugin was leaking
it happens with DX12 and VK on most builds. you can run with -dx11 or use r.gpucrash.collectionenable=0 as @sirjofri said.
Hi there. Sorry for asking this after a long time but how do you find out that it is related to D3D12 GPUProfiler? I’m encounting some similiar issue and I’m trying to use Memory Insights to get some clue, I noticed some reported stacks about D3D things, but I’m not sure about if that is the reason… Looking forward to you reply TY!
