Instancing Components
Re: Instancing Components
So, sounds like this feature may be launching with Indigo 3.0? I'm betting whaat's a very busy wizard right now.
Re: Instancing Components
I HATE having to put plants in Sketchup files since Google still hasn't figured out how to make Sketchup handle large poly counts. This is awesome! Thanks Whaat, you do great work!
Intel Core-i7 @ 4.0 GHz | GTX 580 | 12 GB RAM
Re: Instancing Components
I tried this instancing method and I got the model to load into indigo with all the correct materials, but it doesn't seem to keep the tree object in the correct location or orientation. No matter how far I zoom out, when the image loads in indigo the tree is always appearing right in front of the camera. Any ideas on how to fix this?
Re: Instancing Components
simple.
external model have different SCALE ORIGIN and AXES
2 way...
1) modify source (external object); try this:
http://meshlab.sourceforge.net/
2) modify component:
exchange axes "Y" and "Z"
scale "up" component's objects
and scale "down" component
example
scene in meter, external object in inch
real tree 10meters, external object 393.70inches --> indigo render 393.70meters
edit component
scale all faces of component x39.37
close component
scale component x0.0254
result "fake" 10meters tree but scaled correctly.
external model have different SCALE ORIGIN and AXES
2 way...
1) modify source (external object); try this:
http://meshlab.sourceforge.net/
2) modify component:
exchange axes "Y" and "Z"
scale "up" component's objects
and scale "down" component
example
scene in meter, external object in inch
real tree 10meters, external object 393.70inches --> indigo render 393.70meters
edit component
scale all faces of component x39.37
close component
scale component x0.0254
result "fake" 10meters tree but scaled correctly.
Re: Instancing Components
Any word on this working with Skindigo 3 on a mac, Whaat?
Re: Instancing Components
I'm just understanding this. Thanks Snorky!snorky wrote:simple.
external model have different SCALE ORIGIN and AXES
2 way...
Re: Instancing Components
I intend for this to work on a Mac as well.Frutiger wrote:Any word on this working with Skindigo 3 on a mac, Whaat?
Re: Instancing Components
Actually, it does work on mac! Sorry for the misleading information earlier. I was doing something wrong.Whaat wrote:I intend for this to work on a Mac as well.
Re: Instancing Components
So here's the problem I'm running into.
I'm using some xFrog trees that I have that need to be scaled by a factor of .0254 (as revealed by the illustrious Snorky) in order to be rendered in the proper size when referenced as an external mesh. I've been using Meshlab to do the scaling and resaving, and it does a great job, especially for a free program!
Unfortunately here's where the problems arise. After exporting a file from Meshlab and linking it as an external mesh in skindigo, the textures appear to lose their naming and take on some sort of default name (eg material_0, material_1, etc). This isn't a problem when using only one external reference, but when using multiple external meshes the names quickly start to overlap, as they're all looking for "material_0". I end up with forests that look like this:
Firs with birch bark and conifer leaves. Lovely.
It seems the issues is in Meshlab's renaming of the textures on export. It gives a prompt to rename the textures on export but when I try it use it it crashes pretty hard. Here's what the prompt looks like. So, any clues as to a workaround? Or is there another program that can edit .obj or .3ds files that also would allow me to rename textures so they don't overlap?
I'm using some xFrog trees that I have that need to be scaled by a factor of .0254 (as revealed by the illustrious Snorky) in order to be rendered in the proper size when referenced as an external mesh. I've been using Meshlab to do the scaling and resaving, and it does a great job, especially for a free program!
Unfortunately here's where the problems arise. After exporting a file from Meshlab and linking it as an external mesh in skindigo, the textures appear to lose their naming and take on some sort of default name (eg material_0, material_1, etc). This isn't a problem when using only one external reference, but when using multiple external meshes the names quickly start to overlap, as they're all looking for "material_0". I end up with forests that look like this:
Firs with birch bark and conifer leaves. Lovely.
It seems the issues is in Meshlab's renaming of the textures on export. It gives a prompt to rename the textures on export but when I try it use it it crashes pretty hard. Here's what the prompt looks like. So, any clues as to a workaround? Or is there another program that can edit .obj or .3ds files that also would allow me to rename textures so they don't overlap?
Re: Instancing Components
I know it's not the best solution but if you are running into naming overlaps, I recommend only using .obj files. With them, you can open up the file in Notepad++ and do a Find/Replace operation to create the required unique material names (look for a 'usemtl' command). I have done this with all my Xfrog models (since almost all of them have a material named 'bark' for example. I rename it to something like 'EA15_y_Bark' - EA15_y.obj is the name of the .obj file)Frutiger wrote: So, any clues as to a workaround? Or is there another program that can edit .obj or .3ds files that also would allow me to rename textures so they don't overlap?
I am thinking of ways to handle such naming conflicts with SkIndigo but for now, it has to be done manually or with an external app such as MeshLab.
Re: Instancing Components
Laborious, but totally worth it. This works like a charm.Whaat wrote:I know it's not the best solution but if you are running into naming overlaps, I recommend only using .obj files. With them, you can open up the file in Notepad++ and do a Find/Replace operation to create the required unique material names (look for a 'usemtl' command). I have done this with all my Xfrog models (since almost all of them have a material named 'bark' for example. I rename it to something like 'EA15_y_Bark' - EA15_y.obj is the name of the .obj file)
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Instancing Components
Use Blender to scale and convert your models!
Re: Instancing Components
I tried! The most recent blender mac build crashes hard in OSX 10.7 for whatever reason.
This manual naming method is super effective. And as an added bonus, I look like a pro when I'm "searching through the code". My co-workers think I'm some kind of magician.
This manual naming method is super effective. And as an added bonus, I look like a pro when I'm "searching through the code". My co-workers think I'm some kind of magician.
Re: Instancing Components
If anyone else is having similar problems with Blender with OSX Lion, here's a link to an updated version that works. It doesn't seem to be on the main Blender site. lender site.
Who is online
Users browsing this forum: No registered users and 30 guests