Reading through the thread that you linked to, was strangely comforting, knowing that they will be ironing out these bugs.
Though 3 months without *any* update for a paid product is a little unsettling.
The software should not crash
. This is a bug that needs fixing asap. I've been on Indigo forums and yes, there are a couple of threads that say the implementation of the plugin is not optimal.
Specifically the second response on this thread: http://www.indigorenderer.com/forum/viewtopic.php?f=7&t=13462&sid=99cb33c0639da24a768c49d31a2771c1
We know IClone is an animation / video prod software (It's not DAZ which is more of a stills production software), so to implement a professional render plugin which takes about 3 hours! just to export data to the renderer is less than an optimal way to implement an interface. It's akin to a brute force approach.
As it stands, since i'm not a programmer I've had to go find a "Macro" software to write windows macros to:
1) export a single frame to indigo
2) tweak the best lighting/camera framing/background variables in Indigo.
3) Then save the IGS from Indigo
4) Copy the first half of the IGS file (which is a standard xml file) upto the first instance of <metadata> to all
the IGS frames exported from iClone.
You can imagine on 10 second animation at 25fps, how many manual cut / pastes this would need. And I'm not even talking about the nightmare if the camera were to move.
Luckily for the project I'm working on, the camera is stationary and only the talent moves.
So using MacroExpress to drill through the Directory of IGS files, search for the word <metadata>, delete everything before it, then paste from clipboard the tweaked settings block
For now I just hope the random crashing on export bug gets fixed.
4 Years Ago by