Unable to render large scene with Nvidia Studio Driver 441

Newtek Lightwave 3D (exporter developed by holocube, Integrated Plugin developed by juanjgon)

Moderator: juanjgon

Post Reply
hkleton
Licensed Customer
Posts: 86
Joined: Wed Apr 06, 2016 6:17 am
Location: Netherlands

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
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Yes, this sounds like some kind of issue with this drivers version. Have you tried the 436.48 studio drivers?

Thanks,
-Juanjo
hkleton
Licensed Customer
Posts: 86
Joined: Wed Apr 06, 2016 6:17 am
Location: Netherlands

Hi,

I only can find 441.66, 441.28, 441.12 and 431.86 and below at NVIDIA's website.
436.48 seems to be gone.

Someone has it laying around?

Thanks,
Hans
carolinafilms57
Licensed Customer
Posts: 6
Joined: Mon Oct 23, 2017 12:33 am

I'm was the exact same issue since updating to this driver. After I switched back to 431.86 everything was working again!
User avatar
Lewis
Licensed Customer
Posts: 1101
Joined: Tue Feb 05, 2013 6:30 pm
Location: Croatia
Contact:

Problem with 431.86 is that it's not supporting RTX so it's not an option to "stay" at that version :(.

So OTOY needs to find reason why is a driver change making large scenes un-renderable suddenly.
Could it be some Out Of Core problem then - No ?
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177

WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
User avatar
SSmolak
Licensed Customer
Posts: 1157
Joined: Sat Feb 07, 2015 5:41 pm
Location: Poland
Contact:

Is this problem related to Out of Core or NVlink memory pooling in new drivers ? I cannot get to work memory pooling from months.
Architectural Visualizations http://www.archviz-4d.studio
dmodric
Licensed Customer
Posts: 24
Joined: Fri Feb 17, 2017 1:01 pm

I am having similar issues. Rendering large scenes crashes octane with 441 drivers.



00:01:24 (0084.46) | Render setup Ok.
00:01:24 (0084.46) |
00:01:24 (0084.46) | [profile] Function "LWOctane_renderScene" over "" execution time: 8.729 seconds
00:01:24 (0084.46) | IPR: enter into the rendering loop
00:01:26 (0086.21) * OCTANE API MSG: CUDA error 2 on device 1: out of memory
00:01:26 (0086.21) * OCTANE API MSG: -> failed to allocate device memory
00:01:26 (0086.21) |
00:01:26 (0086.21) | ++++++++++++++++++++++++++
00:01:26 (0086.21) | +++ IPR RENDER FAILURE +++ processing the failure callback
00:01:26 (0086.21) | ++++++++++++++++++++++++++
00:01:26 (0086.21) |
00:01:26 (0086.21) | IPR: reset image callback
00:01:26 (0086.21) | IPR: wait for the getPreviewImage function
00:01:26 (0086.31) | IPR: free the OpenGL buffers
00:01:26 (0086.31) | IPR: rendering done
00:01:27 (0087.97) * OCTANE API MSG: CUDA error 2 on device 0: out of memory
00:01:27 (0087.97) * OCTANE API MSG: -> failed to allocate device memory
__________
AMD3600/X570/64GB/2x2070S
ASUS ROG Strix SCAR 17 G733 AMDRyzen7/64GB/3080 16GB
Post Reply

Return to “Lightwave 3D”