V-Ray 3.5 Beta Feedback

[stevejjd]

Hi,
I didn't know where to post feedback so I'll just continue to add my feedback to this 1 thread. (These are not complaints, but constructive feedback)

Feedback items

1. Interactive Rendering with region render.
With a scene set up for lookdev rendering, hit the Interactive Render button. Let it render for a few seconds, then select the "Region Render" icon and select a small square. Notice that the IR doesn't update the selected region?. IR should respect the Region Render and update where ever you place a rectangle. Having to stop then restart to respect the region is not so efficient as it has to re-render as apposed to continue the render with respect to the new region.

2. Interactive Rendering and Render Engine Changes.
In general the settings for the V-Ray render engine will not update with Interactive Render (The resolution is one specific example). It would be great to have render engine parameters, including render passes to be live with IR. - anything to remove stoppages is a must for truly seamless IR.

3. Interactive Rendering - Layers
Consider a scene with multiple objects sorted with the layer explorer. If I star the interactive render, then try to un-hide objects in the layer explorer, the IR will not update. Objects on visible layers cannot be hidden without restarting the IR.

4. Interactive Render - Refresh button
I just wanted to quickly note that the refresh button does clear a lot of issues but I think the goal should be unimpeded, completely fluid updates. The experience should be 100% fluid with no stoppages. The refresh button should only be used as a debugging tool. I want 3ds max to match and exceed the experience I had with Maya IPR. The refresh button does not clear the render region update problem.

5. Interactive Rendering - Lock Camera
Take a basic model, have it lit and shot with a camera. Lock the render to the camera and start the IR. Now click perspective view port and try to interactively model. The Interactive render will follow any viewport that is in focus instead of locking to the camera. I wish to lock the render to a camera and see modelling updates as I actively use the perspective view-port.

6. VRayDirt - Ambient Occlusion - faceted effect
Consider a scene with cylinders intersecting....like welded pipes. you could also add a sphere to help illustrate the point. Place a Vray Dirt material into the diffuse so that occluded areas are black and unoccluded are white. Notice that the object appears to be faceted? Not add subdivision to the models with open subdiv and the facets simply become more fine rather than being smooth? - I would like the AO dirt to be smooth as the surface of the model is smooth.


to be continued

[vlado]

Yup, these are all known and most of them will be implemented for beta 2. The Refresh button will eventually go away, it was mostly there for debugging purposes.

Best regards,
Vlado

[Vizioen]

I have a few little one to add to IPR, but not sure of it's possible because "other renderers" have this issue as well, but there's a reason I stay with Vray . Is there a list of things supported so we don't keep repeating stuff you already know or are planning to fix?

IPR:
1. The (guess vertical) shift from camera isn't propagated to the VFB
2. Changing things in the color mapping requires a refresh
3. Changing override mtl (exclude,..) requires restart

Other:
1. Adaptive lights. There's still a spinner from probabilistic lights active when you choose adaptive. Unless it really interacts with the adaptive light mode?

To be continued as well.

[vlado]

I missed the vertical shift thingy, thanks for the pointer! I know about the rest and they will be added for beta 2.

For the adaptive lights, the value does affect the calculations. See the explanation here:
https://labs.chaosgroup.com/index.ph...aptive-lights/

Best regards,
Vlado

[Vizioen]

Has the vraylightmtl GI contribution been disabled now?

[LudvikKoutny]

For the adaptive lights, the value does affect the calculations. See the explanation here:
https://labs.chaosgroup.com/index.ph...aptive-lights/

Best regards,
Vlado

Hi, does this mean we have to use BF+LC to take advantage of adaptive lights? The guide says that adaptive lights rely on LC pass, but I have quite a few scenes where I use BF+BF.

[vlado]

Hi, does this mean we have to use BF+LC to take advantage of adaptive lights?

For the moment, yes.

The guide says that adaptive lights rely on LC pass, but I have quite a few scenes where I use BF+BF.

The adaptive lights are only possible because of the additional information gathered during the light cache pass, so for BF+BF V-Ray will switch to uniform probabilistic lights. There are a lot of improvements that can be done in that mode too, but not for 3.5 yet... however even when we do that, the adaptive lights are very hard to beat with any other algorithm.

Best regards,
Vlado

[khoross]

been noticing huge increase in performance with some scenes, it really feels like a nitro boosted version of Vray.
good Job

[stevejjd]

Thanks Vlado,
I thought that your team would be on top of this and at the same time I wanted to try and help too

Thank so much for being committed to creating an awesome renderer made for artists. I feel Like V-Ray is part of this massive surge towards a future where 3D art is more about the choices you make rather than fighting the technology all the way to the finished expression or creative intention.

I always felt like I had to become some kind of socially retarded, polymath, idiot savant who has to master 10 different disciplines just render something that looks beautiful. These days will soon be over as software becomes more transparent. I think we are all charged with excitement for the future of V-ray!

Both CG software in general and specifically V-Ray are becoming so much better, friendlier and faster!

I should have welcomed others to add their beta testing feedback here. Please do, if your seeing this thread.

[Alex_M]

I'm curious. Can you post some render times for comparison?

Thanks

[khoross]

I should have welcomed others to add their beta testing feedback here. Please do, if your seeing this thread.

thank you for starting a feedback thread, was searching the forum for a such thread,
i am using the beta for a current job and was noticing also the same issues that you mentioned, but after i've finished setting up the scene and lighting and was using it mainly just for final render, i was surprised with the render times.

i don't have render times comparison, these are scenes done completely with 3.5 beta and alot of the materials are GGX with frensel glossy, and my impressions are based on what i've grown to expect certain problematic lighting situations or materials at render times.

[chris-x//]

Launching a render with license server off will result in an immediate max crash. Before it was just an error.
With server running, obviously no problem

[vlado]

Launching a render with license server off will result in an immediate max crash. Before it was just an error.

Thanks for the pointer; it's already fixed for beta 2.

Best regards,
Vlado

[Alex_M]

So are there any general speed improvements for this SP? I'm tempted to use the beta for a commercial job here. It will be a good test in a real-world scenario. The question is, is it stable enough or I shouldn't risk it on commercial projects?

[vlado]

So are there any general speed improvements for this SP?

Beyond the adaptive lights we are making more use of SIMD instructions in the code which usually reduces the render times a bit.

I'm tempted to use the beta for a commercial job here. It will be a good test in a real-world scenario. The question is, is it stable enough or I shouldn't risk it on commercial projects?

It might not be a good idea to risk a project because of the beta. It would be nice if you can see how it works, but maybe keep the official build around just in case.

Best regards,
Vlado