Indigo WinXP error

Psychotron80 · Post by **Psychotron80** » Mon Jan 12, 2009 10:12 pm

Hi to everybody,
with the latest indigo (1.1.15) I keep on getting the Windows error notification (see image below) more and more frequently (I model use Blender and the latest Blendigo). Notice that when the error appears, Indigo often keeps running without displaying any kind of error.

Since the dialog itself does not give any clear information on what is going on, can someone help me to diagnose the problem?

Thanks in advance to everyone,

Psy

PS: sorry if this is not the right place to post. In case, please tell me and I will move my request to the relevant forum.

ozzie · Post by **ozzie** » Mon Jan 12, 2009 10:51 pm

could you past log?

3 questions:

1- do you use exr maps?
2- do you scale your scene?
3- how big is the igi file?

Psychotron80 · Post by **Psychotron80** » Mon Jan 12, 2009 11:45 pm

log.txt is always empty: this problem is already being investigated at

http://www.indigorenderer.com/joomla/fo ... 6990#66990

1- no EXR, using physical sky+sun
2- no scaling
3- where can I find it? you mean the default.igs file? it's 8,22Mb

I have some other info: the error seems to occur much more often if I set LM probability=0.5 instead of the default 0.4 in Blendigo...

Psychotron80 · Post by **Psychotron80** » Tue Jan 13, 2009 12:50 am

ozzie, ok, I set "save IGI" in Blendigo and I got an igi file of 37Mb

CTZn · Post by **CTZn** » Tue Jan 13, 2009 12:59 am

As you mentionned the first post is not informative at all.

1 - 32/64 bits ? onboard ram ?
2 - if 32b watch Indigo ram consumption peak in task manager
3 - oversampling ?
4 - exterior, portals ? are they closing the inner volume well ?
5 - remove meshes 1 by 1 and try again and over ?
6 - more to say ?

everything you can tell about the scene may help, you will learn the significant bits progressively.

ozzie · Post by **ozzie** » Tue Jan 13, 2009 2:35 am

The best way is what CTZn said:
copy meshes one by one to other layer and findout which is "corupted".

Psychotron80 · Post by **Psychotron80** » Thu Jan 15, 2009 8:16 am

CTZn:
1. I am using a DELL Precision M4300 laptop, so 32bits
2. RAM consumption peak is far below the available physical memory
3. supersamples=2
4. exit portals should be closing all the apertures correctly (I snapped the vertexes of the portals to the wall vertexes: is this enough?)

Now I am trying to copy meshes to other layers, as ozzie said, and finding the corrupted one, but it obviously takes a long time.

One question: what does "corrupted" mesh mean? What kind of (common) mistakes lead to mesh corruption? I am quite a n00b in Blender, so I might have done something wrong in the modeling....

If anyone had a small time slot, then I could also pm him the scene so that he could take a look at it...but I understand this is difficult.

Thanks again!

Psy

ozzie · Post by **ozzie** » Thu Jan 15, 2009 10:32 am

Psychotron80 wrote:CTZn:

One question: what does "corrupted" mesh mean? What kind of (common) mistakes lead to mesh corruption? I am quite a n00b in Blender, so I might have done something wrong in the modeling....

If anyone had a small time slot, then I could also pm him the scene so that he could take a look at it...but I understand this is difficult.
Psy

For me it was usually scaling.

Psychotron80 · Post by **Psychotron80** » Thu Jan 15, 2009 10:37 am

ozzie, what do u mean by "scaling"? In Blender, you mean scaling in object mode or in edit mode? or in Blendigo using the worldscale control?

ozzie · Post by **ozzie** » Thu Jan 15, 2009 10:44 am

In object mode

CTZn · Post by **CTZn** » Thu Jan 15, 2009 12:23 pm

(I snapped the vertexes of the portals to the wall vertexes: is this enough?)

No, this does not ensure intersection ! That may, or may not actually, very error prone. Not sure how Indigo handles portals errors... does it just... crash ?

Edit: laptop, huh ? no heat concerns, are you auditing this (mobo tools) ?

Post by **OnoSendai** » Thu Jan 15, 2009 12:34 pm

No, indigo does not crash on portal errors, as far as I know.

CTZn · Post by **CTZn** » Thu Jan 15, 2009 1:10 pm

That's correct, it does not crash on misplaced portal, tryied that.

Psychotron80 · Post by **Psychotron80** » Thu Jan 15, 2009 7:34 pm

so in principle I should "compenetrate" the portal into the wall by some mm?

could messy normals be causing the problems? or a bad mesh topology (but I have no idea of what this means exactly...)?

thanks guys, and thanks boss!

Psy

ozzie · Post by **ozzie** » Thu Jan 15, 2009 8:51 pm

and sometimes scaling objects and camera (in object mode)

Indigo WinXP error

Indigo WinXP error

Who is online