Hi Karu,karu wrote:Hi Rajib,rajib wrote: H Parade / Mojave,
I have sent a link to a scene file (via PM to Paride) that will give the OOC error that I have been reporting in Daz plugin and now will crash 2020.1.RC2 standalone too as soon as it starts to render.
I have also noticed something. The Daz plugin problem starts to occur once OOC Memory usage hits around 8GB+. I tested this theory with a fresh new scene file in Daz and I kept adding copies of a multi High-Res models until it started to give me errors that I have been mentioning. I noticed below 8GB it still was able to render in the Octane Viewport without errors but once I crossed that, I started to get Cuda error 2, "Failed to allocate page locked memory. Error 2", "No device pointer for out-of-core memory", "Render engine failure" and even crashes.
I fell there is some difference in the plugin OOC handing code vs the standalone OOC handling code...
Regards,
Rajib
I suspect the difference is that Daz Studio is using more VRAM and/or more system RAM than standalone. There is no different code to handle OOC between the two; the only difference would be the environment in which the code is running.
(I thought I posted this on the RC1 thread but looks like it was somewhere else so the following is largely a copy-paste.)
The maximum amount of out-of-core memory mappable by applications is controlled by the driver and the GPU. Unfortunately we have no way to know ahead of time what that maximum amount is, and it may depend on runtime factors such as what other applications are doing. Generally it's approximately proportional to the amount of VRAM you have, which is why (for example) going from 64 GB to 128 GB system RAM or increasing Octane's out-of-core limit setting past a certain point is unlikely to improve anything. The setting in Octane controls the limit that Octane itself imposes on OOC memory, but there's no guarantee the driver will let you reach that limit.
Since this is out of Octane's control, the best we can do is improve the UI for the relevant settings/warnings/errors, to make it clear what each actually means, to give the user the best chance to have a working setup, and if all else fails to make it clear where the problem lies. I will try to think of some ways we could improve the user experience.
Thank you for the explanation. I hope the UI can be improved in this case so that we as users know why it is happening and can edit the scene / materials to make it fit. May I know once nvlink is supported 100% will this issue go away as linking 2 RTX 2080 Ti should double the VRAM to 22GB and that should help load the scene ? If not, time to start saving for the Titan RTX.... 4 x that will cost a pretty penny or two
.... Btw. I did provide a scene file that crashed the standalone too to Paride as soon as it starts rendering (Loading no issue). Hopefully that helps you all to debug it further.
Regards,
Rajib
