VRay 3.5.04 bugs

[olly]

A few bugs I have found in the current release of VRay, using Max Design 2014 and Windows 7 across all workstations & nodes:

The vray spawner's copy of max crashes when rendering via backburner if the scene includes xrefs set to "auto update" and the xref file is saved, causing an update. The host does not crash and the nodes do rejoin the render.

If a job crashes during a render on backburner (and resumable rendering is enabled) the render restarts and resumes but the buckets that were rendering at the time of the crash remain black when the render completes.
As a side note: where is the resumable info stored? Could you make it an editable "sidecar" file so we can set renders for specific buckets?

VrayPhysicalCamera; "auto guess vert tilt" does not update/display if the camera rotation is changed whilst the camera is hidden. This has been there for a few releases.

If you change a vrayies lights intensity value and then undo, the value is incorrectly set to 0 rather than restored.

When using backburner, DR & resumable rendering: if the manager goes down unexpectedly and the job stops, when the job is resumed (assuming the manager automatically comes back online) the nodes do not rejoin.

When you enter creation mode for a VRayIES and uncheck targeted, the light is still created with a target when you click and drag.

Resumable rendering with DR using backburner: If a render starts and completes the light cache, but is suspended before any buckets are rendered; when the job resumes, the buckets are black.

Let me know if you need clarification on any of these or feel free to tell me I am wrong!

Cheers,
Olly

[nikolay.kusht]

Thank you for your feedback. I will try all test cases that you have mentioned and I would report them to our system.

[duke2]

The resumable rendering bugs sound worrying. We were hoping to use it to get around render farm crashes.

[matanov]

A few bugs I have found in the current release of VRay, using Max Design 2014 and Windows 7 across all workstations & nodes:

If a job crashes during a render on backburner (and resumable rendering is enabled) the render restarts and resumes but the buckets that were rendering at the time of the crash remain black when the render completes.
As a side note: where is the resumable info stored? Could you make it an editable "sidecar" file so we can set renders for specific buckets?

When using backburner, DR & resumable rendering: if the manager goes down unexpectedly and the job stops, when the job is resumed (assuming the manager automatically comes back online) the nodes do not rejoin.

Resumable rendering with DR using backburner: If a render starts and completes the light cache, but is suspended before any buckets are rendered; when the job resumes, the buckets are black.

Cheers,
Olly

Where are you writing those files?

The resumable rendering bugs sound worrying. We were hoping to use it to get around render farm crashes.

I've just tried all scenarios (even few more) with BB and DR from the first post and everything worked as expected. Must be something specific in olly's case.

[tarn]

Arch & Design Materials are Black in the Material Editor

I have a file which I imported from Sketchup into Max 2016, so it is full of Arch & Design materials. I noticed that these are showing up as black in the material editor slots with 3.50.04 installed. The interesting thing is that when doing an actual rendering, they rendered properly. I did have V-Ray selected as the render engine for the material editor. I reverted back to V-Ray 3.4 again and the Arch & Design materials display normally again. Has anyone else had this problem? I posted this same problem about the 3.5 Beta, but I never found a solution, so I am asking again.
Tim

[REDVERTEX]

Should we expect a stable bug fix release newer than 3.50.04 ?

[alexander.kazandzhiev]

Hello, our current effort is towards releasing 3.60.

Best regards,
Alexander

[olly]

Where are you writing those files?.

Our renders are saved to a mapped drive that all nodes have write access to.

I will test these bugs again to verify they are reproducible in our environment and not scene specific.