Tweet
Gradient Ramp map in VrayLightMtl causes GPU memory leak
In RT CUDA, using Gradient Ramp map plugged in VrayLightMtl causes memory leak.
To test this, apply a VrayLightMtl to an object and put a Gradient Ramp map in the Light color slot. Start RT CUDA and pay attention to the "Mtls" statistics in vray log window. Initially it will be about 8 mb. While RT CUDA is still running, start doing anything with the material - enabling/disabling the map with the checkbox, changing settings in the Gradient Ramp map etc and watch how the "Mtls" memory statistics raise from 8mb to 12mb, then 16mb then 20mb and so on each time a change is made. If the material tree is more complex, let's say a Composite map with 3-4 Gradient ramps and a Color Correct map at the end, each change in the material fills not 2-4mb but 50-100mb GPU memory at a time. When RT has filled about half of the GPU memory, the navigation starts getting more and more sluggish. Eventually RT crashes when the memory is fully filled up.
Using the Gradient map doesn't cause this problem, it's just the Gradient Ramp map that seems to cause it and only if it's connected to a VrayLightMtl. VrayMtl is fine. I also tried with a few other types of maps like bitmap, noise, tiles etc. and there were no such problems with them.
Another thing that caught my attention in the message window is the warning that Gradient Ramp maps are "not supported and will be baked". It's strange because the RT supported features page show Gradient Ramp as fully supported.
For vray version and hardware, please check signature.
Attached below you'll find a test scene. Just open, run Active Shade and start adjusting things in the Gradient Ramp maps or the material.
And here's a screenshot of the message window:
To test this, apply a VrayLightMtl to an object and put a Gradient Ramp map in the Light color slot. Start RT CUDA and pay attention to the "Mtls" statistics in vray log window. Initially it will be about 8 mb. While RT CUDA is still running, start doing anything with the material - enabling/disabling the map with the checkbox, changing settings in the Gradient Ramp map etc and watch how the "Mtls" memory statistics raise from 8mb to 12mb, then 16mb then 20mb and so on each time a change is made. If the material tree is more complex, let's say a Composite map with 3-4 Gradient ramps and a Color Correct map at the end, each change in the material fills not 2-4mb but 50-100mb GPU memory at a time. When RT has filled about half of the GPU memory, the navigation starts getting more and more sluggish. Eventually RT crashes when the memory is fully filled up.
Using the Gradient map doesn't cause this problem, it's just the Gradient Ramp map that seems to cause it and only if it's connected to a VrayLightMtl. VrayMtl is fine. I also tried with a few other types of maps like bitmap, noise, tiles etc. and there were no such problems with them.
Another thing that caught my attention in the message window is the warning that Gradient Ramp maps are "not supported and will be baked". It's strange because the RT supported features page show Gradient Ramp as fully supported.
For vray version and hardware, please check signature.
Attached below you'll find a test scene. Just open, run Active Shade and start adjusting things in the Gradient Ramp maps or the material.
And here's a screenshot of the message window:
Comment