lights make nvdia drivers crashes
Moderator: juanjgon
This is known limitation due to how the Windows NVidia driver works: if the GPU CUDA kernel process is too complex, and the wait time to get a render sample is too large, the driver thinks that the GPU is frozen and resets it.
There are some register variables to control this wait time. They are set to suitable values by the Octane Standalone install program. Have you installed the Standalone in your computer?
-Juanjo
There are some register variables to control this wait time. They are set to suitable values by the Octane Standalone install program. Have you installed the Standalone in your computer?
-Juanjo
50 Octane lights should not be a problem to crash the drivers. What kernel are you using? ... perhaps you have a lot of bounces in the kernel configuration. Also some features, like the displacement mapping, the hair or a lot of instances in the same place, could be hard to render.
Anyway you can change the register parameters to try to get more time for the drivers:
- Launch the regedit (Start -> Run window -> regedit)
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
- The key "TdrLevel" should be set to 3.
- The key "TdrDelay" is the delay in seconds. Maybe set it to 20 or 30.
Restart your system and try again.
-Juanjo
Anyway you can change the register parameters to try to get more time for the drivers:
- Launch the regedit (Start -> Run window -> regedit)
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
- The key "TdrLevel" should be set to 3.
- The key "TdrDelay" is the delay in seconds. Maybe set it to 20 or 30.
Restart your system and try again.
-Juanjo
Weird, and are you sure that you have installed the Octane 2.2 Standalone in your system using the Octane installer?
http://render.otoy.com/customerdownload ... _win64.exe
Anyway you could try to add the variables to the register yourself, reboot and see what happens.
-Juanjo
http://render.otoy.com/customerdownload ... _win64.exe
Anyway you could try to add the variables to the register yourself, reboot and see what happens.
-Juanjo