[ Play Quicktime file ] gpu failed.MOV [ 4.59 MiB | Viewed 2706 times ]
PolderAnimation wrote:Can we have the option for ABC an FBX file to loop, and to have a time offset. This is very handy when using animated ABC files in a large project where sometimes the frame ranges are in high numbers and the looping abc file is only 400 frames long. Hope you guys can consider this.
Cheers
paride4331 wrote:Hi coilbook,
as I can see in your clip, out-of-core is not checked; Titan XP has 12GB on board, 2080TI only 11GB. Could you try using out-of-core option?
Regards
Paride
Notiusweb wrote:Otoy - if I F around with displacement too much and too vigorously I can crash Octane, even crash my PC to blue screen with a Win 10 warning about Page Fault in non-paged area blah blah blah....
Is there any setting, or recommended rule-of-thumb set-up, in Octane that you know, or users have come to discover, that would tend to make it more stable as far as being able to go crazy with the displacement sliders? And by crazy I mean whipping the sliders around randomly because I don't feel like typing in the numbers because I'm having too much fun moving the sliders and seeing crazy sh!t. (ie I drag it from .01 to 5.0, kind of haphazardly and accidentally.)
Thx!
coilbook wrote:now these new errors appear without any reasons. these scenes were rendered for months and all the sudden all these scenes do this. Nothing was changed Even isolating one object this scene does this
I was rendering with these drivers for a long time and all the sudden i cannot even open octaneviewport without an error .
denoiserThread0 : Initialization failed. Restart required
CUDA error 702 on device 0: the launch timed out and was terminated
-> kernel synchronization failed
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to load symbol data to the device(const11)
device 0: failed to upload imager params
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to unregister pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to unregister pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to destroy CUDA event
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to destroy CUDA event
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to deallocate device memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to deallocate pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
haze wrote:coilbook wrote:now these new errors appear without any reasons. these scenes were rendered for months and all the sudden all these scenes do this. Nothing was changed Even isolating one object this scene does this
I was rendering with these drivers for a long time and all the sudden i cannot even open octaneviewport without an error .
denoiserThread0 : Initialization failed. Restart required
CUDA error 702 on device 0: the launch timed out and was terminated
-> kernel synchronization failed
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to load symbol data to the device(const11)
device 0: failed to upload imager params
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to unregister pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to unregister pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to destroy CUDA event
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to destroy CUDA event
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to deallocate device memory
CUDA error 702 on device 0: the launch timed out and was terminated
-> could not get memory info
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to deallocate pinned memory
CUDA error 702 on device 0: the launch timed out and was terminated
Are you able to PM the scene?
PolderAnimation wrote:Can we have the option for ABC an FBX file to loop, and to have a time offset. This is very handy when using animated ABC files in a large project where sometimes the frame ranges are in high numbers and the looping abc file is only 400 frames long. Hope you guys can consider this.
Cheers
Return to Development Build Releases
Users browsing this forum: No registered users and 9 guests