07-29-2014, 03:51 PM
This is something I've only seen in Fumefx maya (linux). Never on MAX.
But I've noticed it in many scenes now-so it seems like something is not quite 'cleaned up' right when you load an existing fumefx in a scene. Possibly it has to do with sim start frames that are not 1 or 0-but who knows?! I'm not certain if its always the initial scene loaded in the maya session either-but it might be.
What you get-
You load an existing Fumefx scene-begin a sim- and the first results look exploded-like your velocities of time scale are set to a rediculous amount. Also it can sometimes drive the memory up exponentially as Fume FX 'tries' to calculate some crazy exploded values, grid sizes as adaptive grid tries to keep up. Maya may crash too!
I've experienced this with setups that i am familiar with-and know these 'anomaly sims' make no sense.
I simply stop the sim. And start it over again. Now the result is as expected. The 'anomaly sim' won''t return unless i exit maya and load the scene again. I've checked with colleagues (on maya linux) and its true for them as well. Not so bad as long as you work on your own machine and catch it happening.
BUT I could see this being very problematic doing sims on a farm-forcing users to sim on their own machines. This could be a show stopper if they need to farm sim.
Repro-
-This will never happen with a brand new Fumefx added to a scene. It must reside in the loaded scene already.
-It always sorts itself out correctly the *second* attempt at doing a sim.
-Possibly related to having Maximum Simulation Steps to other than '1'. I often set to '3'.
Can you repro with any of the scenes I've sent you in the past?
If not I'll try and make you one.
I'd also like to know if anyone else on maya has experience this. Possibly it could be our pipeline
and the scene presets we load maya with.
But I've noticed it in many scenes now-so it seems like something is not quite 'cleaned up' right when you load an existing fumefx in a scene. Possibly it has to do with sim start frames that are not 1 or 0-but who knows?! I'm not certain if its always the initial scene loaded in the maya session either-but it might be.
What you get-
You load an existing Fumefx scene-begin a sim- and the first results look exploded-like your velocities of time scale are set to a rediculous amount. Also it can sometimes drive the memory up exponentially as Fume FX 'tries' to calculate some crazy exploded values, grid sizes as adaptive grid tries to keep up. Maya may crash too!
I've experienced this with setups that i am familiar with-and know these 'anomaly sims' make no sense.
I simply stop the sim. And start it over again. Now the result is as expected. The 'anomaly sim' won''t return unless i exit maya and load the scene again. I've checked with colleagues (on maya linux) and its true for them as well. Not so bad as long as you work on your own machine and catch it happening.
BUT I could see this being very problematic doing sims on a farm-forcing users to sim on their own machines. This could be a show stopper if they need to farm sim.
Repro-
-This will never happen with a brand new Fumefx added to a scene. It must reside in the loaded scene already.
-It always sorts itself out correctly the *second* attempt at doing a sim.
-Possibly related to having Maximum Simulation Steps to other than '1'. I often set to '3'.
Can you repro with any of the scenes I've sent you in the past?
If not I'll try and make you one.
I'd also like to know if anyone else on maya has experience this. Possibly it could be our pipeline
and the scene presets we load maya with.