Collected Issues/Bugs/Oversights in V-Ray 5 (will be updated)

[PdZ]

Windows 10 Pro
Version: 10.0.19042 Build 19042
Cinema 4D R23.110 (Build RB330286)
V-Ray 5 for Cinema 4D, hotfix 1 (v5.00.43 from Feb 11 2021)

CPU: AMD Ryzen 9 3900X 12-Core Processor               3.80 GHz
RAM: 64,0 GB
Graphic: GeForce GTX 1070 Ti
SSD

Hi all,

The first time iam working with V-Ray 5 in production. I will post Bugs/Issues along the way and update this thread all the time when I come across a bug/oversight etc.


General:

• [MISSING] V-Ray Material Filter is missing (This is very important)

V-Ray Render Settings:

• [NEW!!!] [OVERSIGHT] Use V-Ray Output System: If Rendering is restarted and theres already the same file there, it will overwrite the file. Theres no warning or "stop before overwriting the file". It simply overwrites the old file. This is highly dangerous in my opinion.
• [NEW!!!] [OVERSIGHT] Use V-Ray Output System: If Rendering is started and the output-path does not exist, no warning is given. Nothing is happening. This is highly dangerous in my opinion.

V-Ray Material-/Scene-Converter when opening 3.7 Scenes:

• [MISSING] Converter Popup doesnt show up on scenes which has no V-Ray Rendersettings enabled. You have to do it manually by using "Convert V-Ray 3 Scene" in "V-Ray -> Tools"
• [MISSING] Old V-Ray Proxy Conversion Support. When opening 3.7 Scenes with V-Ray Proxies they are not supported. I know the Proxysystem is different know. Are old VrMeshes supported? If yes: a Converter would be great. If not this would also be horrible. How do we know how long something is supported? Currently my whole library with 3.7 Materials and 3.7 Proxies seem not to be fully supported/converted right.

Cinema 4D Cloner:

• [BUG] If the Cloner is set to "Render Instance" and also there is an instance as child of a cloner which also set to "Render Instance" Interactive Renderer positions the clones anywhere else. (I know there is nothing like render instanced render instances. It was a fault of mine) but Cinema 4D Viewport and Renderer is rendering fine even with this. If Cloner is set to "instance" and child-instance to "render instance" it works.
• [BUG] If theres a Cloner with Render Instances and the original object in a group but not the original object is textured, instead the Group which has Cloner, Instances and the original object is mapped/textured: Texture glitches are happening

V-Ray Material:

• [BUG] After copying one specific Material, changing name and adding an opacity Map -> Console popped up -> V-Ray was spamming: "No another preview could be created" "New Preview is not allowed". It constantly spammed this in the console. After deleting this material everything was fine. Preview was not generated as V-Ray said. After restarting Cinema and reloading the scene it was "fixed". Preview was also generated. Very weird bug.

V-Ray Camera-Tag:

• [MISSING] Settings are not undoable
• [OVERSIGHT] Focal Length (mm): When creating the Camera-Tag its set to 36. But if you set it to "Default-Value" it is set to 40

V-Ray Interactive Rendering:

• [NEW!!!] [BUG] The Interactive Renderer in general is extremely buggy, Cinema crashes often/hangs. It happens when doing random things. I cant even tell what is causing this. It seems its very sensitive to anything. Currently C4D freezes when I just clicked on Cameratag while interactive was rendering.
• [MISSING] V-Ray Material -> Options -> Round Edges Enabled: Not changing in Interactive Rendering. You have to restart Interactive Rendering to see the effect

V-Ray Sun:

• [MISSING] Sun-Direction-Indicator is missing. In C4D and 3.7 you had an Indicator which shows you in which direction the sun is pointing
• [MISSING] or [BUG] In the Cinema 4D Viewport -> Options -> Shadows: Are not shown

V-Ray Frame Buffer:

• [BUG] Options -> History -> Location: Use Project Path is not working

[shaio]

Hey PdZ ,
thank you for the feedback. I'll address all of it in a moment, but before that I would recommend downloading the latest stable build from our Nighties Server since it includes some resolved issues since the latest official release on Feb 11 that you're currently using.

[shaio]

[NEW!!!] [MISSING] V-Ray Material Filter is missing (This is very important)

I'll add a feature request about this since it is indeed very useful to have a filter for the materials. Thanks for the suggestion.

[NEW!!!] [BUG] After copying one specific Material, changing name and adding an opacity Map -> Console popped up -> V-Ray was spamming: "No another preview could be created" "New Preview is not allowed". It constantly spammed this in the console. After deleting this material everything was fine. Preview was not generated as V-Ray said. After restarting Cinema and reloading the scene it was "fixed". Preview was also generated. Very weird bug.

Is this something that is reproducible consistently on your end? This is a known issue and very random to reproduce, and I can't reproduce it with the steps provided by you as well.

[MISSING] Sun-Direction-Indicator is missing. In C4D and 3.7 you had an Indicator which shows you in which direction the sun is pointing

