Vray IPR crashing immediately

Hello, I’ve been going through all Phoenix FD samples provided and most of them result in an immediate crash as soon as I turn the Vray IPR on (doesn’t matter if is CPU,CUDA or OpenCL). I’m on Windows 10, Maya 2017 SP3, GeForce GTX 1080, 64GB RAM, i7 6800K, and latest Vray/Phoenix FD.
I’m attaching all the log files and a sample project that crashes instantly (for me) as I turn the Vray IPR on, maybe someone could try it or tell me if there is anything at all that I can try? Thanks

Maya 2017 project:
Crash log files:
crashTest.zip (19 KB)
crashInfo.zip (110 KB)

Hey,

Thanks for reporting this! IPR for Maya is not supported yet, I hope we can be on it these next few weeks.

Cheers!

Thanks for the prompt answer Svetlin.

Any ETA on a possible fix? If (especially) there is a PhoenixFD element in the scene, the IPR crashes immediately.

Hey,

Would it be possible to send us a scene for this or steps to reproduce, e.g. using the toolbar presets? We stabilized it since the last time we talked about it, so if there are still any issues, we have to fix them. Also, are you using latest Phoenix and latest V-Ray?

Cheers!

Ah, managed to crash it here as well! Will ping you again soon with hopefully some good news :slight_smile:

Alright, please check tomorrow’s Phoenix nightly for the fix - the crash occurred when rendering a mesh with displacement in IPR, depending on the number of threads used.

Thanks very much for the heads up! Please ping me if there are still issues!

Thanks, will do. In any case, if it might be of any help, here is a scene that for me crashes instantly each time: in the scene there is only a PhoenixFD Simulator and VRayPlane, so just a very simple test bench. Activating the IPR, no matter if CPU or GPU based, results in an instant crash. Hope this can help to debug things.
crashTest.zip
crashTest.zip (29.4 KB)

Affirmative - should be working fine now :slight_smile:

Working flawlessly now, thanks a lot for the fix!

Hooray! Thanks for bumping us on this - originally we fixed a different IRP issue, so it was very important to resolve this too.

Cheers!