V-Ray Next Update 3 available for download

[Muhammed_Hamed]

What do you mean?

probably the bump delta scale issues
https://forums.chaosgroup.com/forum/...-biggest-issue

[Vizioen]

probably the bump delta scale issues
https://forums.chaosgroup.com/forum/...-biggest-issue

Indeed, but I also remember bump creating faceting or a hard shadow edge, although I remember that was solved but some people still had similar issues under some circumstances.

[matanov]

Indeed, but I also remember bump creating faceting or a hard shadow edge, although I remember that was solved but some people still had similar issues under some circumstances.

The hard shadow edge should be resolved, I'm not aware of any more issues related to it.

The bump delta scale issue it's being worked on for months and I guess will be included in one of the next releases. It's not a trivial one so it needed a lot of research since the solutions in the other renderers are not ideal.

[rudolfb]

Keep in mind that the first time you launch the RTX engine (per new build/driver) you wait 45 seconds on average for kernel compilation per GPU.

I've done some further testing and the RT engine is still consistently slower than the CUDA engine (not by a major amount but still), if its not meant to be quicker as such or even on par then its not a problem but my understanding was that it would be quicker ?

[matanov]

It's heavily dependent on the scene but yes - it shouldn't be slower. Please send me such scenes so we can check if we can improve it on our side.

[JezUK]

I ran a test yesterday and my render times went up from 4m16s to 4m54s......

Progressive Rendering VRay-Next (not GPU).

[JD3D_CGI]

I ran a test yesterday and my render times went up from 4m16s to 4m54s......

Progressive Rendering VRay-Next (not GPU).

Then this is completely bizarre, since you're not rendering with your GPU.

RTX rendering is a subset of GPU rendering that works on RTX cards. It doesn't work with CPU rendering.

[JD3D_CGI]

I think I have just spotted a big with the LIGHTCACHE PRESET animation/still preset (gpu)

Whatever you select on the drop-down, it just toggles between to two options.

So if I have it set to animation, click the dropdown and select animation, it will toggle to still and not stay/select animation.

Also, I don't know if this is a big or a feature, but if I select animation, then edit the settings, selecting the default goes back to what I had set for the the animaiton.

So if I select animation then set the subdivs to 5, when I select animation again, it shows my subdivs as 5, not as whatever your default is.

In fact, it's giving bizarre results and getting them confused now. You might want to look at this.

[matanov]

I think I have just spotted a big with the LIGHTCACHE PRESET animation/still preset (gpu)

Whatever you select on the drop-down, it just toggles between to two options.

So if I have it set to animation, click the dropdown and select animation, it will toggle to still and not stay/select animation.

Also, I don't know if this is a big or a feature, but if I select animation, then edit the settings, selecting the default goes back to what I had set for the the animaiton.

So if I select animation then set the subdivs to 5, when I select animation again, it shows my subdivs as 5, not as whatever your default is.

In fact, it's giving bizarre results and getting them confused now. You might want to look at this.

Keeping set values between modes is on purpose. You can always right-click on the spinners to set them on default values (as almost every V-Ray related setting that has a default value).

We will fix the first one.

[yeoldewolfe]

Hello, been testing another scene with RTX and it consistently crashes, works fine on CUDA. Is there a specific email we should send our scenes to for analyzing the problem?

Thank you

[JD3D_CGI]

Keeping set values between modes is on purpose. You can always right-click on the spinners to set them on default values (as almost every V-Ray related setting that has a default value).

We will fix the first one.

Nice one.

Also, so far, every scene I have tested is slower using the lightcache animation preset than brute force.

Do we have to mess about with "single frame" or fly through and precalculate things like the old days?

[JezUK]

Then this is completely bizarre, since you're not rendering with your GPU.

RTX rendering is a subset of GPU rendering that works on RTX cards. It doesn't work with CPU rendering.

It isn't unknown to affect one area of software whilst attempting to enhance/fix another.

Ask AutoDesk, they're the leading experts at that kind of thing

[vlado]

Hello, been testing another scene with RTX and it consistently crashes, works fine on CUDA. Is there a specific email we should send our scenes to for analyzing the problem?

Please send it to support@chaosgroup.com

Best regards,
Vlado

[vlado]

Also, so far, every scene I have tested is slower using the lightcache animation preset than brute force.

The light cache simulates many light bounces (~100), I'm curious if you get faster brute force with the same number of bounces?

Do we have to mess about with "single frame" or fly through and precalculate things like the old days?

No, there shouldn't be to mess with anything, the defaults should work fine.

Best regards,
Vlado

[vlado]

It isn't unknown to affect one area of software whilst attempting to enhance/fix another.

In this case they are really unrelated pieces of code. In my tests, there isn't a significant difference in render times on the CPU between update 2 and update 3, but I'd be curious to take a look at any scenes that show such a slowdown.

Best regards,
Vlado