OTOY Forums

Posted: **Tue Aug 19, 2014 3:04 am**

Well we spent 8 hours turning off xrefs and other items and finally fixed our error. It looks like the problem was too many displacement materials on many objects. I guess these polys are not counted in the render stats?

Posted: **Tue Aug 19, 2014 3:40 am**

3dgeeks wrote:CUDA error 702 on device 1: The device kernel took too long to execute. This can only occur if timeouts are enabled. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> kernel execution failed (dl)
device 1: direct lighting failed

Sorry, I have missed it.
Render is too slow, so windows things it's hang and kills the gpu process.
I will include automatic system timeout increasing in next release.

Posted: **Tue Aug 19, 2014 5:30 am**

Thanks Karba.

Also, it make sense to have a global displace override. It would be good for the case where for animations we could turn off displacement and for still images turn it back on, without refactoring all the materials.

Posted: **Tue Aug 19, 2014 1:15 pm**

3dgeeks wrote:Thanks Karba.

Also, it make sense to have a global displace override. It would be good for the case where for animations we could turn off displacement and for still images turn it back on, without refactoring all the materials.

+1

OTOY Forums

2.05 hangs up

Re: 2.05 hangs up

Re: 2.05 hangs up

Re: 2.05 hangs up

Re: 2.05 hangs up