we have noticed dramatically increased rendering times for fume 2, not sure why or if there is a way to solve this.
If anyone else has noticed this let me know, and better if you know how to fix it that would be great. The node running the sim are at like 2 or 3 percent processor usage…
So far I’m not having much luck simulating on the farm using Deadline. When I submit a simulation, I set it up the same way i do in Backburner in regards to how I enable Fume for network simulating. Which, according to the deadline manual is all i need to do…oh, and I “Disable Progress Update Timeout”
When i submit the sim, it gives every indication that it’s working. It saves out .fxd files to the directories that I specify and once the sim is done it renders a .tga file. The problem is that the .fxd files are only a few “k” each and are essentially “empty” files. When I reopen the scene to render the simulation I get “Missing Frame” in the fume preview window.
Sims work through backburner, but not through deadline and I’m wondering what I’m missing?
thanks for any help
-b
That’s strange. When you submit the job to backburner, does it split up the job into multiple tasks (ie: one per frame), or is it a single task that covers the entire frame range? I’m just trying to get a sense of how backburner does things to figure out why it’s not working as expected in Deadline.
Cheers,
I submit it as a single task. Basically what I’m doing is submitting a single frame to render, and with the backburner mode button toggeled in fume it submits the job to one machine (since there’s only 1 render task). When the job gets picked up it runs the sim for the specified frame range and then spits out a render in order to fulfill it’s obligations.
I forgot to mention, I’m using FumeFX2.1a and Deadline 4.1 if that helps at all. both are the most up-to-date version that i know about.
thanks for any additional insight.
-b
Is that just for backburner, or is that also the case with Deadline?
Thanks!
also the case for deadline. i submit a single frame for render, same as I do when i submit to backburner.
like i said, when i do this, it gives the appearance that it’s working correctly…it saves out the full range of .fxd files and when the actual simulation is complete it saves out the frame that i submitted.
curiouser and curiouser…
I’m sure I’ve seen this situation before…I’m just really struggling to remember what caused it.
I’ll ask around the studio tomorrow to see if someone remembers…
At the moment, I’m thinking its something in the Fume setup config which either needs fixing or resetting…
Does this issue occur on a fresh FumeFX setup in a fresh 3dsMax scene?
Mike
Hey Mike,
Yeah, if you find anything that could help me figure this out that would be wicked. I’m not looking forward to having to turn off deadline in favor of turning on backburner on my fume nodes…that was a big part of why we switched over to deadline in the first place…to consolidate all of our rendering and not have to have different render managers for different apps.
so far, this has been the only real speed bump…it’s been working great with max, maya, nuke and krakatoa…just doesn’t seem to wanna play well with fume simulations (fume renders work fine).
thanks
-b