Crash when loading an EXR file, happened in 4042 as well
3 Likes
@JakBB I haven’t encountered any problem loading an exr heightmap exported from gaea, using file input. Loads, and builds fine.
That said, WM did crash when I tried to load an exr normal map inside the “Material” node set to import.
Can you outline the steps to reproduce the crash conditions in your specific case?
1 Like
Curious… I can’t replicate this issue, and WM simply uses the OpenEXR library, so it would seem odd to have a crash in it.
Is it a consistent crash, or spradic? Did the crash produce a crash dump file / crash reporting window?
Looks like it depends on the EXR file, when I try and import one from Gaea it works. If I import one from Megascans it crashes.
I sent the crash logs to support
1 Like
@JakBB Makes sense, the exr normal map I was importing within my material node was also from megascans library. I don’t have any more of those, and I don’t want to dig into meegascans either (since Fab came about). I’ll test some more with other sources.
Upon further investigation I found out that EXR files containing RGB data, even those exported in the past directly out of world machine, crash wm instantly (even if the file input is set to heightmap, so it’s not exactly file input that’s the problem). While those containing grayscale data (like a heightmap or mask) load normally.
This thing is true with both File input node, and the Material input node. Grayscale EXRs load normally, RGB EXRs crash the session instantly.
1 Like
That’s very helpful, thank you! I have found and fixed the offending issue. (Importer code was not updated to handle WM’s internal change to half-floats for RGB).
2 Likes