Problem with keyframing fluid inflow properties #27306

New Issue

Stuart murra · 2011-05-06T13:44:53+02:00

Stuart murra commented

2011-05-06 13:44:53 +02:00

%%%I have a strange problem with my fluid inflow object, in that when it has no keyframes applied to any of its properties it flows perfectly fine, however as soon as I apply more than one keyframe (say for example one at frame 1 for the emitter to be "active" and one at frame 80 to be "inactive") the flow of the emitter does weird things.

If I do the simple on/off toggle keyframes, it tends to emit at the correct force for a few frames, but then it dies down and doesnt emit much or anything at all. If I up the resolution, it can be seen that it seems to only be emitting from around the edges of the object.
If I set up keyframes altering the velocity of the inflow from 0 to 50 over the space of 50 frames for example, the emitter doesn't emit anything for a while and then all of a sudden spurts like a fountain at a random frame within that time-frame. For this to happen I generally have to have the domain scale set high like 8m or above, gravity at -25ish and key the velocity to rise to above 20 or so.

Here are video examples of what I'm talking about in scenario 1. The first one has no keyframes on the activate channel and is how it should look, the second one is how it looks with a keyframe setting it as active on frame 1 and inactive on frame 80.

No keyframes: http://www.youtube.com/watch?v=q5HYRtogEa8
Keyframes: http://www.youtube.com/watch?v=Y4N60W5vuN4

I've attached blend files illustrating the problem.

I hope I've done this right as I've only been using Blender for two days but I can't find a solution to this anywhere!

Blender 2.57.1 r36339 64bit
Windows 7 64bit
Intel Core2 Duo E8500 3.61ghz
4GB RAM
AMD Radeon HD4860%%%

%%%I have a strange problem with my fluid inflow object, in that when it has no keyframes applied to any of its properties it flows perfectly fine, however as soon as I apply more than one keyframe (say for example one at frame 1 for the emitter to be "active" and one at frame 80 to be "inactive") the flow of the emitter does weird things. 1) If I do the simple on/off toggle keyframes, it tends to emit at the correct force for a few frames, but then it dies down and doesnt emit much or anything at all. If I up the resolution, it can be seen that it seems to only be emitting from around the edges of the object. 2) If I set up keyframes altering the velocity of the inflow from 0 to 50 over the space of 50 frames for example, the emitter doesn't emit anything for a while and then all of a sudden spurts like a fountain at a random frame within that time-frame. For this to happen I generally have to have the domain scale set high like 8m or above, gravity at -25ish and key the velocity to rise to above 20 or so. Here are video examples of what I'm talking about in scenario 1. The first one has no keyframes on the activate channel and is how it should look, the second one is how it looks with a keyframe setting it as active on frame 1 and inactive on frame 80. No keyframes: http://www.youtube.com/watch?v=q5HYRtogEa8 Keyframes: http://www.youtube.com/watch?v=Y4N60W5vuN4 I've attached blend files illustrating the problem. I hope I've done this right as I've only been using Blender for two days but I can't find a solution to this anywhere! Blender 2.57.1 r36339 64bit Windows 7 64bit Intel Core2 Duo E8500 3.61ghz 4GB RAM AMD Radeon HD4860%%%

Stuart murra commented

2011-05-06 13:44:53 +02:00

Changed status to: 'Open'

Stuart murra commented

2011-05-06 13:46:44 +02:00

%%%I should add that the same thing happens as instance 1) when I create keyframes scaling the inflow object too.%%%

Ton Roosendaal commented

2011-05-10 17:21:19 +02:00

%%%Hi,

The fluid system has been coded with quite a static scene graph in mind, animation support was added later on in small steps.
Even though Blender allows to set keys on any property, many of these won't work. Your case has been noted on our wiki too:
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Fluid_Simulation

it would be a good idea to simply exclude un-animatable variables from RNA. use this call in rna:
RNA_def_property_clear_flag(prop, PROP_ANIMATABLE);
%%%

%%%Hi, The fluid system has been coded with quite a static scene graph in mind, animation support was added later on in small steps. Even though Blender allows to set keys on any property, many of these won't work. Your case has been noted on our wiki too: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Fluid_Simulation it would be a good idea to simply exclude un-animatable variables from RNA. use this call in rna: RNA_def_property_clear_flag(prop, PROP_ANIMATABLE); %%%

Stuart murra commented

2011-05-10 17:42:54 +02:00

%%%I see, thanks for the clarification!%%%

Ton Roosendaal commented

2011-05-12 16:57:18 +02:00

%%%Daniel: when you have time, can you check the properties for fluid/smoke and disable the ones that are not animatable? Thanks!%%%

Daniel Genrich commented

2011-06-07 22:18:02 +02:00

%%%This bug report is valid. It's not only broken for on/off, but also for roation/scale/animation. The problem manifests for inflows (i guess other types are affected, too), where the simulation doesn't init the whole object with fluid but only some of the boundary. No idea how that functionality got broken from 2.49b to 2.5x.

I'm on it.

Thanks for reporting.%%%

%%%This bug report is valid. It's not only broken for on/off, but also for roation/scale/animation. The problem manifests for inflows (i guess other types are affected, too), where the simulation doesn't init the whole object with fluid but only some of the boundary. No idea how that functionality got broken from 2.49b to 2.5x. I'm on it. Thanks for reporting.%%%

Thomas Dinges commented

2011-12-30 01:33:59 +01:00

%%%After 6 months, any updates? ;-)
%%%

%%%After 6 months, any updates? ;-) %%%

Sergey Sharybin commented

2012-04-03 15:16:47 +02:00

%%%Animated inflow and outflows were added to our TODO wiki a while ago. Will mark report as a TODO now.%%%