Instancing Components

[Pibuz]

Hi Max! Yes, I do remember a technique you posted some time ago on the italian forum.. I thought that was a little more tricky than this one by Whaat, to be honest I'm kinda lazy I must say, and I find these new hints to work better and better fit my workflow.

Still, I also find that we will need a better method to guess the obj materials than trial and error. So I hope this is a basis on which a more sophisticated procedure will be built on. Go Dale!

[snorky]

...
6) Try rendering with Indigo. You will get error messages because Indigo cannot find the proper materials for the external file. Take note of the name of the material in the error message.
...

can you add a script to connect a found orphan material to an igm file by inputbox before it export to indigo???
so you avoid the error messages!!!

[Pibuz]

So Dale... I gave this a try and I must report it doesn't work for me. Problems show up after trying the render: the error Indigo gives me doesn't concern specific missing materials, but a general problem loading the mesh. I correctly pre-named the component, activated the instancing method and accurately specified the path to find it (running on XP). Tried different paths but I don't seem to be able to solve anything.

[Pibuz]

Sorry to bother. I made some tests and only few of them (ONE, to be more precise) work as they should. I'm doing tome tests with OBJs created with treeD. Note that importing the objects into SU using the traditional OBJ importer by Fluid (official SU forums) gives no error messages.

I attach two screenshots: one is from SU and the second one is from Indigo. It says something about some line3 column9.. I've followed the instructions by Whaat and the tips I was given by the great Snorky, but nothing seems to work with some models.


I can attach one of them if you want to try..
http://www.box.net/shared/imo14or1ta

[snorky]

ehi Pibuz...
first: wrong path!!! works only with whole path, with file.extension.
second: line " vn NaN NaN NaN " on obj file may cause error

[Pibuz]

Hi Max! I understand the first error (I don't know why I didn't include the extension....I usually do )

But I don't manually WRITE the obj, that is just as exported from TreeD!
How can I fix that?

EDIT: fixing the path doesn't solve the problem, same exact issue

[snorky]

Hi Max! I understand the first error (I don't know why I didn't include the extension....I usually do )

But I don't manually WRITE the obj, that is just as exported from TreeD!
How can I fix that?

EDIT: fixing the path doesn't solve the problem, same exact issue

problem solved!
I fix it with meshlab... is simple and fast.

great tree!

[Pibuz]

...I'd rather say "problem avoided"

I'd very like to know why the SkIndigo external reference doesn't work...maybe Whaat can tell...

[Pibuz]

BTW, MeshLab "fixed" the geometry problem indeed..
Now...is it possible to rotate the axis of the mesh?

[snorky]

BTW, MeshLab "fixed" the geometry problem indeed..
Now...is it possible to rotate the axis of the mesh?

http://meshlab.sourceforge.net/wiki/ind ... ing_a_Mesh

[Pibuz]

First forest of external components. I used the "fixed" tree Thank you Snorky!

[fractal.design]

Far out, that's looking great.

[japc]

Howw this really works!

[Frutiger]

Jealousy consumes me. I'm going to give this another try on my Mac. Any idea if my task is a futile one, Whaat?

[FoXar]

Wow, this is really staggering! Very nice, can't wait till this option is available! How will you be able to change the materials etc?

Cheers,
Roo Evans