Ok so, I was importing a few things and come across a bug. At first I simply began to think I didn’t have enough memory to support this. Then a Person I met on Discord also tried in a clean empty project, to load the same file. Now we tried in in OBJ and in FBX both giving us errors and Crashing. I only have 16gigs of Memory, he has 40+ He will Post his Error Message here shortly, and I can also Provide the Files in Question. If needed.
At first I thought this was a Memory issue but after having him test it across Versions 4.13.* and 4.14.* Will Post Errors for 4.14.* and 4.13.* for Windows 10 here Shortly, sometimes it doesnt Launch the Error and also Doesn’t send it.
If you can provide the mesh that would be great. Sometimes these issues are specific to meshes that I cannot reproduce locally and I’ve not run across any “out of memory” crashes like this when you should have more left. Although the log is showing that it was using ~23gb of ram for this one mesh.
When you share the file please include your DxDiag as well.
Will do soon. For some reason I think it has to do with the Density, I broke the file down into 5-6 parts separated them so they weren’t all together and had no problem at all.
That’s definitely a way to handle it. Ultimately, if you’re getting a crash, where the crash reporter window opens, we’d like to reproduce that part and report it. The goal here is for the editor not to crash in these instances but to gracefully fail and give you a warning message over a crash report and the editor closing. Anything you can provide that would reproduce this, would be helpful to that end.
Marking this as resolved for the moment. If you have a test asset that can reproduce the crash or additional steps to recreate it without the asset please post back here to re-open this ticket.