V-Ray 3.30.01 BETA! available for download

[vlado]

Hmm, can you show me a screengrab?

Best regards,
Vlado

[whtnoise]

This might be a bit of a ridiculous question, but what are the chances of vrayClipper and vrayEdgeTexture's rounded corners working happily together?

You know, just to complicate the shit out of everything

Cheers,

Jesse

[Donfarese]

Finally got to try it! but have some issues. I'm using RT, and with the new Beta I cannot get RT to Work. Under cuda it does not show My Cuda Device. I have an AMD as my main GPU and a Nvidia as my secondary compute GPU. The Nvidia GPU is still on driver 353.62 because that was the fastest driver before. Under "Vray RT Render Devices Select" it says "Device name" and that's it, nothing to choose but "Device name". the info box below it says "Environment Variable Vray_Opencl_Platforms_x64 not Found - Using all available devices". Could it be my driver, should I update it? why can I not find my Titanx?

[savage309]

Finally got to try it! but have some issues. I'm using RT, and with the new Beta I cannot get RT to Work. Under cuda it does not show My Cuda Device. I have an AMD as my main GPU and a Nvidia as my secondary compute GPU. The Nvidia GPU is still on driver 353.62 because that was the fastest driver before. Under "Vray RT Render Devices Select" it says "Device name" and that's it, nothing to choose but "Device name". the info box below it says "Environment Variable Vray_Opencl_Platforms_x64 not Found - Using all available devices". Could it be my driver, should I update it? why can I not find my Titanx?

In 3.30.03 V-Ray does not run in a separate process for RT rendering. For some reason however, when 3DS Max starts, it tells (somehow) the operating system that it will use the driver for the main GPU only (in your case the AMD). So V-Ray (and Max, in fact) can't see the Titan. But if you have nVidia GPU for your monitor, you can use as many nVidia GPUs as you like.
Luckily I had the same problem a few weeks ago and I found a couple of other solutions (besides plugin nVidia GPU for main monitor).
1. If you have Titan X, Tesla, Quadro (may work for other game GPUs, but I have not tested), you can do this. This will tell the OS that the GPU will not be used for monitor and just for compute (keep in mind that if you need to use it on the same machine as a monitor, you have to turn off the TCC driver using the same command). Reboot is required, but besides that it works great.
2. If you don't want for some reason to switch to TCC driver (or your GPU is not capable for TCC driver mode) you can navigate to RT install path (default Program Files/Chaosgroup/RT For Max/...) and run "./vray -server". After that you have to choose "Distributed rendering", uncheck use local host and use 127.0.0.1 as IP address. This will make V-Ray to use the RT engine as before (meaning, RT will run in a different process).

[Donfarese]

In 3.30.03 V-Ray does not run in a separate process for RT rendering. For some reason however, when 3DS Max starts, it tells (somehow) the operating system that it will use the driver for the main GPU only (in your case the AMD). So V-Ray (and Max, in fact) can't see the Titan. But if you have nVidia GPU for your monitor, you can use as many nVidia GPUs as you like.
Luckily I had the same problem a few weeks ago and I found a couple of other solutions (besides plugin nVidia GPU for main monitor).
1. If you have Titan X, Tesla, Quadro (may work for other game GPUs, but I have not tested), you can do this. This will tell the OS that the GPU will not be used for monitor and just for compute (keep in mind that if you need to use it on the same machine as a monitor, you have to turn off the TCC driver using the same command). Reboot is required, but besides that it works great.
2. If you don't want for some reason to switch to TCC driver (or your GPU is not capable for TCC driver mode) you can navigate to RT install path (default Program Files/Chaosgroup/RT For Max/...) and run "./vray -server". After that you have to choose "Distributed rendering", uncheck use local host and use 127.0.0.1 as IP address. This will make V-Ray to use the RT engine as before (meaning, RT will run in a different process).

Sorry I'm confused, I have a Titan X, what and how am I suppose to do this TCC thing? through command prompt? run that exe?

[savage309]

Sorry I'm confused, I have a Titan X, what and how am I suppose to do this TCC thing? through command prompt? run that exe?

In the link I posted above there are these instructions (http://http.developer.nvidia.com/Par..._Cluster.htm):

To change the TCC mode, use the NVIDIA SMI utility. This is located by default at C:\Program Files\NVIDIA Corporation\NVSMI. Use the following syntax to change the TCC mode:
nvidia-smi -g {GPU_ID} -dm {0|1}
0 = WDDM
1 = TCC

You can find your GPU ID running nvidia-smi -L

[Donfarese]

Okay got it, gonna try. is there any word on the latest nvidia driver being slower, some drivers where after 353.62

[savage309]

Okay got it, gonna try. is there any word on the latest nvidia driver being slower, some drivers where after 353.62

All latest driver work as expected with 3.30.01, so it is safe to update.

[Jiri.Matys]

I have a problem in 3.30.01 - cant change the option for log window - its grayed out, disabled.

[vlado]

I have a problem in 3.30.01 - cant change the option for log window - its grayed out, disabled.

In 3ds Max 2016 we now use the 3ds Max render messages window, which you can open from the menu Render > Render Message Window... - you can right-click in the window for some options.

Best regards,
Vlado

[Jiri.Matys]

Oh, ok, thanks for that.

[Jiri.Matys]

I make some speed tests in new VRay 3.30 and Forest Pack Pro 5. And its amazing:



First picture: VRay 3.2 + Forest Pack 4.4.1 - 10:44
Second picture: VRay 3.3 + Forest Pack 5 - 5:44 (!!!!!!!)
Third picture: VRay 3.3 with new sky model + Forest Pack 5 - 5:46
Fourd picture: VRay 3.3 with new sky model and caustics + FP 5 - 5:52

Its amazing, how fast is this!

[Donfarese]

Vray Adv. seems like it got quite the boost! awesome. But for Vray RT, I'm getting the total oposite. VrayRT 3.2 21min55sec, VrayRT 3.3 41min and I just stopped it myself, looked like it could of gone on for a long long time more. Whats happening here, I reset Vray too, and entered the setting back it again.

Also Using Titan X in TCC Mode Seems to be a major issue, you can't monitor it's temp, fans, nothing. and You can seem to set fan speed curve profiles, or fan adjustments so that it runs cooler for rendering. What is the solution here? hope it's not just using it as the DR.

[Morne]

Hmm, can you show me a screengrab?

Best regards,
Vlado

Bobby can you show your VFB vs PS please? The one I'm busy with is NDA

[savage309]

Vray Adv. seems like it got quite the boost! awesome. But for Vray RT, I'm getting the total oposite. VrayRT 3.2 21min55sec, VrayRT 3.3 41min and I just stopped it myself, looked like it could of gone on for a long long time more. Whats happening here, I reset Vray too, and entered the setting back it again.

Also Using Titan X in TCC Mode Seems to be a major issue, you can't monitor it's temp, fans, nothing. and You can seem to set fan speed curve profiles, or fan adjustments so that it runs cooler for rendering. What is the solution here? hope it's not just using it as the DR.

The benchmark #2 scene setup for example seems to render twice as slow, compared to 3.20.03. But in fact, because of the many bug fixes, the result in 3.30.01 is completely different - much more GI, much more light inside the scene, more reflection and refraction bounces. So the render speed for the benchmark scene is in fact the same, there are just more rays and the result is quite different and more accurate. If you want to have the same result as in 3.20.03 you will have to change some of its settings.
But I would definitely like to take a look and check your scene, if possible.

For the in-process-rt-engine I guess it is what it is for the moment.