hi Octane team,
I made a test scene for octane render, and it worked well in direct lighting mode.
But my graphics cards crashes every time when i switch to path tracing mode.
Please help me solve this problem, thank you.
Link to the files:
http://hotfile.com/dl/106987230/7e712f9 ... t.zip.html
Octane Version: beta2.43
windows 7 x64 CUDA3.2 Forceware 266.58
Hardware
i7 [email protected] 16GB DRAM
MSI GTX 460 1GB Hawk
Sparkle GTX 460 2GB
SLI disabled
GPU crashed after switching to path tracing
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Hi mate
I've tried your test scene and no crashing here.
Notice that Octane 2.43 cuda 3.2 is not working properly with MultiGPU.
Try dissabling your 1GB card for rendering and use only the 2GB one. Maybe it solves your problem
Cheers
I've tried your test scene and no crashing here.
Notice that Octane 2.43 cuda 3.2 is not working properly with MultiGPU.
Try dissabling your 1GB card for rendering and use only the 2GB one. Maybe it solves your problem
Cheers
Rampage IV Extreme+i7 3920k+2x GTX580 3GB+2x GTX470
Thank you for your testing.ttaberna wrote:Hi mate
I've tried your test scene and no crashing here.
Notice that Octane 2.43 cuda 3.2 is not working properly with MultiGPU.
Try dissabling your 1GB card for rendering and use only the 2GB one. Maybe it solves your problem
Cheers
Yeah I've already used one gpu each time for rendering.
I found out that lower the maxdepth value of path tracing helped a little, but still unstable.
BR
akira.
I think you just stumbled over the Windows GPU timeout check: See http://www.refractivesoftware.com/forum ... ?f=9&t=824akira wrote:hi Octane team,
I made a test scene for octane render, and it worked well in direct lighting mode.
But my graphics cards crashes every time when i switch to path tracing mode.
Please help me solve this problem, thank you.
Link to the files:
http://hotfile.com/dl/106987230/7e712f9 ... t.zip.html
Octane Version: beta2.43
windows 7 x64 CUDA3.2 Forceware 266.58
Hardware
i7 [email protected] 16GB DRAM
MSI GTX 460 1GB Hawk
Sparkle GTX 460 2GB
SLI disabled
You have two option to fix the issue:
a) Install version 1.022b (http://www.refractivesoftware.com/forum ... =24&t=2509), which will disable the timeout completely. You don't have to run that version at all, just install it and continue woking with beta 2.43.
b) Install the registry change of this post: http://www.refractivesoftware.com/forum ... 556#p45556, which will set the timeout to 10s, which should be enough for almost every scene.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Is there a way to solve this timeout issue on Linux machines? Because I'm also getting crashes with heavy scenes & pathtracing. If the rendering veiwport doesn't refresh in something like 5 seconds, the program crashes.
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net
It's the X server that kills Octane. Unfortunately I don't know enough about Linux to solve this problem. I did some search on the internet, but didn't find a way to specify/increase the timeout.matej wrote:Is there a way to solve this timeout issue on Linux machines? Because I'm also getting crashes with heavy scenes & pathtracing. If the rendering veiwport doesn't refresh in something like 5 seconds, the program crashes.
Sorry,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I think I have read something like this in the NVIDIA CUDA forums. You just have to make sure that the X server is not using the rendering card, i.e. it doesn't know it at all. Haven't tried it though.matej wrote:If I had two cards, one for display and one for rendering, this issue wouldn't appear, right?
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I choosed solution B and it worked(it's 0.35fps under pathtracing), no more crashes here.abstrax wrote: I think you just stumbled over the Windows GPU timeout check: See http://www.refractivesoftware.com/forum ... ?f=9&t=824
You have two option to fix the issue:
a) Install version 1.022b (http://www.refractivesoftware.com/forum ... =24&t=2509), which will disable the timeout completely. You don't have to run that version at all, just install it and continue woking with beta 2.43.
b) Install the registry change of this post: http://www.refractivesoftware.com/forum ... 556#p45556, which will set the timeout to 10s, which should be enough for almost every scene.
Cheers,
Marcus
Thank you for your help.
regards,
akira.