Page 1 of 2
2020.1.2.0 nvLink still not working.
Posted: Tue Jun 23, 2020 1:51 am
by pixelsmack
LW2020.0.1
Octane 2020.1.2.0
Windows10 Pro b2004
NVIDIA 442.92 Studio Driver
MSI 2080Ti Gaming Trio x2 with nvLink bridge. SLI enabled.
Octane Stand Alone installed and configured ( peering and OOC enabled).
Reported GPU ram
nvLink OFF
Used
1144
Free
8786
Total
11264
nvLink ON
Used
1150
Free
8514
Total
11264
NVLink Status says
0 even though it's turned on. Which explains why I am not seeing larger ram pool.
I know RTX motion-blur support has not been added but I include to keep the dream alive.
MoBlur
RTX ON
52s
RTX OFF
51s
No MoBlur
RTX ON
22s
RTX OFF
50s
Re: 2020.1.2.0 nvLink still not working.
Posted: Tue Jun 23, 2020 7:35 am
by juanjgon
Ok. I'm going to add some new log lines to the next plugin build that I want to release later this week to try to debug this issue.
Thanks,
-Juanjo
Re: 2020.1.2.0 nvLink still not working.
Posted: Tue Jun 23, 2020 6:16 pm
by pixelsmack
Unfortunately I am back in production and I have to undo my nvLink set up. The GPUs just get way too hot. One hits 90c! So I need to run them in my production configuration. There are no nvLink extender cables so I won't be able to use this mode and test.
Hopefully another person here can verify this nvLink progress? Thank you for your progress on this!
Re: 2020.1.2.0 nvLink still not working.
Posted: Wed Jul 15, 2020 10:06 pm
by dmodric
In 2020.1.3.0 it is working but is far from advertised. I didn't expected double the VRAM but this is not even close.
And still not faster then 4.05 even with RTX
8m33s in 4.05 vs 9m41s 2020.1.3
Re: 2020.1.2.0 nvLink still not working.
Posted: Thu Jul 16, 2020 2:29 am
by Goldorak
dmodric wrote:In 2020.1.3.0 it is working but is far from advertised. I didn't expected double the VRAM but this is not even close.
And still not faster then 4.05 even with RTX
8m33s in 4.05 vs 9m41s 2020.1.3
RTX doesn’t accelerate texture displacement which seems like a big part of your scene may be using. If you want “RTX on” speed gains, use vertex displacement instead, and try to keep geo in core, otherwise it may be best to turn it off if you are seeing lower speeds than in V4 (2020 is definitely faster than V4 in on 2070, all things being equal).
Re: 2020.1.2.0 nvLink still not working.
Posted: Thu Jul 16, 2020 8:08 am
by dmodric
I don't understand what are you trying to say. Given all things equal (all that out of core textures and geometry, displacement maps etc.) 4.05 is faster in that given scene.
Here is the render speed with RTX off.... 13m42s
Re: 2020.1.2.0 nvLink still not working.
Posted: Thu Jul 16, 2020 3:58 pm
by Goldorak
Can you export to orbx and share so we can look into this?
Re: 2020.1.2.0 nvLink still not working.
Posted: Fri Jul 17, 2020 8:51 am
by dmodric
Sent in PM. Thanks
Re: 2020.1.2.0 nvLink still not working.
Posted: Fri Jul 17, 2020 5:01 pm
by pixelsmack
The doubling of the available GPU ram pool is something I would/should expect as that’s how it works with the Quadros. The Studio driver is supposed to enable the same functionality when nvLink is active.
Re: 2020.1.2.0 nvLink still not working.
Posted: Sat Jul 18, 2020 12:13 am
by Goldorak
dmodric wrote:Sent in PM. Thanks
Thanks - slammed this week, but will take a look early next week.