long UI times when large sim in scene..

[Chris Pember]

I don't know if this is a bug, or something else. I have a sim with 250+mb/frame size for the data,and it seems to take a very, very long time to pull up the UI. I can see this if displays are enabled for the sim, but I have the main viewport display disabled, yet it seems to still load the data.. disable the data channel below it (fuel, fire, etc) and it gets speedy again.

tks!

C

[sitnisati]

Chris,

Does this happens during the simulation ?
If so, then you must know that FumeFX fully utilize CPU during simulation and
there's a little of CPU time left for other tasks.

Regards,

Kresimir

[Chris Pember]

Hey Kresimir,

nope, this is just opening the ui after the sim is complete..
to repro (at least, I can here)

1. sim a fairly detailed scene (i guess one frame should be fine, mine was 240mb for the sim data for one frame)
2. disable the "enable display" toggle under the viewport settings in the command panel rollout
3. close the floater UI
4. open the floater UI

the result should be a bit of a pause when you call up the floater UI, even though it shouldn't be loading anything into the view. At least, that's what I'd expect with a master toggle.

5. close the UI again, and disable the channels that are checked (like, smoke, fire, etc)
6. reopen the floater again

result should be very, very fast opening of the UI (I don't think it makes a difference if the main "enable display" toggle is on or off at this point, I can't remember offhand, and I don't have fume here in front of me atm)

Of course, I could be reading into all the display stuff incorrectly I've done that a lot before. It just seemed to make everything sluggish with a huge sim unless i shut it all off.

regards,

Chris

[amckay]

hey bud - yeah I find viewport draws slower than the preview window if you are doing complex sims. but if you have that stuff off you'd think that the ui would pop up quickly as all the settings are stored in the container not the file right?

you can check its not a memory footprint by changing the big sim output path to a new file and then try to reopen it and see if it takes forever to load still or if it suddenly is instant. and if it is then thats obviously reading the file in.

yeah that is a bit odd. Hopefully Kreso can verify whether its reading either the fdc or fxd info upon loading.

I tend to do garbage cleanups constantly too just to flush any excess memory after big ass sims. doesnt help 'tooo' much but can help from crashing if you're doing sims all day long.

-Allan

[Chris Pember]

Hey Dude, yeah, I'll give that a shot in a couple minutes, I do think it's still trying to load the sim tho, unless the channels are all off..

ttl

c