Hi there,
I'm facing the issue that the Error Console shows me this, as well as the Memory that has been used, but it does not visualize the full amount of my VRAM.
I"ve enabled nv link in the the plugin options as well as in the Nvidia Control Center.
Here my spec;
Houdini 20.5.455
Octane Version - 2024.1.2
Processor AMD Ryzen Threadripper PRO 3975WX 32-Cores, 3500 Mhz, 32 Core(s), 64 Logical Processor(s)
Total Physical Memory 256 GB
2x RTX 3090
Windows Version 10.0.22631 Build 22631
Nvidia Studio Driver - 572.83
Error Message DXGI Adapter + NV LINK - 2x RTX 3090
Moderator: juanjgon
Hey Al88!
Unfortunately it's a little tricky for us to troubleshoot this one since we don't have a hardware setup with NVlink.
There is a good chance that this is an issue with Octane core and not just Octane Houdini. If you want to help resolve this issue, you could export your file to .orbx, and load it into octane standalone, and see if it show's the same issue there. If so then we can pass it onto the core devs to take a look!
Unfortunately it's a little tricky for us to troubleshoot this one since we don't have a hardware setup with NVlink.
There is a good chance that this is an issue with Octane core and not just Octane Houdini. If you want to help resolve this issue, you could export your file to .orbx, and load it into octane standalone, and see if it show's the same issue there. If so then we can pass it onto the core devs to take a look!
it will not show You 48, it would still show 24, but at least in Standalone, there should be another bar pointing p2p usage: Let me find or make You a screenshot.Al88 wrote: Tue Mar 25, 2025 2:14 pm .. but it does not visualize the full amount of my VRAM.
I"ve enabled nv link in the the plugin options as well as in the Nvidia Control Center.
that message though, that You make screenshot of does look strange. Do You have the physical bridge between cards installed?
Last edited by glimpse on Sat Mar 29, 2025 9:42 am, edited 1 time in total.
That's how NVLINK is reflected in Standalone when it works as it should. Additional BLUE bar is visible and You can also see another line (Peer to peer amount)
Hi AI88,Al88 wrote: Thu Mar 27, 2025 12:13 pm Hi dom_otoy,
thanks for getting back to me. Unfortunately this issue presist also in Octane Standalone. Please see below:
Could you confirm this is also happening to you using some not so recent NVIDIA drivers and share a screenshot of your Octane Standalone device settings window (
File -> Preferences -> Devices
)?Also if you could try this with the latest version of Standalone available here and let us know if this still happens that would help.
Thank you.
Yes I do, and I have enabled it in the Nvidia Control Panel.glimpse wrote: Thu Mar 27, 2025 12:49 pmit will not show You 48, it would still show 24, but at least in Standalone, there should be another bar pointing p2p usage: Let me find or make You a screenshot.Al88 wrote: Tue Mar 25, 2025 2:14 pm .. but it does not visualize the full amount of my VRAM.
I"ve enabled nv link in the the plugin options as well as in the Nvidia Control Center.
that message though, that You make screenshot of does look strange. Do You have the physical bridge between cards installed?
Hi,mojave wrote: Mon Mar 31, 2025 10:00 pmHi AI88,Al88 wrote: Thu Mar 27, 2025 12:13 pm Hi dom_otoy,
thanks for getting back to me. Unfortunately this issue presist also in Octane Standalone. Please see below:
Could you confirm this is also happening to you using some not so recent NVIDIA drivers and share a screenshot of your Octane Standalone device settings window (File -> Preferences -> Devices
)?
Also if you could try this with the latest version of Standalone available here and let us know if this still happens that would help.
Thank you.
please find below the screenshot for Octane Standalone with the latest driver. I have enabled the P2P, there yo can see it is working. Nevertheless, my goal is actually to have the NV Link working as intended within the Houdini Plugin.
Is there a Driver Version you would recommend?
Hi AI88,
The issue might actually be related to using NVLINK, causing Windows not to report the CUDA devices properly to Octane, we will need to look into this in more detail to give a solution. One way you can possibly get around this issue in the meantime would be reverting to Octane 2023 which should not be affected by this issue, and we will get back to you as soon as we have more information.
Besides that, please note that your device settings do not show any peers being selected, so it does not seem you are using P2P despite having installed an NVLINK bridge.
https://docs.otoy.com/standaloneSE/NVLi ... rGPUs.html
I hope that helps.
The issue might actually be related to using NVLINK, causing Windows not to report the CUDA devices properly to Octane, we will need to look into this in more detail to give a solution. One way you can possibly get around this issue in the meantime would be reverting to Octane 2023 which should not be affected by this issue, and we will get back to you as soon as we have more information.
Besides that, please note that your device settings do not show any peers being selected, so it does not seem you are using P2P despite having installed an NVLINK bridge.
https://docs.otoy.com/standaloneSE/NVLi ... rGPUs.html
I hope that helps.