no extra tags needed, but not really optimized on runtime (image a scene with 1000+ objects
Indigo Exporter for 0.7t5 - beta release
I see the problem...
It is perhaps possible to exclude C4D instances from this checking loop! because all instancing links back to the original Mesh object, so checking 10000 instances of some grass mesh would be simply a waste of time.
**EDIT**
oh, now I see that you only check Indigo tagged objects
The most Scenes with 1000+ objects heavily use instances,
so I don't think its such a big problem...
It is perhaps possible to exclude C4D instances from this checking loop! because all instancing links back to the original Mesh object, so checking 10000 instances of some grass mesh would be simply a waste of time.
**EDIT**
oh, now I see that you only check Indigo tagged objects
The most Scenes with 1000+ objects heavily use instances,
so I don't think its such a big problem...
polygonmanufaktur.de
looks very promissing, I just wait for your next version to give my finished Wildcat a try in indigo 
would your instancing check also work for objects in an array object?
would your instancing check also work for objects in an array object?
polygonmanufaktur.de
he he ^^fused wrote:@zomB:
hmmmm... maybe?
At last it should be easy to check
If C4D defines instances internally all the same way, even MoGrap stuff
would benefit from your instancing check
BTW:
It seems I found the issue about the "Camera doesn't get exported" bug No. 12, I couldn't reproduce...
It occurs if you have set NO "Indigo render settings" Tag
Talking about the camera... it seems your exporter just exports the default camera settings,
ignoring all changes you did FOV etc. can you confirm this?!
polygonmanufaktur.de
its my 400€ Job to avoid getting insane of sitting 24/7 infront of the computerfused wrote:you have to work on sundays?
that sucks pretty much.
I'm a "Logen Steward" in the Color Line Arena in Hamburg, serving drinks etc.
money is Ok, but all the nice Lady's you work with are a nice contact to the "outside world" ^^
igm support is the less interesting feature to implement I think.fused wrote: load and save .igm wont be in the release anyways... still have no solution to the string conversion(and im pretty much too lazy to think of sth on my own
)
I'm hot on instancing, and fixed Bug No 1
I just hope I'm not to drunk after work, to test the new version
(another benefit of this Job ^^)
polygonmanufaktur.de
Who is online
Users browsing this forum: No registered users and 36 guests

