Crash after 15-50 mins.
- Bogey Jammer
- Posts: 44
- Joined: Mon Aug 13, 2007 12:37 am
- Location: France
zsouthboy: fair enough; we still don't know what this is about. Someone having the same issue ?
Bogey Jammer : salut ! probably, from point 1 to point 3 the answer is negative. Now you could have broken some known limits with your scene, but someone else would have to tell. Point 4 has a much higher probability for an affirmative.

Bogey Jammer : salut ! probably, from point 1 to point 3 the answer is negative. Now you could have broken some known limits with your scene, but someone else would have to tell. Point 4 has a much higher probability for an affirmative.
Yep. Try the points exposed above (export-reimport), try another scene. I'm suspecting your scene ahead any other issue, clean it a max etcI'll try again to render my scene with other conditions

obsolete asset
- Kosmokrator
- Posts: 1141
- Joined: Sat Jul 29, 2006 11:52 am
- Location: Greece-Athens
have u overclock very high your pc???
if yes this is the ause of the fails after some minutes...i have axperiense this problems too until stabilize my system setup with a certain system setup....
if u don have overclock anything....search on your hardware...some may have a problem and fail in heavy conditions (likes indigo renders with full cores)
i have found indigo th most reliable and full-on stress test for extreme pc-overclk!!!
if yes this is the ause of the fails after some minutes...i have axperiense this problems too until stabilize my system setup with a certain system setup....
if u don have overclock anything....search on your hardware...some may have a problem and fail in heavy conditions (likes indigo renders with full cores)
i have found indigo th most reliable and full-on stress test for extreme pc-overclk!!!
1)Core i7 965XE stock CLOCK ,PSU:CHIEFTEC 850W
M/B ASUS P6T DELUXE,WATERCOOLING ZALMAN RESERATOR 2
MEMORY:6GB CORRSAIR @1600,Ati HD 4870x2,
MONITOR:LG 1950SQ,CASE:THERMALTAKE SOPRANO
M/B ASUS P6T DELUXE,WATERCOOLING ZALMAN RESERATOR 2
MEMORY:6GB CORRSAIR @1600,Ati HD 4870x2,
MONITOR:LG 1950SQ,CASE:THERMALTAKE SOPRANO
- Bogey Jammer
- Posts: 44
- Joined: Mon Aug 13, 2007 12:37 am
- Location: France
Thanks for suggestions guys
I don't overclock my laptop, the room temp is not warm.. But I think it was not a overheat problem because vista clearly showed a messagebox "Indigo ceased to work" or something like this in english.. The system was not frozen or rebooted.
I'll tell tomorrow if the current rendering will survive.
I don't overclock my laptop, the room temp is not warm.. But I think it was not a overheat problem because vista clearly showed a messagebox "Indigo ceased to work" or something like this in english.. The system was not frozen or rebooted.
I'll tell tomorrow if the current rendering will survive.
- Bogey Jammer
- Posts: 44
- Joined: Mon Aug 13, 2007 12:37 am
- Location: France
- Bogey Jammer
- Posts: 44
- Joined: Mon Aug 13, 2007 12:37 am
- Location: France
My render machine:CTZn wrote:Me again on that, but are you running on a 32 bit system* ? If so, do you have a chance to try the faulty scene on a 64 bit rig ?
* could you give more specs please ?
- Acer aspire 5612Zwlmi
- Intel T2060 dual core 1.6 GHz
- 1GB RAM
- vista home premium 32bit
I just started to run the same scene rendering with emitting material replaced by a matt one...
Ok, the specs may be usefull, but not for me because of my poor knowledge on hardware, sorry ^^
Never heard about using Indigo in safe mode, but in your case maybe that would help ?
Now it could be usefull to know more about your scene, but again I have no precise clue on this issue. Do these debugging test you are doing, maybe remove emitters 1 by 1...
Never heard about using Indigo in safe mode, but in your case maybe that would help ?
Now it could be usefull to know more about your scene, but again I have no precise clue on this issue. Do these debugging test you are doing, maybe remove emitters 1 by 1...

obsolete asset
- Bogey Jammer
- Posts: 44
- Joined: Mon Aug 13, 2007 12:37 am
- Location: France
This is my scene I wanted to render:
Since last time I've replaced only the emitting material by a matt one. My computer managed to render it for almost 73hours. So using emitting mesh could be dangerous. The emitting meshes are supposed to be the fluo tubes on the roof.
I noticed in a crashed render that the fluo tubes were not bright and not enlightening the room. In real life we can even see that a lamp is on, in the render the tube looked like off, the car in the center didn't reflect the tubes... Is it due to a wrong setting?
I can't go forward very much in the investigation because I don't have enough information about how Indigo manages mesh emitters. And my rendering times are too long...

Don't pay attention to the noise, I'm still experiencing Indigo and this scene uses a lot of indirect light scattered by a SSS curtain behind the camera.log.txt wrote:Time elapsed: 72 h, 57 m, 42 s
Done 6748080000.00000 samples (8580.62744 samples per pixel)
25691.06371 samples / second (38.92404 micro-seconds / sample)
Since last time I've replaced only the emitting material by a matt one. My computer managed to render it for almost 73hours. So using emitting mesh could be dangerous. The emitting meshes are supposed to be the fluo tubes on the roof.
I noticed in a crashed render that the fluo tubes were not bright and not enlightening the room. In real life we can even see that a lamp is on, in the render the tube looked like off, the car in the center didn't reflect the tubes... Is it due to a wrong setting?
I can't go forward very much in the investigation because I don't have enough information about how Indigo manages mesh emitters. And my rendering times are too long...
Who is online
Users browsing this forum: No registered users and 19 guests