Is NVLink works with Octane plugins ?

[SSmolak]

The issue with NvLink is not c4doctane only related, but is affecting also 3ds Max, for example.
So we need to wait for a fix in the general SDK.
ciao Beppe

Thank you for information. Any ETA for this ? Days, weeks, months ?

[nejck]

Any updates perhaps?

[bepeg4d]

The core devs have identified and solved the issue with NvLink, and the fix will be part of the next SDK update, plugins will follow.
ciao Beppe

[nejck]

Thank you devs, thank you bepeg4d!

[SSmolak]

I don't know what to say. Maybe these images can do that :







I suppose that even Out of Core doesn't work propely if it can't catch this situation.

Sorry, false alarm. It was my too small RAM fault. I had to manually increase Windows Virtual Memory and Octane works fine even with huge amount of Hi-Poly objects. Octane plugin needs much more Ram to convert objects than Standalone version. Strange is that Windows 10 can't automatically increase virtual memory in such situation ( I had set it to auto )

[SSmolak]

New NVidia Studio driver is out but NVlink still doesn't work.

[SSmolak]

Memory pooling was done in experimental version of VRay using NVlinked GeForce RTX 2080TIs year ago : https://www.chaosgroup.com/blog/profili ... -rtx-cards ( at the page end ) . Why this doesn't work in Octane ?