Just reviewed the link. Thanks! And it sounds like you are having a real problem getting VW to export properly. Hopefully they fix it soon.
I wasn’t terribly clear in my response. I understand that 3D geometry would slow down the file (so I probably shouldn’t have suggested a Visual Basic plant ). 🙂
I suggested extrusions inside each plant instance in the plant tool because hope is that the simple extrusion could be mapped by twin motion, or some other rendering program upon importing the VW file. I am hoping it can “read” and convert it from a simple extrusion to a higher res plant. You are correct that I don’t want a big file on the VW side. I was hoping to only have a big file on the rendering side, filled with all of these nice, high quality plants.
When we use Lumion we pretty much model every plant (thousands) for the purpose of immersive fly-through a such, so I have no worries about the size of the file on the rendering side, but you are right, I need to keep the size of the VW file manageable so I don’t lose time. Clients seem to want to see every angle these days and they love what Lumion can do. What I don’t love is the time it takes for staff to place every plant on the rendering side. I am looking for is a way for the rendering program to semi-automatically “swap out” a simple geometry (or image prop) upon import from VW. If that makes sense. Thanks again!