This is because the V-Ray lights are now separate objects. In 3.7 All lights were tags attached to a Cinema 4D light therefore the preview was actually coming from the Cinema 4D Direct Light. I'll add a feature request, so we can improve this for the sunlight in the future.

[MISSING] or [BUG] In the Cinema 4D Viewport -> Options -> Shadows: Are not shown

This is related to the previous issue above. The shadows and lighting from inside the Viewport in 3.7 were actually produced by the Cinema 4D Light object. Now when the Lights in V-Ray 5 are separate objects not a tag they don't emit any light in the viewport. Viewport previews for lights and materials would require a lot of development time and are not with a top priority for now. We will improve this in the future as soon as we catch up with most of the missing features from V-Ray 3.7.

V-Ray Camera-Tag:

• [MISSING] Settings are not undoable

Some of them are undoable because of their direct connection with the same parameter inside the Cinema 4D camera. I'll check this and report it for fixing.

[OVERSIGHT] Focal Length (mm): When creating the Camera-Tag its set to 36. But if you set it to "Default-Value" it is set to 40

I'll check and report this for fixing as well. Thank you for the feedback.

Let me know if you have more questions.

[PdZ]

Is this something that is reproducible consistently on your end? This is a known issue and very random to reproduce, and I can't reproduce it with the steps provided by you as well.

unfortunately not. Thank you for your feedback!

[PdZ]

V-Ray Material-/Scene-Converter when opening 3.7 Scenes:

• [NEW!!!] [MISSING] Converter Popup doesnt show up on scenes which has no V-Ray Rendersettings enabled. You have to do it manually by using "Convert V-Ray 3 Scene" in "V-Ray -> Tools"
• [NEW!!!] [MISSING] Old V-Ray Proxy Conversion Support. When opening 3.7 Scenes with V-Ray Proxies they are not supported. I know the Proxysystem is different know. Are old VrMeshes supported? If yes: a Converter would be great. If not this would also be horrible. How do we know how long something is supported? Currently my whole library with 3.7 Materials and 3.7 Proxies seem not to be fully supported/converted right.

[deyan.hadzhiev]

Hi PdZ, the scene converter popup may not show if it does not detect render settings from V-Ray 3.7, although I think we should extend this condition to check the materials as well. Until we manage to change that, you can manually trigger the conversion from the explicit command in the V-Ray menu:

[PdZ]

Hey PdZ ,
thank you for the feedback. I'll address all of it in a moment, but before that I would recommend downloading the latest stable build from our Nighties Server since it includes some resolved issues since the latest official release on Feb 11 that you're currently using.

Hey shaio is it possible to tell me which issues are resolved? Dont wanna test all the issues again. I installed the new hotfix 2 yesterday. I assume this is the latest release.

Thx in advance!

Hi PdZ, the scene converter popup may not show if it does not detect render settings from V-Ray 3.7, although I think we should extend this condition to check the materials as well. Until we manage to change that, you can manually trigger the conversion from the explicit command in the V-Ray menu:

Hey @deyan,

Thx. I will test that as soon as I arrive at work in a few minutes. Thank you.

[shaio]

Hey shaio is it possible to tell me which issues are resolved? Dont wanna test all the issues again. I installed the new hotfix 2 yesterday. I assume this is the latest release.

The changelog for Hotfix 2 is posted in this topic: V-Ray 5 for Cinema 4D - Hotfix 2 is now available

[PdZ]

The changelog for Hotfix 2 is posted in this topic: V-Ray 5 for Cinema 4D - Hotfix 2 is now available

Yeah I saw that. But theres nothing mentioned of the issues which I wrote in the thread...

[shaio]

Yeah I saw that. But theres nothing mentioned of the issues which I wrote in the thread...

We released Hotfix 2 yesterday. I hope we don't leave the expectation that we can fix all reports from your or any other post in two days. If there is nothing related to your post mentioned in the changelog this means that either the issue/feature request is not resolved and is planned for resolving based on the other bug reports and feature requests priority.
Whenever we fix something reported on the forums we make sure to update the forum topic and let every one involved know that we've resolved the issue. Or maybe I misunderstood your question, and we're talking about different things.
Let me know if this answers your question.

[PdZ]

shaio dont get me wrong! I know this takes time. I thought you said that some of my mentioned issues are fixed. You wrote it like that might me the case.

Iam looking forward to a great V-Ray 5.

Thank you!

[PdZ]

V-Ray Render Settings:

• [NEW!!!] [OVERSIGHT] Use V-Ray Output System: If Rendering is restarted and theres already the same file there, it will overwrite the file. Theres no warning or "stop before overwriting the file". It simply overwrites the old file. This is highly dangerous in my opinion.
• [NEW!!!] [OVERSIGHT] Use V-Ray Output System: If Rendering is started and the output-path does not exist, no warning is given. Nothing is happening. This is highly dangerous in my opinion.

[PdZ]

V-Ray Interactive Rendering:

• [BUG] The Interactive Renderer in general is extremely buggy, Cinema crashes often/hangs. It happens when doing random things. I cant even tell what is causing this. It seems its very sensitive to anything. Currently C4D freezes when I just clicked on Cameratag while interactive was rendering.