V-Ray 3.0 for 3ds Max Beta Open!

[askhamdesign]

@Spip

Can you in 32 bits substract them from each other and show us the result? I’m curious as to differences.

Thanks, bye.

Sorry Dadal I do not understand quite what you mean?

[vlado]

@3DKodo

Don’t think I used the Embree thing??

Then it would be interesting to try it See here: http://help.chaosgroup.com/vray/help/300R1/render\_params\_system.htm#embree

Be interesting to see if gpu speeds would be similar?Yep, me too

Best regards,
Vlado

[Dariusz_Makowski_Dadal]

Take both of the renders in 32 bit in photoshop. Put them 1 above another and set the top one to Substract. Then show us the (I hope)Fully black image if no show us what there is. This will show us how different are the renders.

[savage309]

@3DKodo

I use opened up that basic scene that I use to test materials and sent it via network render to one of my machines, rendered the same scene x3 times to check the times were consistent. Don’t think I used the Embree thing?? Be interesting to see if gpu speeds would be similar?

Don’t expect speed improvements on the GPU (at least not yet).
However, there are new stuffs supported (render elements, procedural noise and others).

Best,
Blago.

[raymarcher]

With the VRmat materials, does this open the door for Chaosgroup to develop Vray native procedural maps like for example, Vray color correct, VrayNoise, VrayGradient, VrayTile, etc. ?

[vlado]

Here are some quick differences, but I used directly the images from the web site, so I don’t know how valid this is (good that they are PNGs).

As you can see, there are some differences. I expect there to be - so much code has changed and the noise is also very likely to be different. Still, seems very close.

Best regards,
Vlado

[askhamdesign]

@Guest

Then it would be interesting to try it See here: http://help.chaosgroup.com/vray/help/300R1/render\_params\_system.htm#embree

Yep, me too

Best regards,
Vlado

I shall give it a try and post results!

[Dariusz_Makowski_Dadal]

Heya

Thanks, well 8 bit image is really bad to do it on but o well

[vlado]

@snivlem

Thanks, well 8 bit image is really bad to do it on but o well

Yep, I agree. Hopefully Simon will get to do proper 32-bit ones.

Best regards,
Vlado

[kosso_olli]

@sebastiaaan

The speed increase on the glass render is unreal!

The 3.0 render has a lot more noise than the one from 2.4. You can clearly see that on your images.

[vlado]

@DrDardis

The 3.0 render has a lot more noise than the one from 2.4. You can clearly see that on your images.

The noise levels are in general different, yes. I’ve tried to explain it here: http://help.chaosgroup.com/vray/help/300R1/migrate\_to\_3\_0.htm#bruteforce

But, on the one hand, in one case you are faced with a 1h render and no way to go lower, and in the other with a 13 minute render with only slightly more noise that you can clean up if you need. People specifically wanted faster glass renders, so I do faster glass renders…

Best regards,
Vlado

[askhamdesign]

I will re-run the glass test to double check!

[kosso_olli]

Oh, okay. Didn’t see it yesterday, sorry. What would be the best way to get the two images to comparable noise levels?

[vlado]

@anchovy

Oh, okay. Didn’t see it yesterday, sorry. What would be the best way to get the two images to comparable noise levels?

Increase the AA settings a bit. That’s all.

Best regards,
Vlado

[kosso_olli]

@stellwagenc

Increase the AA settings a bit. That’s all.

Sorry for the dumb question: Using the new shading rate parameter or via min and max settings?

[vlado]

@DiditzZz

Sorry for the dumb question: Using the new shading rate parameter or via min and max settings?

If it’s not a glossy material, the shading rate will not affect it. You can modify the min/max subdivs (and maybe the color threshold, I don’t know what it is set to in the scene). Basically in the same way you would normally deal with noise in V-Ray.

Best regards,
Vlado

[kosso_olli]

Thanks for the clarification, Vlado. Seems to be easy to clear up the noise, then.

[michaelwbell]

Hi Chris,

Thanks for the reply!

RE: Purchasing a new Vray 3.0 instead of upgrading an exsisting 2.4:

@vlado

Hi Michael,

For us this is not a problem at all - again we are not here to force to do anything, we choose what’s best in your situation.

Here I feel you (wrongly) assume that the compatibility would be 100%… If you use V-Ray 3.0 to create a scene and try to use V-Ray 2.0 to render it (assuming it is really possible), you might face some serious compatibility issue.
The opposite is more likely to supported. And you are right to mention that the base cost of a new V-Ray license is going to be cheaper
Ultimately every user have different situations and concerns. If in your case the option to buy V-Ray now and receive the free upgrade to V-Ray 3.0 with 3x RN sounds a better deal, then we would be more than happy to help you in this process.

Wow. This is pretty crazy! I do struggle to think why anyone would want to upgrade now! I will definitely buy a new 2.4 licence in this case (for the free ugprade path). The current 2.4 → 3.0 upgrade is a definite ‘downgrade’.

But a new Vray 3.0 with the 3 render nodes sounds ace. Great!

[Mokiki]

Thanks for those render tests @ askhamdesign. But I’m confused wasn’t the render speed increase supposed to be brute force only? So why the big increase with using IR as primary solution? (Not that I’m complain)

[vlado]

@vlado

Thanks for those render tests @ askhamdesign. But I’m confused wasn’t the render speed increase supposed to be brute force only? So why the big increase with using IR as primary solution? (Not that I’m complain)

The changes affect other situations too, not only and specifically brute force - although they are indeed more apparent if you use brute force, especially with lots of bounces.

Best regards,
Vlado