what's about if indigo would only use a display buffer for the visible area. I mean if render is 6000x6000 but display window is only 800x600 it would be enogh to display the 800x600 part of the render image. Perhaps adding some scrollbars to the display window allows to scroll throug the rendered i...

Hi zsouthboy,
THX VERY MUCH
It's the great support from the comunity that pushs me forward
So I like to forward a big thank to everyone that codes, uses and comments Blendigo!

@sovakas: small other questions? when exporting materials with textures, do you copy all texture files to the same directory as the igm file or do you directly create a zip file with all inside ???

no we don't need "uv_set" for import as maxigo also ignores it. So i will do the same for blendigo. Every importer should care himself to map UV maps after import. For me this is a good way do go if everyone is OK :wink: The other question was if it's possible to handle multiple uv-sets in blender, ...

yup, will have a serie of console messages while import telling "feature XY not supported" :wink: :lol: I quite finished my XML parser that i will also use internaly for storing materials inside the blender scene file. So my material GUI will have to work directly with a "igm" like XML structure :ro...

@suvakas: ok, if maxigo ignores the uv_set while import, i can write in what ever i want :roll: . So we can let this undefined and every exporter/importer has to reset/repair the uv_set himself. @wedge: It seems that the python interface of blender only provides on UV-set. In Blender itself you can ...

@suvakas, wedge, nick: concerning UV mapping in exported materials. Suvakas in your example files (btw thanks a lot for sharing) you used <uv_set>-none-</uv_set> . What is the reason for that? How the user can rematch the uv to the mesh in maxigo? [edit] I'am not sure if it wouldn't be better do agr...

@mrCarnivore:
Thx for info, will check that asap...

check blenders console output perhaps you forgot to setup the "indigowrapper.conf" file

i think it's not important if we have 1 or 2 variable-sets. 2 seems to be simplier i think. Soon i will come up with the XML library :D - then all material data are stored as indigo XML datablocks inside blender scene. So it will be possible to save or load "*.igm" material-files. 8) The access from...

in case it has nothing to do with blendigo (you/we can check the exported xml for correctness), indigo once had uv-mapping problem when face was lying in one of the base axis-planes (xy, xz, yz) or sometimes when camera was aligned along one of the base axis (x or y or z). I don't know if this was f...

Just for test, as i had similar effect long time ago too, try to give your wall a very small rotation and/or move it small bit out of the x,y,z-axis. Or try this with the camera too (small rotation and/or shit).

I checked code but there's still a big mix between "matRGB" and "matAbs", i'am not sure if this works correctly like this in every case. I suppose it's better realy recheck/rewrite the diffuse-color and specular-absorption stuff. Before both values used the same base "matRGB" with the advantage, whe...

i don't know how indigo interpretes norrmals when normalsmoothing is deactivated. If not you need 3 normals per vertex for a cube, for a sphere you need only one normal per vertex. The count of normals depends on the object and the 3d-modeler software. If you like the represent a vertex with 3 norma...

I think UVs are related to faces. You have 12 faces with 3 points each, 12*3=36 matches your 36 UVs. Imagine that a vertex/corner of a cube has 3 faces connected and each face can have different UV for this corner. One problem u still have! the normals looks like your cube is a sphere :wink: for a r...