Have you any issue inscreasing the Out-of-core using Nvlink?tcheng00 wrote:Does it go away when you deactivate AI Lights?HHbomb wrote:I have such crashes with big scenes when moving object ( and I have always Ai lights activated )
Regards
Paride
Have you any issue inscreasing the Out-of-core using Nvlink?tcheng00 wrote:Does it go away when you deactivate AI Lights?HHbomb wrote:I have such crashes with big scenes when moving object ( and I have always Ai lights activated )
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.paride4331 wrote:Have you any issue inscreasing the Out-of-core using Nvlink?tcheng00 wrote:Does it go away when you deactivate AI Lights?HHbomb wrote:I have such crashes with big scenes when moving object ( and I have always Ai lights activated )
Regards
Paride
Hi mbetke,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.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
Thank you for that, i'll keep NVlink disabled for now.paride4331 wrote:Hi tcheng00,
"Mismatching barriers, 5 and 2" is a known issue, developers are working on it.
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?Hi mbetke,
did you try making all movable proxy, non grouping objects, head room 512mb?
Regards
Paride