Page 3 of 6
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Mon May 18, 2020 1:02 pm
by paride4331
tcheng00 wrote:HHbomb wrote:I have such crashes with big scenes when moving object ( and I have always Ai lights activated )
Does it go away when you deactivate AI Lights?
Have you any issue inscreasing the Out-of-core using Nvlink?
Regards
Paride
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Mon May 18, 2020 7:41 pm
by tcheng00
paride4331 wrote:tcheng00 wrote:HHbomb wrote:I have such crashes with big scenes when moving object ( and I have always Ai lights activated )
Does it go away when you deactivate AI Lights?
Have you any issue inscreasing the Out-of-core using Nvlink?
Regards
Paride
I'm using NVlink. There's the occasional "Mismatching barriers, 5 and 2", but it doesn't crash out max and I can just restart it. OOC with NVlink seems to save me an additional 1 GB of OOC to CPU RAM, maybe less. Not sure if it should be more. Things are generally more stable without nvlink, but I lose the extra Vram.
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Tue May 19, 2020 6:39 am
by mbetke
I also have problems with NVLink and out of memory messages with an aerial image. So lots of vegetation but no "super mesh" scenario. It fails to render with 20GB our of possible 48GB
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Tue May 19, 2020 8:19 am
by paride4331
Hi tcheng00,
"Mismatching barriers, 5 and 2" is a known issue, developers are working on it.
Regards
Paride
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Tue May 19, 2020 8:22 am
by paride4331
mbetke wrote:I also have problems with NVLink and out of memory messages with an aerial image. So lots of vegetation but no "super mesh" scenario. It fails to render with 20GB our of possible 48GB
Hi mbetke,
did you try making all movable proxy, non grouping objects, head room 512mb?
Regards
Paride
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Tue May 19, 2020 9:11 am
by samsue
mbetke wrote:I also have problems with NVLink and out of memory messages with an aerial image. So lots of vegetation but no "super mesh" scenario. It fails to render with 20GB our of possible 48GB
I recommend taking a look at this topic, paride4331 helped me a lot.
viewtopic.php?f=27&t=74536
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Tue May 19, 2020 9:14 am
by Sidches
Hi guys, the setting USE ONLY STANDART PARTICLE is still not set by default, every new project needs to be opened, checkboxed, saved and re-opened. =(
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Tue May 19, 2020 1:35 pm
by tcheng00
paride4331 wrote:Hi tcheng00,
"Mismatching barriers, 5 and 2" is a known issue, developers are working on it.
Regards
Paride
Thank you for that, i'll keep NVlink disabled for now.
Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Wed May 20, 2020 5:38 am
by javierluisbravo
just to write it here as it is related:
when gamma hack is ON.. and nonlinear tonemappiing ON => the exr saved is clamped..
so when you expose down in nuke, after or whatever.. there are no highlights properly kept.
if you render with gamma hack OFF and nonlinear tonemapping OFF (whatever response curve as being off is not affected) => the exr saves fine as it did in versions 2019.
Thanks! Hope you can fix it

Re: OctaneRender® for 3ds max® v2020.1 - 10.11
Posted: Wed May 20, 2020 7:11 am
by mbetke
Hi mbetke,
did you try making all movable proxy, non grouping objects, head room 512mb?
Regards
Paride
You mean grouping objects with the 3ds max feature "Groups"? Or attaching them as an editable poly to each other and make them a big object?
I use layers and groups a lot to keep my scenes organized.