Page 3 of 4

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Wed Apr 28, 2010 1:22 pm
by eyeinthesky
radiance wrote:you should set the tdr level to 0, also read the 2nd post, as there was a typo in the first one...

Radiance


nothing to do ... octane crashes ... even if it uses 200 MB to 500 this is the clip of the registry editor... something wrong?

Thank You

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Wed Apr 28, 2010 2:56 pm
by radiance
try adding a key TdrDelay: REG_DWORD with value 10 or 12 or so ?

Radiance

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Thu Apr 29, 2010 9:17 am
by eyeinthesky
radiance wrote:try adding a key TdrDelay: REG_DWORD with value 10 or 12 or so ?

Radiance


Radiance, apologize if I continue to bore you, unfortunately, continues to crash ... I do not know what to do, it seems that the operating system ignores the values in the registry ... Sometimes the image appears and then octane crashes after the first sample ... especially if it exceeds half of the video card 512mb memory ..

Thank You for reply

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Thu Apr 29, 2010 9:41 am
by radiance
Hi,

Just wait a bit, i will prepare some ready to apply registry fix files later today and post them here.

Radiance

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Thu Apr 29, 2010 10:25 am
by radiance
Hi,

I've done some further research in the docs and i'm afraid you won't be able to fix it on XP.
The default timeout is higher than Vista/7 (2 seconds), for XP it's 5 seconds,
but the keys won't work on it.

The only option is to add a 2nd GPU and use it for octane rendering,
and it has to be a GPU that is not connected to a display/used for displaying a windows desktop.

Individual GPU program launches are limited to a run time
of less than 5 seconds on a GPU with a display attached.
Exceeding this time limit usually causes a launch failure
reported through the CUDA driver or the CUDA runtime. GPUs
without a display attached are not subject to the 5 second
runtime restriction. For this reason it is recommended that
CUDA be run on a GPU that is NOT attached to a display and
does not have the Windows desktop extended onto it. In this
case, the system must contain at least one NVIDIA GPU that
serves as the primary graphics adapter.


since the FX1700 is quite a slow card, i would recommend for you to get a 2nd GPU, a GTX200 or GTX400 series.
you'll be able to use octane with far more complex scenes as it will have more memory,
and you'll have a much smoother experience.

Our 32bit system is running XP here, and it has 2 gpu's in it (2x FX3800, and when using the 2nd gpu, it works flawlessly)

Radiance

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Thu Apr 29, 2010 3:29 pm
by eyeinthesky
Thank You Radiance

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Sat May 01, 2010 1:37 am
by teknofreek
On those Tdr dwords ...
When you edit the reg and add the dword, do you input the value in as hex or decimal? ie the 600 reported above...
:oops:

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Sat May 01, 2010 1:29 pm
by radiance
teknofreek wrote:On those Tdr dwords ...
When you edit the reg and add the dword, do you input the value in as hex or decimal? ie the 600 reported above...
:oops:


the only thing you need to add is the TdrLevel and it needs to be 0

Radiance

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Thu Jul 22, 2010 7:18 pm
by pm3d
no more issues with path tracing i have laptop new beta 2.2b works ok now after previous problems of crashing
yippe i can render 2048 x 512 x2 without crash

my laptop is 8600M GT no more problems

thanks

Re: Regarding octane closing with pathtracing & high resolutions

PostPosted: Wed Oct 20, 2010 8:50 am
by jmlepretre
Hi all,

I read all of those posts and i am wondering if the things have changed since the last post
concerning Freezes, blue screens on large renderings with pathTracing on XP32 ...?

Jean-marc