OTOY Forums

Deferred Meshes increase ram usage. Not sure why but thought I'd let you know. Went from 1.3gb used then to 2.2 gb used once I deferred a dense mesh.

RAM, or VRAM?

Paul

Think it's Vram. The one for my GPU.

Deferred Meshes increase ram usage. Not sure why but thought I'd let you know. Went from 1.3gb used then to 2.2 gb used once I deferred a dense mesh.

Hi. Yes, there definitely seems to be problems with deferred meshes. With the Render Cache OFF, the plugin is actually loading the deferred mesh twice (which is why the VRAM used is increasing), due to Modo providing the mesh vertices twice. With the Render Cache ON, the same thing happens - so the internal Render Cache API is hitting the same Modo bug. I will report this error to TheFoundry. Until TheFoundry provide a fix, Deferred Mesh support in the plugin should be considered to be not working.

Paul

Hi. Yes, there definitely seems to be problems with deferred meshes. With the Render Cache OFF, the plugin is actually loading the deferred mesh twice (which is why the VRAM used is increasing), due to Modo providing the mesh vertices twice. With the Render Cache ON, the same thing happens - so the internal Render Cache API is hitting the same Modo bug. I will report this error to TheFoundry. Until TheFoundry provide a fix, Deferred Mesh support in the plugin should be considered to be not working.

I spoke too soon I have been able to work around this problem, and the version below should resolve this issue.

3.5.3.117
- Resolved issues with Deferred meshes loading twice

https://render.otoy.com/customerdownloa ... _64bit.exe

Paul

Awesome! Thanks. This should be very useful.

Hi Paul, first and foremost just wanted to say awesome work on this plugin. I've been using it for months now with zero issues it's rock solid and a joy to use.

One thing I noticed though with the Dirt Texture and I'm not even sure if it's a bug, possibly just the inherent nature of the shader. Basically the Dirt Texture doesn't respect transparency values of an object with an opacity mask. Check my renders below: one with and one without the Dirt Texture applied.

No Dirt Texture With Dirt Texture applied Without transparency clipping
Notice the intersecting areas of the plant object with transparency clipping, showing the dirt texture on the ball object.

Hi Dino. I haven't seen the Dirt shader issue mentioned previously. It is a general Octane issue - so may I suggest exporting each of the above scenarios to ORBX and posting them, along with the above renders, to the Octane Standalone 3.05.3 release thread, where the Otoy devs can comment.

Thanks

Paul

Thanks Paul will follow this up in the general Octane thread.

Cheers,
Dino.

I am getting this crash on Modo10.2v1 on Mint18 too. The plugin works fine on Modo902. This appears to be a bug in Modo10.2v1, but I will need to consult with TheFoundry devs to determine the exact problem.

Roy, TheFoundry has given me a fix for this issue - can you pls try the version below:

https://render.otoy.com/customerdownloa ... _Linux.run

Thanks

Paul

Roy, TheFoundry has given me a fix for this issue - can you pls try the version below:

https://render.otoy.com/customerdownloa ... _Linux.run

Success! Thanks, Paul.

Out of curiosity, what was the problem/solution? I have the feeling other Modo plugin developers might be running into the same issue...

Cheers,

Roy