Unable to render large scene with Nvidia Studio Driver 441
Posted: Sat Dec 14, 2019 5:56 pm
Hi,
My extreme big scene does render with Nvidia Studiodriver 431.86, but will not render with 441.66 (studio driver)
With 431.86 I was able to render it, did upgrade to 441.66 to test the RTX performance in Standalone 2020.
Great improvement!
But, now I cannot render my current project anymore.
Had to roll back to 431.86 to get it working again. (that is the only thing I changed, nothing else)
The error I get in the log file when using 441.66 is this:
00:01:49 (0109.85) | ... Init rendering ...
00:02:05 (0125.58) * OCTANE API MSG: Failed to allocate page-locked memory
00:02:05 (0125.58) * OCTANE API MSG: Failed to allocate page-locked memory
00:02:05 (0125.58) |
00:02:05 (0125.58) | ++++++++++++++++++++++
00:02:05 (0125.58) * OCTANE API MSG: No device pointer for out-of-core memory 0000002283872060
00:02:05 (0125.58) | +++ RENDER FAILURE +++ processing the failure callback
00:02:05 (0125.58) * OCTANE API MSG: Failed to allocate page-locked memory
Any ideas what might be causing this?
Thanks,
Hans
My extreme big scene does render with Nvidia Studiodriver 431.86, but will not render with 441.66 (studio driver)
With 431.86 I was able to render it, did upgrade to 441.66 to test the RTX performance in Standalone 2020.
Great improvement!
But, now I cannot render my current project anymore.
Had to roll back to 431.86 to get it working again. (that is the only thing I changed, nothing else)
The error I get in the log file when using 441.66 is this:
00:01:49 (0109.85) | ... Init rendering ...
00:02:05 (0125.58) * OCTANE API MSG: Failed to allocate page-locked memory
00:02:05 (0125.58) * OCTANE API MSG: Failed to allocate page-locked memory
00:02:05 (0125.58) |
00:02:05 (0125.58) | ++++++++++++++++++++++
00:02:05 (0125.58) * OCTANE API MSG: No device pointer for out-of-core memory 0000002283872060
00:02:05 (0125.58) | +++ RENDER FAILURE +++ processing the failure callback
00:02:05 (0125.58) * OCTANE API MSG: Failed to allocate page-locked memory
Any ideas what might be causing this?
Thanks,
Hans