Page 7 of 9

Posted: Thu Nov 13, 2008 6:57 am
by pxl666
hey smart - sorry for being annoying - but is there any way to use igm's within blendigo? is it planned and possible?

Posted: Thu Nov 13, 2008 7:03 am
by Pinko5
Yes it's possible Pxl666 i use igm file with "External" type shader only restriction that i know is in the name infact the Blender shader it must be the same name of the igm file...
ciao ciao
Luca. ;)

Posted: Thu Nov 13, 2008 7:05 am
by Woodie
I found that some scenes that have history of scripts being used tend to be in some way messed up. Wasn't there a way to clear python cache in the file, so you are starting with clean slate? This might be why you guys have your mapping problems.

Posted: Thu Nov 13, 2008 7:26 am
by pxl666
Pinko5 wrote:Yes it's possible Pxl666 i use igm file with "External" type shader only restriction that i know is in the name infact the Blender shader it must be the same name of the igm file...
ciao ciao
Luca. ;)
thanks pinko

tried - doesn't work....either tried with extension - .igm and without - both fails - what i am doing wrong???

pixx attached

Posted: Thu Nov 13, 2008 7:33 am
by Pinko5
I dont know if the error can be xxxxx.igm try without.....i am working in these days on a scene with 2 external shaders and it works fine...
ciao
Luca. ;)

Posted: Thu Nov 13, 2008 7:48 am
by pxl666
Pinko5 wrote:I dont know if the error can be xxxxx.igm try without.....i am working in these days on a scene with 2 external shaders and it works fine...
ciao
Luca. ;)
i dont know...which version of indigo/blendigo are u using pinko? im using newest blendigo/indigo and tried several igm's but none of them works...are u under windows? can this be related to blender??

Posted: Thu Nov 13, 2008 8:19 am
by Juniorsatan
I would check weather the path to your mat.igm is correctly specified in your scene.igs file.

In conclusion to the error message, this was set wrongly.

Posted: Thu Nov 13, 2008 8:29 am
by pxl666
Juniorsatan wrote:I would check weather the path to your mat.igm is correctly specified in your scene.igs file.

In conclusion to the error message, this was set wrongly.
did u see the pix attached?

Posted: Thu Nov 13, 2008 8:42 am
by Pinko5
i use Indigo 1.1.14 and Blendigo 1.1.13 under windows xp pro, my shaders *.igm are both in the directory of my project i use Ruby and Diamond and they work very well... i see your image and the one reason that i could think is the extension in the name of your blender shader.....try without the extension (.igm)...
ciao
Luca. ;)

Posted: Thu Nov 13, 2008 8:45 am
by Pinko5
yes pxl666 the problem is the name of your blender material....i try with my scene to rename my ruby in ruby.igm and in this way i reproduce the same error... ;)
Luca.

Posted: Thu Nov 13, 2008 8:45 am
by Juniorsatan
Uh sry >.<

Posted: Thu Nov 13, 2008 11:20 am
by pxl666
@ Pinko - i see theres a problem with internal material names - i mean names within an igm file...i didnt get it exactly right but i see there seems to be a problem. did u try any other matt? like http://www.indigorenderer.com/joomla/in ... Itemid=107
or http://www.indigorenderer.com/joomla/in ... Itemid=107

do they work for u?

cheers

Posted: Thu Nov 13, 2008 8:18 pm
by pxl666
regarding IGM's i figured that one has to check the names WITHIN an IGM file and make sure they are the same as the names within blender/blendigo tabs (they very often are not...) and pray...i still have problems with textured/displaced/bumped matts - u have to check uv layer names within blender/blendigo tabs and within IGM....pain

anyone can tell is there workaround?

Posted: Thu Nov 13, 2008 8:44 pm
by Pinko5
I try asap Pxl666
ciao
Luca. ;)

Ok i try the material that u suggest me and you are right dont works :shock: :shock: :shock: i hope Smart tell us where is the problem or what is the metod to use them...
In my scene there are diamond.igm and Ruby.igm and they work fine... :?
Hope you undestand my poor english ;)
Luca. ;)

Posted: Fri Nov 14, 2008 12:05 pm
by Olis
Sorry I haven't responded on my error. The scene is quite large.
I looked up the default_meshes.xml and found this:
Image

It doesn't seem like Indigo accepts that.