
I do have a quick question regarding NVLink. Is there a difference in running NVLink on consumer cards (Geforce) versus Quadros in Octane? Afaik they support NVLink with TCC mode on but I'm not sure how the implementation in Octane works.
It looks like my scene cause crash because of huge amount of 8K textures and NVlink doesn't support memory pooling for such type of data. I sent test scene to "karu". It would be great if Octane support NVlink for textures too because in most ArchViz situations textures are the main problem with VRam usage. And as I know "other" renderer support NVlink memory pooling for all scene data from more than half yearmojave wrote:We will look into this, thank you.SSmolak wrote:NVLink memory pooling for RTX 2080ti still doesn't work
Oops, sorry. I tried several times to upload the orbx file, but the forum keeps cutting it off at about the halfway point. The file is 492 MBytes in size.mojave wrote:The OCS itself did work but it doesn't contain any assetsgrimm wrote:Thanks, that makes sense.mojave wrote: RT cores provide acceleration for just triangles at this stag. I think you wanted to share an ORBX package instead?Did the OCS file not work? I'm still curious as to why the file doesn't render as fast as the 4.05 version of SA does? That way I know how to adjust it for the new version.
JasonThis is why I asked for the ORBX for testing what you report. Thanks for your help.
We would need some more information to be able to reproduce this, would you be able to share your device settings/headroom, etc. as well as the scene itself or some hints about how to get to this point?jimho wrote:regard to the nvlink
I tried to put a nvlink bridge (2 slot which is for quadro 6000) on 2 of my 2080ti adapters,
the sli function can be actived in windows through nvidia control panel,
the peer is appeared successfully in the octane's preference/device panel
for a large scene, it seems the p2p start working, but unfortunatly fails finally,
it is just on the way.
As per the latest NVidia drivers while writing these lines the only difference is that multiple NVlink setups are just supported for Quadro cards. This seemed to work in the past for some users but NVidia confirmed it is not supported and will not be in the foreseeable future.nejck wrote:Is there a difference in running NVLink on consumer cards (Geforce) versus Quadros in Octane? Afaik they support NVLink with TCC mode on but I'm not sure how the implementation in Octane works.
Does this happen by any chance just when you enable RTX acceleration support in the device settings? We have internally solved a few issues that didn't make it into this release that could be causing this. Would you be able to share this scene or a trimmed down version we can use to test your report? Thank you.Dmikucki wrote:The Random Walk medium still shows seams when two materials are used on the same object. This is a regression from the old node. It seems to happen even with no textures and a duplicate material node. See screenshots.
-The settings for the workstation :mojave wrote:We would need some more information to be able to reproduce this, would you be able to share your device settings/headroom, etc. as well as the scene itself or some hints about how to get to this point?jimho wrote:regard to the nvlink
I tried to put a nvlink bridge (2 slot which is for quadro 6000) on 2 of my 2080ti adapters,
the sli function can be actived in windows through nvidia control panel,
the peer is appeared successfully in the octane's preference/device panel
for a large scene, it seems the p2p start working, but unfortunatly fails finally,
it is just on the way.
Thank you.