You should enable the denoising in only one GPU, the one with more memory, and never in the GPU used for the monitors, that usually has less VRAM available.
Thanks,
-Juanjo
OctaneRender 2019.1 LightWave Production build 2019.1.4.0
Moderator: juanjgon
Yes, the plugin supports vertex maps in the mesh objects. You have the options to configure the vertex maps extracted by the plugin for each float or color attribute slot in the Octane object properties options.Carlos3D wrote:Can you tell me if Octane can render Vertex Color Maps.
Thanks,
-Juanjo
juanjgon wrote:Yes, the plugin supports vertex maps in the mesh objects. You have the options to configure the vertex maps extracted by the plugin for each float or color attribute slot in the Octane object properties options.Carlos3D wrote:Can you tell me if Octane can render Vertex Color Maps.
Thanks,
-Juanjo
Thank you very much Juanjo.
I will study it now.
Thanks
Carlos
I have just upgraded to 2019.4. Did anybody noticed some serious slow downs when using out of core rendering with denoiser comparing it to 4.05?
These are the times I am getting with test scene I made. On some more complex scenes time difference is even bigger. I am using 2x2070 super.
2019.4
ooc 3:35 (215s)
ooc denoiser 5:26 (326s)
no ooc no denoiser 2:35 (155s)
4.05
ooc 2:46 (166s)
ooc denoiser 3:37 (217s)
no ooc no denoiser 2:39 (159s)
These are the times I am getting with test scene I made. On some more complex scenes time difference is even bigger. I am using 2x2070 super.
2019.4
ooc 3:35 (215s)
ooc denoiser 5:26 (326s)
no ooc no denoiser 2:35 (155s)
4.05
ooc 2:46 (166s)
ooc denoiser 3:37 (217s)
no ooc no denoiser 2:39 (159s)
__________
AMD3600/X570/64GB/2x2070S
ASUS ROG Strix SCAR 17 G733 AMDRyzen7/64GB/3080 16GB
AMD3600/X570/64GB/2x2070S
ASUS ROG Strix SCAR 17 G733 AMDRyzen7/64GB/3080 16GB
Hello Juanjo,
thanks for your continuous work!
Could you please consider to add some easier refresh option for Vectron?
When using Vectron and trying to create some new stuff (and not just copying ready-to-use parameters from the internet) it is vital to easily explore parameter ranges.
In the current way it is not usable this way, and I have to use plain Octane to discover the parameter-ranges, write them down and later re-enter them in Lightwave. This really sucks when having formulas with many parameters
Cheers!
Andreas
thanks for your continuous work!
Could you please consider to add some easier refresh option for Vectron?
When using Vectron and trying to create some new stuff (and not just copying ready-to-use parameters from the internet) it is vital to easily explore parameter ranges.
In the current way it is not usable this way, and I have to use plain Octane to discover the parameter-ranges, write them down and later re-enter them in Lightwave. This really sucks when having formulas with many parameters

Cheers!
Andreas
- ryanaexavier
- Posts: 20
- Joined: Fri Jul 06, 2018 8:11 am
I second thisthargor6 wrote:Hello Juanjo,
thanks for your continuous work!
Could you please consider to add some easier refresh option for Vectron?
When using Vectron and trying to create some new stuff (and not just copying ready-to-use parameters from the internet) it is vital to easily explore parameter ranges.
In the current way it is not usable this way, and I have to use plain Octane to discover the parameter-ranges, write them down and later re-enter them in Lightwave. This really sucks when having formulas with many parameters
Cheers!
Andreas
