v1.4.2 crash

[deepblue812]

testing out some Vantage workflow with the free Evermotion anniversary scene and getting a pretty consistent D3D crash, but doesn't seem to be related to any specific item or area of the scene as far as I can tell. Sometimes I can maneuver around and edit the scene for 10-15 minutes before it crashes, other times is just a minute or so. Log seems to indicate something with a map call (?)

Have tried with nVidia driver 466.11 and 471.41 on an rtx3090 and getting the same error. Debug_log.txt attached

-SJ

[vladimir.nedev]

Can you tell us what you are doing when the crash happens ?
Just navigating the camera or changing something else maybe ?

Greetings,
Vladimir Nedev

[deepblue812]

nothing in particular as far as I can tell. seems to happen occasionally when navigating through the scene or interacting with the geometry.
In fact just now was trying to pinpoint any particular object that was causing it and had left the machine to eat dinner. When I returned it had crashed with the same D3D error.

tried with and without the Safe GPU activated

Tried again and let it sit for a bit and had some new errors, log attached. Looks like some CUDA errors this time instead of the map error from before.

[npg]

Does this happen with other scenes? If you are using V-Ray GPU, are you having random issues with it as well?

The second debug log is quite unexpected. Given that you have plenty of free VRAM and you weren't doing anything, is it possible that your GPU is overheating? Try running some GPU monitoring app (e.g. GPU-Z, MSI Afterburner) and maybe some stress testing apps (e.g. FurMark, OCCT, though our app also uses RT and tensor cores that these tests do not).

[deepblue812]

Shouldn't be overheating, stays cooler during Vantage than any gaming, and I do regularly monitor the temps in GPU-z (for Vantage average GPU ~ 64°C, memory ~ 75°C). The CUDA error might have been because I was resizing the window quite a bit and changing focus to some other windows while it was running in the background, hadn't seen that error before then. This is the only scene I've tried lately that seems to have any crash issues. It is from Evermotion and not built by me, so not sure what quirks are in there.

Trying the scene now with Vray GPU to see if it has any issues with that. I noticed it threw a few warnings about map channel index 0 displacement missing, and a couple warnings about a non-GPU supported displacement.

[npg]

Is it this scene? https://evermotion.org/articles/show...of-evermotion-

[deepblue812]

yup, that's the one

[deepblue812]

Dug a bit deeper into the scene using Vray GPU render. The warning for the displacements seemed to be coming from several of the rock textures/objects. Vray didn't seem to like a few of the objects having 2D VrayDisplacementMod applied, switching to 3D fixed the warning, and on a few of the objects that had 3D set on the displacementMod it didn't like having the 'Use object mtl' checked on. Kept adjusting objects until all the warnings were cleared from the Vray GPU render log and re-exported as a .vrscene and brought into Vantage. Been tinkering with the scene for about an hour now and no crashes.

Guess the moral of the story is the Vray GPU renderer message window is useful for troubleshooting Vantage scenes even when the .vrscene export dialog doesn't throw any errors.

[vladimir.nedev]

This is most likely a coincidence, Vantage ignores all displacement.

Greetings,
Vladimir Nedev