OctaneRender® for 3ds max® v2.06a (proxy support)

[thilima]

hey Karba take a look

[HHbomb]

One question Karba for proxies : how do this format will evolve and what about compatibilty across versions ?

[Karba]

Stupid question but what does the proxy gives? What is the difference between proxy and instance? What are the benefits?

proxy geometry is only for fast 3dsmax viewport. you just use light geometry for 3dsmax viewport and initial geoemtry for the render.
it also makes scene file lighter because you move have geometry parts to separate files. for render itself it doesn't make any sense at all.

[Karba]

What do you mean big scene load time? when you just open a scene file or start render?

When the scene is loading into the octane render buffer, the buffer can go not responding.
These scenes we cannot render interactively, or when the max scene is also open.
We have to send to backburner and render to a server.

Scene file opens in a reasonable time.

Still plenty of VRAM (6gb cards) and RAM (32gb on machine) remaining.

You told you have this render hang only with displacement? I am investigating it at the moment.

[Karba]

hey Karba take a look

Thank you, I will fix that.

[Karba]

One question Karba for proxies : how do this format will evolve and what about compatibilty across versions ?

I have no idea how this format will evolve. It depends on users experience. I did the best from my understanding the problem, but I am not able to take into account everything.
Newer plugin versions will be able to load older geometry files.

[perro_abombao]

thanks karba!!!

this would be awesome in 1.55 version too

[WhaleHunter]

What do you mean big scene load time? when you just open a scene file or start render?

When the scene is loading into the octane render buffer, the buffer can go not responding.
These scenes we cannot render interactively, or when the max scene is also open.
We have to send to backburner and render to a server.

Scene file opens in a reasonable time.

Still plenty of VRAM (6gb cards) and RAM (32gb on machine) remaining.

You told you have this render hang only with displacement? I am investigating it at the moment.

Large Scene with displacements did have the issue, scene would not render any method with displacement. We removed displacements from every material in every file and the scene rendered through backburner servers (failure averted..). However, even with no displacement render of full scene will not start in the octane buffer. This is not the only scene. Mostly we are dealing with chunky scenes, but nothing over the triangle/poly limit or over 6gb VRAM.

Thanks.

[Karba]

Large Scene with displacements did have the issue, scene would not render any method with displacement. We removed displacements from every material in every file and the scene rendered through backburner servers (failure averted..). However, even with no displacement render of full scene will not start in the octane buffer. This is not the only scene. Mostly we are dealing with chunky scenes, but nothing over the triangle/poly limit or over 6gb VRAM.
Thanks.

Displacement hang should be fixed. Wait for a new release. Regarding other issues - can't say anything at the moment.

[3dgeeks]

Is it possible to still add a displacement override, as this may enable some renders to progress without needing to hunt down every displacement in xrefs and materials.