Tweet
Hi,
I've decided to make my general thread about things that do not work or work differently in V-Ray RT, where I will be all of them in one place.
I have to say I am a bit disappointed with V-Ray RT. It's been quite a few years, and it's still so far from production ready. Not only that, but it's mainly very dangerous to use for any kind of look development, which is unfortunate, as look development is a main point of using interactive rendering anyway. Any attempt of lookdev, shading or lighting, will always sooner or later result to completely different output with regular V-Ray ADV renderer.
Sometimes because part of something you are tweaking does not have any effect, which you do not notice, and it will then show up as major difference in final rendering. Other times something will just fail to update. Regardless of which one it is, any inconsistency will always result in lots of wasted time and work because it's usually lot easier to re-do everything from scratch than try to reverse-engineer which one of the knobs or inputs does not work or fails to update.
So it is unsettling, that V-Ray RT fails the most at something interactive renderers are actually meant to be for - look development. It feels like interactive rendering is one of the areas where V-Ray falls quite far behind its competitors.
Now that the rant is over, let's get to the first batch of issues (Max 2016 SP2 + V-Ray 3.30.03):
1, Color Mapping curve breaks HDR/EXR environment maps in V-Ray RT
I often use Color Mapping curve in output rollout to for example reduce dynamic range of an environment map to dim the sun. It works perfectly in V-Ray but breaks environment in V-Ray RT.
Here is the video showcasing the problem: https://youtu.be/iPSQZA1zl4s
Here is a link to the scene: https://dl.dropboxusercontent.com/u/...iro_CCurve.zip
2, This scene contains two bugs:
A, In a simple shading network, plugging and unplugging nodes does no update in RT as long as any map parameters are not changed. This is one of those things where you can tweak something for dozens of minutes and scratch your head why isn't it working, then you run production renderer and you see something totally different.
B, Regular native Noise map, probably the most used procedural map inside of 3ds Max, has completely different output in V-Ray RT compared to V-Ray. So if you do any kind of lookdev using that map, it will come out totally different in production renderer.
Video showcasing the problem is here: https://youtu.be/qcx62RjxQsY
And link to the scene is here: https://dl.dropboxusercontent.com/u/...ffMixNoise.zip
I will keep posting more as i find them.
I've decided to make my general thread about things that do not work or work differently in V-Ray RT, where I will be all of them in one place.
I have to say I am a bit disappointed with V-Ray RT. It's been quite a few years, and it's still so far from production ready. Not only that, but it's mainly very dangerous to use for any kind of look development, which is unfortunate, as look development is a main point of using interactive rendering anyway. Any attempt of lookdev, shading or lighting, will always sooner or later result to completely different output with regular V-Ray ADV renderer.
Sometimes because part of something you are tweaking does not have any effect, which you do not notice, and it will then show up as major difference in final rendering. Other times something will just fail to update. Regardless of which one it is, any inconsistency will always result in lots of wasted time and work because it's usually lot easier to re-do everything from scratch than try to reverse-engineer which one of the knobs or inputs does not work or fails to update.
So it is unsettling, that V-Ray RT fails the most at something interactive renderers are actually meant to be for - look development. It feels like interactive rendering is one of the areas where V-Ray falls quite far behind its competitors.
Now that the rant is over, let's get to the first batch of issues (Max 2016 SP2 + V-Ray 3.30.03):
1, Color Mapping curve breaks HDR/EXR environment maps in V-Ray RT
I often use Color Mapping curve in output rollout to for example reduce dynamic range of an environment map to dim the sun. It works perfectly in V-Ray but breaks environment in V-Ray RT.
Here is the video showcasing the problem: https://youtu.be/iPSQZA1zl4s
Here is a link to the scene: https://dl.dropboxusercontent.com/u/...iro_CCurve.zip
2, This scene contains two bugs:
A, In a simple shading network, plugging and unplugging nodes does no update in RT as long as any map parameters are not changed. This is one of those things where you can tweak something for dozens of minutes and scratch your head why isn't it working, then you run production renderer and you see something totally different.
B, Regular native Noise map, probably the most used procedural map inside of 3ds Max, has completely different output in V-Ray RT compared to V-Ray. So if you do any kind of lookdev using that map, it will come out totally different in production renderer.
Video showcasing the problem is here: https://youtu.be/qcx62RjxQsY
And link to the scene is here: https://dl.dropboxusercontent.com/u/...ffMixNoise.zip
I will keep posting more as i find them.
Comment