Indigo Renderer Forum

for the last weak or so indigo has been crashing on my after between 15 and 50 minutes. i can't figure out why. i tried reinstalling going from 101 to 104 and the results are identical.

any ideas

I'm running Vista premium BTW and i never had this problem before

Always the same scene? Had this problem in a scene of mine. It seemed like the polycount of my meshlights had something to do with it. After i reduced it, it worked fine.

I'll try a diferent scene and see. I have been working on the same scene for a while now.

Could it be that your computer is overheating?

tried a different scene and its fine.
that really bites though, cause the crashing scene is a reno i'm working on and i'm NOT going to redo it.
i'll try the problem scene from a different camera and see if that works cause thats the last change i can remember is trying to render through a new camera angle.

i wonder if i was to post the .skp file if Ono or someone in the know would be interested in tking a look at it?

just an idea...

Try to open a new project/scene/what ever and then just overtake the meshes from the old scene....

You could also try, if you can first export it as obj and then reimport it back...

i tried a select all/cut from old file, then paste in a new file and it seemed to be fine weird

now i'm trying to move my portals in the old file cause i noticed they were misaligned for some reason? i'll post results.

working fine again!

good

Sorry to get back this topic again but I had an Indigo crash after 10 hours of rendering (1.0.9 with vista premium 32bits). It is the first time it happened to me but I used many mesh emitters in my scene.
The questions:

1. Is there really a mesh emitter limitation? (faces or mesh?)
2. Does something in the computer (eg the RAM) overflow?
3. It is risky to render a very complex scene with a weak computer? (I need to render this scene for 80hours to get 8000 samples/pixels)
4. Is the problem coming from something else?

My two cents but that could be 32 bits overflow.

CTZn wrote:My two cents but that could be 32 bits overflow.

Nonsense. I've rendered more than one scene for weeks with 32-bit builds (and FYI 32-bit build doesn't mean you can't have longs and doubles)

zsouthboy wrote:

CTZn wrote:My two cents but that could be 32 bits overflow.

Nonsense. I've rendered more than one scene for weeks with 32-bit builds (and FYI 32-bit build doesn't mean you can't have longs and doubles)

I guess, that depends on your rig...


Though, it's strange that such an error occurs after 10h. A RAM overflow usually happens earlier and/or gives an error message...

There shouldn't be any emitter limit.

More than likely - it's 1) a hardware problem or 2) a threading problem.

Both are plausable.

Hard problem could include drivers deciding to misbehave, or simple over heating, or a RAM stick with some soft errors that only occur when some address is accessed in a specific way.

Threading problem could be an (unintentionally) thread-unsafe portion of Indigo simply grabbing the wrong resource at the wrong time, under some very specific circumstances.