2020.1.2.0 nvLink still not working.

[Lewis]

Thanks for chiming in Jules, appreciate your engagement about this .

I have question.

I'm rendering some heavy scene (Ach-Viz, total about 20 mil polys+instances) and my Out Of Core settings are set to 15GB (my machine has 128GB total so plenty is left free).

When render starts OOC usage says 2.47GB but after few frames render Aborts and log says "Out of memory GPU 0, 1, 2".
I'm NOT using display GPU (that would be my GPU 3) and RTX is on but render aborts anyway after some time.

Is there a chance that there is some BUG in RTX code or OOC code in general 'coz how it can be out of memory if i still have 12.5GB for usage in OOC settings ?
Does RTX somehow limit OOC or such issue ?

Thanks

[Goldorak]

In 2020.1, RTX on doesn’t work with ooc - in theory it should switch to RTX off, but I suspect that may not be happening. Can you confirm this happened with RTX off too?

[Lewis]

In 2020.1, RTX on doesn’t work with ooc - in theory it should switch to RTX off, but I suspect that may not be happening. Can you confirm this happened with RTX off too?

Hi, i do not know does it switch RTX off automatically 'coz we have RTX Logo (RED) on IPR window when rendering and it's always present on that window if RTX is on in preferences (LightWave plugin) so i cant' say did octane automatically turned it off (Juan - should LOGO disapear or notice it's off ?) but i see OOC memory usage increase.

Funny thing after I tested this scene more I've increased GPU headroom from 400 MB to 500 MB and now my scene rendered fine(RTX says it's ON) even with 4.7GB OOC showed to be used during render (before it failed with only 2.47 GB used OOC).

[juanjgon]

I think that there is no way to get the RTX final status from the SDK to report it in the plugins. In fact, perhaps even the RTX could be enabled for some objects or shaders and not of others, although I'm not sure at all, to be honest.

Thanks,
-Juanjo