Stability and usability

I feel like the last 6 months working with VRay has become, for me, less and less productive, while becoming more and more frustrating. I’ve been putting off posting a thread like this for a while, but I think it’s time.

The way I work means the production renderer itself is great, it’s using RT or IPR in early project phases when my problems begin. Without an interactive/realtime option, my job would be much more difficult I admit, so thanks for the effort on that front, but after trying out a competing product recently, it makes VRay look dated and unstable in the area of interactivity. Even as I’m writing this, im suffering constant crashes and instability. It’s really quite astounding when you take a step back and think about how much time is wasted on this.

- IPR I find to be very unstable and prone to crashing max, and without support for atmospheric effects it becomes for me, almost completely useless. A robust, fully working version of IPR is the dream.
- Having to switch between GI engines, and image samplers becomes a pain in the bum. BF+LC+progressive is my setup for IPR, but not for production for example.
- Speaking of random issues, see the attached image. This is the first time I’ve ever seen this (forest pack showing up as the display proxies). Refresh interactive rendering button doesn’t fix this.
- Hiding a layer…maybe not now, maybe not in 10 minutes, but at some point it WILL crash max. How can one report such inconsistent bugs?

- RT is even more painful to use. I would not use it, but the instability and lack of atmospheric effects in IPR means I always roll back to RT (cpu). I find RT to be such a mixed bag as to make bug reporting pointless. For one I find it to be slower than competitor’s interactive offerings; perhaps not in brute speed, but in how much time is spent starting, stopping, crashing, etc etc etc.
- Somethings prompt an RT update, others don’t. Using the re-initialize function doesn’t seem to do anything, so a full scene recompile and waiting for RT to get up and running again is required every 5 minutes or so,
- Sometimes I get a total max lockup when an RT session is ended, requiring me to close the max session in Task Manager
- Changing the FOV using the UI shortcuts (bottom right of screen) doesn’t prompt an update.
- Atmospheric effects cannot be enabled or disabled, they must be deleted or RT restarted in order to switch them on or off.
- These RT errors that request a restart of max are so painful.

Some other things
- The new Physical Camera and exposure system is a joke. Please give us back the old system.
- Lens effects are confusing and aren’t user friendly. Why does using glare seem to totally disable bloom effects?
- LUT support is, while “correct”, not lending itself to creative use so I’ll ask again: please give us an opacity slider/spinner for LUTs in the VFB.
- Filmic tonemapping options. Again, perhaps this sort of thing isn’t “correct” but using the curves adjustments in the VFB is fiddly and frustrating. I know you don’t want to hear me compare VRay to other engines, but Corona’s VFB allows me to make a hard-sun daylight image look far far more realistic straight out of the VFB than VRay can, or at least with much less effort and fiddling. It seems like it’s a taboo to compare VRay to Corona on the forums, but let’s be honest here; they’re doing amazing things with such a comparatively small team.
- Does denoising work for render elements yet? I can’t seem to get a denoised reflection element.
- Bump and Normal mapping seems weak in comparison to Corona.
- The Vray2sidedmaterial just can’t cut it for nice looking foliage. Wasn’t a specific shader spoken of many moons ago?
- Make it possible to save an EXR from the frame buffer save button with all channels included. Currently only possible from the render setup window. (Update: possible to do so)
- Vrayaerialperspective is so good, but the way it affects passes other than RGB requires a second render just for clean passes.
- Clarify how VFB adjustments affect which passes saved from the VFB. Some are affected, some aren’t? Who knows?
- Implement a way to lock which view of RT and IPR is being rendered.
- CIE Overcast: I would be nice to have directional brightness based on sun position. At the moment it’s a pretty useless sky model. I use a desaturated CIE Clear as a workaround which isn’t desirable.
- Hosek sky. Love it, but really need brightness controls for better creative control.
- We can filter the sun color, but can we please have the option of tinting the sky too. Not with extra nodes and color correction workarounds.
- Add the ability to hide some objects from Wirecolor pass. This will aid masking of objects behind glass. Otherwise I end up with messy reflection passes, or on the other had I must re-render just for a second set of masks.
- Let’s be honest, Corona’s lightmixer is a remarkable tool, and I think anyone that has tried it, would love this sort of feature in Vray.

As much as some like to throw around numbers versing one engine to another and how VRay is fastest, it’s not about that for me. It’s about usability in the real-world. Day to day. Not a teapot in a room with a simple light. I’m talking about millions of polys, hundreds of lights, tens of thousands of proxies and whatnot. VFB control that allows for creativity, not refusal by Chaosgroup because it’s not “correct”. If we just follow the rules, we’ll never create the next best image. Give us the tools and control we need to create the imagery we want to. Honestly I would rather sacrifice 10% of VRay’s speed if only it was more stable and useable.

Using win 7, max 2016 and various versions of Vray both nightly, stable and official releases since the start of the year; all of these problems have persisted.

Anyway have a good weekend, and if I’ll update if more things come to mind.

- James

All valid points except for the two below (that I know of):

You can save a multichannel exr by selecting the third/bottom icon in the save image dropdown button and select “Save all image channels to a single file”

You can lock the view for IPR (haven’t tried in RT) by using the lock icon next to the “View to Render” list the Render Setup dialog.

I do wish IPR was a little more stable though. It just means a lot of saves which can be slow once the scene gets complex.

Thanks for the feedback; some comments are below.

