Page 2 of 3
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Thu Sep 10, 2020 1:09 pm
by paride4331
mbetke wrote:Why is this? It renders nice until the end.
Then denoiser destroys the Beauty pass and the denoised beauty too.
Hi mebtke,
it should depends on Ram limit, rendering 20000*20000, 128GB may not be enough, denoiser might need a little bit more.
Try to export to SA your scene before to render it. 3dsMax eats Ram you could save.
Using Nvlink, your Titan X should reduce Out-fo-core, so you could try to set it to 6GB (maybe less).
In Order to reduce Out-of-core, you could also reduce a little bit the textures map resolution.
I hope it helps
Regards
Paride
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Fri Sep 11, 2020 6:17 am
by mbetke
It should depends on Ram limit, rendering 20000*20000, 128GB may not be enough, denoiser might need a little bit more.
Try to export to SA your scene before to render it. 3dsMax eats Ram you could save.
It's not that easy. The scene itself is only 14GB in VRAM. So I don't need out of core at all.
With 10.000x10.000 the denoiser messes up the scene. Even the regular non-denoised beauty pass. But it consumes only around 64GB of system memory.
So if even this resolution gets messed up it must be something inside Octane not working. In stand alone its same problem.
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Fri Sep 11, 2020 8:42 am
by mbetke
After more research, importing, merging, isolating and hiding stuff I found out that the render even gets killed with just one model and nothing else in it.
Definitely an Octane issue.
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Fri Sep 11, 2020 11:46 am
by paride4331
mbetke wrote:It should depends on Ram limit, rendering 20000*20000, 128GB may not be enough, denoiser might need a little bit more.
Try to export to SA your scene before to render it. 3dsMax eats Ram you could save.
It's not that easy. The scene itself is only 14GB in VRAM. So I don't need out of core at all.
With 10.000x10.000 the denoiser messes up the scene. Even the regular non-denoised beauty pass. But it consumes only around 64GB of system memory.
So if even this resolution gets messed up it must be something inside Octane not working. In stand alone its same problem.
memory.jpg
Hi mbetke,
I will send an .orbx in pm to test, I've 64GB on board then I cannot push up the render size.
Said that, I found some assets you could fix, like non Octane materials in xref too.
Regards
Paride
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Fri Sep 11, 2020 4:16 pm
by paride4331
samsue wrote:critical errors when trying to delete
-----
displac mixer dont work
MCefoafY3F.png
Hi samsue,
mix only with vertex displacement map
Regards
Paride
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Mon Sep 14, 2020 6:10 am
by mbetke
Hi mbetke,
I will send an .orbx in pm to test, I've 64GB on board then I cannot push up the render size.
Said that, I found some assets you could fix, like non Octane materials in xref too.
Regards
Paride
Thanks, but after loading your .orbx into SA the render just looks messed up too with given resolution.
Funfact: My scene get wired colors with 10.000x10.000px but renders fine with 11234x11234px. But lines are strange distorted. Like if I pull the upper half 30 degree to the left.
When I put a diffuse material on all assets it fails too.
I think Octane just fails on this scene.
Now I have to stitch some smaller renders of it into a panorama.
Is there any plugin, script that will render several parts of the scene for me? I will stitch it together in post then.
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Mon Sep 14, 2020 8:52 am
by HHbomb
Hi,
"currentrenderer = renderers.current
currentrenderer.RTXAccelEnabled = false "
don't work anymore ? idem for true

Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Mon Sep 14, 2020 1:41 pm
by paride4331
mbetke wrote:Hi mbetke,
I will send an .orbx in pm to test, I've 64GB on board then I cannot push up the render size.
Said that, I found some assets you could fix, like non Octane materials in xref too.
Regards
Paride
Thanks, but after loading your .orbx into SA the render just looks messed up too with given resolution.
Funfact: My scene get wired colors with 10.000x10.000px but renders fine with 11234x11234px. But lines are strange distorted. Like if I pull the upper half 30 degree to the left.
When I put a diffuse material on all assets it fails too.
I think Octane just fails on this scene.
Now I have to stitch some smaller renders of it into a panorama.
Is there any plugin, script that will render several parts of the scene for me? I will stitch it together in post then.
Hi mbetke,
I'm still testing this issue in order to figure out or report this to the developers.
Regards
Paride
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Fri Sep 18, 2020 5:15 am
by coilbook
Hi Paride,
I dont remember what you told me before about the old and new volume behavior. Are they planning to fix new volume rendering very dark?
Can w e render particles with embergen. For some reason exporting vdb with particles from embergen octane wont render volumes at all ?
Thanks
Re: OctaneRender® for 3ds max® v2020.1.5 - 10.17
Posted: Fri Sep 18, 2020 10:07 am
by paride4331
coilbook wrote:Hi Paride,
I dont remember what you told me before about the old and new volume behavior. Are they planning to fix new volume rendering very dark?
Can w e render particles with embergen. For some reason exporting vdb with particles from embergen octane wont render volumes at all ?
Thanks
Hi coilbook,
It's depends on changes on the step length of the medium node in v2020.
The solution is to have the Step length value higher.
Could you share the volume with particles you exported to .vdb?
Regards
Paride