Just checking, you are starting the model from a default pose right? Not launching straight into an already animated pose? Syflex particularly doesn't like the base mesh being scaled in an animation scene.
On 10 March 2014 10:27, Siew Yi Liang <[email protected]> wrote: > Hi Emilio and Oscar: > > If that's the case, I'll polish up the animation first, then cache it out > and use that result to drive the cloth simulation rather than doing it all > in one scene. > > I'm still going to try and see if I can solve this problem within a > referenced workflow though when I get some spare time...I think I must have > overlooked something wrt to the way I set up the Syflex ICE tree. > (Otherwise if I don't get this working, I'll never hear the end of it from > my professor about nCloth being superior =P ) > > @ olivier: Hi Olivier, I actually ran into that problem in the main rig > scene; as you said, copy/pasting the tree resolved it. :D In this case > though because the ICE tree is referenced, I wasn't able to do that in the > animation scene...but what I'll probably do is delete the ice tree from > the referenced model, re-create the tree in the animation scene itself, and > see if that works. > > Thanks for replying guys! Have to admit caching the animation itself > wasn't the first thing that came to my mind. Again, sorry to bother with > such a simple simulation question, but it's hard to find resources on > Syflex.... > > Yours sincerely, > Siew Yi Liang > > On 3/10/2014 3:22 AM, olivier jeannel wrote: > > > I remember having sometimes weird issues (simulation behaving badly) when > changing topology of a syflex sim (for example increasing a grid density) > or copying the ice tree to another object. > Usualy copying the whole tree deleting and pasting in a fresh new icetree > solved the problems. > > > Le 10/03/2014 10:57, Oscar Juarez a écrit : > > What we do is always simulate in another scene, since we point cache > everything, we cache the simulation scene and load that cache in the > lighting scene, so we avoid issues with simulation and referenced models. > > > On Mon, Mar 10, 2014 at 10:55 AM, Emilio Hernandez <[email protected]>wrote: > >> Stupid question maybe but have you baked the syflex sim before importing >> as a reference model? >> El mar 10, 2014 10:49 AM, "Siew Yi Liang" <[email protected]> escribió: >> >> Hi all: >>> >>> I'm working on a little test animation in XSI where a guy wearing some >>> pants is doing acrobatics, and I was playing around with Syflex in order to >>> get some cloth simulation going for fun. Right now, I have a main scene >>> file that contains the rig with a Syflex ICE tree, and the simulation works >>> fine there. However, once I export it to a model and replace the path of >>> the referenced model in the scene that contains my animation, the >>> simulation fails to behave as expected. Additionally, I've noticed some of >>> the changes I made to the rig seem to be broken in the referenced scene >>> (mostly custom params that I created for the DisplayInfo in order to tweak >>> the sim). Additionally, the sim appears to behave entirely differently than >>> in the original rig scene. (I tried doing a rough animation in the original >>> scene file to test the sim behaviour and it behaved as expected) Notably, >>> when I export the model from the original scene, I get the warning: >>> >>> // WARNING : 3000 - Model Runner_Rig does not contain all inputs for >>> object Pants_M_sim_rdrGeo to perform. Imported model may not behave as >>> expected. >>> >>> I have no idea what nodes/inputs are missing though. The entire model >>> afaik should be self-contained, as it's not referencing anything else. >>> >>> I tried importing a new referenced model and copying the animation from >>> the old rig onto the new one: storing an action and then applying it >>> resulted in odd transfer: the IK handles had incorrect animation >>> transferred, but most of the other controls' animation transferred >>> correctly. I tried copying all the keys from the animated rig via the dope >>> sheet, but I couldn't paste the keys on the new model; the option was >>> grayed out (!) I didn't change anything in the rig hierarchy apart from >>> adding custom params to the DisplayInfo, so I don't think this is normal... >>> >>> Does anyone have any best practice guidelines for this where ref >>> models+Syflex is concerned? I've never run into these problems with >>> referenced models before, but then again, this is my first time playing >>> around with Syflex, so I'm not sure if I've done something wrong here. >>> (Especially wrt updating referenced models; right now I just basically >>> opened the model PPG and replaced the filename to point to the updated >>> model which I've always been doing. Is this possibly causing the issue?) >>> >>> Thanks! >>> >>> -- >>> Yours sincerely, >>> Siew Yi Liang >>> >>> > > > -- www.matinai.com