What are your production settings? There is an option to force progressive rendering for IPR (it is enabled by default) so even if your production renderer is set to use buckets, the IPR will still be progressive. What other settings are different between IPR and production rendering?

- Speaking of random issues, see the attached image. This is the first time I’ve ever seen this (forest pack showing up as the display proxies). Refresh interactive rendering button doesn’t fix this.Forest pack issues are unfortunately as much on the Itoo side.

- Hiding a layer…maybe not now, maybe not in 10 minutes, but at some point it WILL crash max. How can one report such inconsistent bugs?It is enough to mention that there is a problem. If it is not easy to reproduce, we will find a way to track it down.

- Sometimes I get a total max lockup when an RT session is ended, requiring me to close the max session in Task Manager.It would be useful if you can get us a crash dump from the 3dsmax.exe process at that time.

- Changing the FOV using the UI shortcuts (bottom right of screen) doesn’t prompt an update.This is known and will be fixed.

- Atmospheric effects cannot be enabled or disabled, they must be deleted or RT restarted in order to switch them on or off.Will check this out.

- The new Physical Camera and exposure system is a joke. Please give us back the old system.All the old stuff is there and you can still use it.

- Lens effects are confusing and aren’t user friendly. Why does using glare seem to totally disable bloom effects?They are both mixed together depending in their weights. They are not additive.

- Does denoising work for render elements yet?Nope.

- Bump and Normal mapping seems weak in comparison to Corona.Can you give an example?

- The Vray2sidedmaterial just can’t cut it for nice looking foliage. Wasn’t a specific shader spoken of many moons ago?I still stand by my opinion that the 2-sided material works in a realistic and physically plausible way. A specific shader may or may not be coming, but not as part of V-Ray 3.x

- Make it possible to save an EXR from the frame buffer save button with all channels included.Press the Save button and hold it down; it will expand into a flyout. Select the last button to write a multichannel OpenEXR file.

- Implement a way to lock which view of RT and IPR is being rendered.The regular camera locking from the render setup should work fine.

- CIE Overcast: I would be nice to have directional brightness based on sun position. At the moment it’s a pretty useless sky model. I use a desaturated CIE Clear as a workaround which isn’t desirable.It’s a standard model required for lighting analysis.

- Hosek sky. Love it, but really need brightness controls for better creative control.You can pass the sky texture through any color corrections that you wish.

- We can filter the sun color, but can we please have the option of tinting the sky too. Not with extra nodes and color correction workarounds.I don’t think so… extra nodes give you so much more flexibility.

- Let’s be honest, Corona’s lightmixer is a remarkable tool, and I think anyone that has tried it, would love this sort of feature in Vray.V-Ray 3.x will not have a light mixer. However, the 3.6 update will give you a full light select render element that contains the entire contribtion of light sources.

Best regards,
Vlado

Thanks! I only tried locking with RT and that didn’t work.
And thanks for the exr hint. Updated post.

+1000
Man I love you!!
you summed up everything I dream of!
​​​​​V-Ray is fast, quite fast actully. It is just those little things that would make our life easier.

Do you still have the .dmp file created? Another option is to generate them with Process Explorer (in which case you can also select a mini-dump which is much smaller and should be created without problems).

It would be very useful for us to have that file, so thanks for the effort!

Best regards,
Vlado

You know what it did actually write the dmp file. In this case I had a camera correction modifier on a physical camera which seems to have made the scene hang on ‘translating verticies’ indefinitely. Do you want that dmp file, or is this a max problem?

Hm, is that a repeatable issue? Yes, I would like to have the .dmp file, thanks! You can send it to vlado@chaosgroup.com

Best regards,
Vlado

Hrmmm I guess it’s somewhat repeatable; it wasn’t happening on friday, but now it’s happening so I’ll try to get it to happen and send a dmp file later today.

Ok it’s repeatable; max 2016 sp4, create physical camera, add camera correction modifier, turn the modifier off, render and it gets stuck on transforming vertices.

I sometimes try to get the same error on my workstations when people post stuff like this but I am getting the same “freeze” doing what you are describing. 3dsmax 2016 SP3 EXT2, V-Ray 3.50.04

I mean we should be using the corrections inside the camera itself, but it’s a bug nonetheless… I was merely a force of habit that I used the modifier.

I am using it more and more and am enjoying more and more. I have gotten into the habit of saving first when I know I will be using it for an extended period of time or will be doing a lot of edits.

One thing I’d love to have is for the IR to STOP automatically when the VFB is closed. Too many times I have closed the VFB, forgetting to stop the IR then some time later opening the VFB again only to find that its been running the whole time.

Describe “convenient workflow” :slight_smile:

It will be fixed, thanks!

I’m agree with you ! I work in the same way and I have to say, that changed a lot of thing for me…
Also agree with the fact that when you close VFB, it should stop IPR. Thanks for the fix !

Only had 5 mins to do this, so it’s not a great test.

I’ve attached a scene rendered more or less the same with corona and vray. To my eyes the Vray bump in incorrect and less sharp.

Obviously the lights are a bit different but that doesn’t change the fact that they are shading differently and in my opinion, confirm my suspicions.

First is the scene layout from above, second is the Corona render, and last is Vray.



You didn’t post a scene, so can I ask you repeat the test with a VRayColor2Bump texture?

In any case, keep in mind that bump mapping is a cheat. There isn’t a “more correct” way to do it.

Best regards,
Vlado

I think I should the light in a different position so it’s a more obvious test. I’ll do that, try it vs. displacement, and come back you, possibly eating my words.