WHD
07-15-2009, 03:32 PM
Hi All,
I've been playing around with model cycling to test out a few ideas. Primarily with respect to Onyx Tree , Poser, and Organica. There are certain things that I'd like to do and EIAS is either just not capable of these things or in some cases as with Onyx the function has been discontinued.
With respect to Tree Pro I found that I could export a series of fact files with motion out of Onyx that had wind applied. This can then be imported into EIAS and cycled to provide wind functions in Intel Mac versions of EIAS. The main bottle neck here is that I can't find an automatic way to export sequentially numbered fact files from the tree modeling modules. You must export and hand name them one by one that takes a long time. Does anyone who uses Onyx know of a way to automate this process and if not would it be worth requesting as a stop gap measure to have wind in trees in EIAS until an intel version become feasible?
With respect to other programs like Poser and Organica I am able to export multiple sequential files. The problem is that they are either 3ds or obj files. Here importing them is bottlenecked on the EIAS side where each has to be hand imported unless I'm missing a multi file import feature. I wish EIAS on file imports where you set the model type to other would hold that setting until your imports were done. As it stands now you need to reset to "all file types" for every model you import. Seems that should be easy to alter . Matt, is this something you would consider for the next version of EIAS?
Also would be nice if we could import multiples of these other file formats the way we can currently import fact file sequences in EIAS8 since the vast majority of cycled models that I end up using come from other programs and are not fact files. Anyone have a way to automate any of this that I'm not aware of?
Also, another issue is that often models come in with more than one part. It would be nice if there was a way to import say a tree that has trunk,branches,leaves as multiple separate parts,and be able to set up cycling without having to separate all thos parts for every frame. Is it possible to enable cycling to recognize the separate pieces and parent the groups to a single cycling master object or null. This is more of a feature request than a is this possible question. I know that this is more than can currently be done with the existing EIAS8 package.
Just some issues that I've run into recently that a discussion of seems would be useful.
Bill Dempsey
I've been playing around with model cycling to test out a few ideas. Primarily with respect to Onyx Tree , Poser, and Organica. There are certain things that I'd like to do and EIAS is either just not capable of these things or in some cases as with Onyx the function has been discontinued.
With respect to Tree Pro I found that I could export a series of fact files with motion out of Onyx that had wind applied. This can then be imported into EIAS and cycled to provide wind functions in Intel Mac versions of EIAS. The main bottle neck here is that I can't find an automatic way to export sequentially numbered fact files from the tree modeling modules. You must export and hand name them one by one that takes a long time. Does anyone who uses Onyx know of a way to automate this process and if not would it be worth requesting as a stop gap measure to have wind in trees in EIAS until an intel version become feasible?
With respect to other programs like Poser and Organica I am able to export multiple sequential files. The problem is that they are either 3ds or obj files. Here importing them is bottlenecked on the EIAS side where each has to be hand imported unless I'm missing a multi file import feature. I wish EIAS on file imports where you set the model type to other would hold that setting until your imports were done. As it stands now you need to reset to "all file types" for every model you import. Seems that should be easy to alter . Matt, is this something you would consider for the next version of EIAS?
Also would be nice if we could import multiples of these other file formats the way we can currently import fact file sequences in EIAS8 since the vast majority of cycled models that I end up using come from other programs and are not fact files. Anyone have a way to automate any of this that I'm not aware of?
Also, another issue is that often models come in with more than one part. It would be nice if there was a way to import say a tree that has trunk,branches,leaves as multiple separate parts,and be able to set up cycling without having to separate all thos parts for every frame. Is it possible to enable cycling to recognize the separate pieces and parent the groups to a single cycling master object or null. This is more of a feature request than a is this possible question. I know that this is more than can currently be done with the existing EIAS8 package.
Just some issues that I've run into recently that a discussion of seems would be useful.
Bill Dempsey