Error during V-Ray RT initialization in stage 9!

[Johnnysonicom]

Hello,

Since upgrading to 3ds Max 2016 and using CPU based ActiveShade Rendering using V-Ray RT 3.30.03 I have been getting the following error followed by an immediate crash of Max.

SYSTEM: Active Shade renderer is changed to V-Ray RT 3.30.03. Previous messages are cleared.
error: Error during V-Ray RT initialization in stage 9!

If anyone could shed any light on the problem I would be very grateful.

I have attached the max scene and the dumpuserinfo.

Many thanks,

John

testfile2016.zip

[svetlozar.draganov]

The scene you sent us works fine here under 3ds Max 2016 and V-Ray 3.30.03.
Does the issue occur on every scene(even on empty one) or it exits only on that particular one?

Would it be possible to send us the full log from the Render Message > Active Shade window?
Make sure that Show /Log Information and Progress Messages checkbox are active from the Rendering Tab of the Preference Settings window.


Does the issue appear with previous version 3.20.03?
Does V-Ray RT work fine with OpenCL and Cuda engines?

[Johnnysonicom]

Hello Svetlozar,

Thanks for responding.

This seems to happen even on a empty scene.
This did not happen when using 3.20.03.
This happens when using CPU, OpenCL and CUDA methods.

Max does not save the logfile (despite the preference settings as you dictated) but I managed to copy the info from the window - please see files attached.

Many thanks for your support,

John

logfiles.zip

[tashko.zashev]

Thanks for attaching the log files.

Unfortunately we are not able to identify the issue easily by this error message.
Are you using any custom presets or maxstart file ?
Would you please try to deactivate the option "In process RT engine" from the RT settings and try again ?

If nothing helps, then I would recommend to contact us via our support mail - support@chaosgroup.com

[Johnnysonicom]

Hello Tashko,

I was using both custom presets and a custom maxstart file.

After removing these and starting using the 2016 defaults the issue seems to be resolved.

If it happens again, and I can narrow it down to a particular action I'll be back in touch.

Many thanks for your help!

All the best,

John

[tashko.zashev]

Thank you for the update.
Let us know if we can be of any further assistance.