Page MenuHome

Many properties of Ocean Modifier are animatable when they should not (e.g. Wind Velocity).
Closed, ResolvedPublicBUG


System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.77

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: rB211b6c29f771

Short description of error
When adding keyframes to the "Wind Velocity" parameter within the Ocean Modifier, it does not update the value when played. Clicking on the box for Wind Velocity will update the value to the correct number, but then it will stay stuck on that number and the model will also stay stuck to that value until clicked on again. I also tried saving the animation to see if it might be a viewport issue, but it rendered with the same issue.

Exact steps for others to reproduce the error
Add a plane> add ocean modifier to the plane
Frame 1 Ocean Modifier keyframes: Time = 1.00 Wind Velocity = 1m/s
Frame 250 Ocean Modifier keyframes: Time = 10.00 Wind Velocity = 30m/s
Play the animation from frame 1 and the plane will move based on the wind velocity that appeared that last time you clicked the parameter.
Ex: If the last time you clicked on the Wind Velocity parameter was to enter 30m/s, then when you play the animation it will move using the value of 30m/s even though the box may have reset to 1m/s at the beginning of the animation.

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Confirmed.Jun 29 2020, 8:16 PM
Bastien Montagne (mont29) claimed this task.

Thanks for the report, but there is no bug here, we do not want to update the whole UI at every frame for performances reasons, and that would be the only way to ensure all animated properties are updated real time in UI during animation playback. Just hovering the settings with the mouse is enough to update them though.

I just checked again and I don't believe the problem is invalid and it still exists even in Blender 2.9.
The problem about the UI is not the main problem I want to address.

The main problem is that using keyframes with the wind velocity variable does not change the animation as it plays or when it is rendered.
Ex: If I click on frame 1 and click on the wind velocity box it should have a value of 1m/s. When I hit play, the wave animation itself (not just the number in the UI) does not change from the setting of 1m/s.

It will loop continuously at the wind velocity of 1m/s as if there was no keyframe other keyframe to transition to.

If I go to frame 250 and click on the wind velocity box which should have a value of 30m/s and the hit play again. The entire animation will loop with the wind velocity setting of 30m/s.

Ah OK, in fact I think there are many properties in this modifier that should not be animatable, since they are only used once when initializing the simulation. Will fix that.

Bastien Montagne (mont29) renamed this task from Ocean Modifier > Wind Velocity does not update with keyframes when played. to Many properties of Ocean Modifier are animatable when they should not (e.g. Wind Velocity)..Sep 25 2020, 5:17 PM
Bastien Montagne (mont29) reopened this task as Confirmed.
Bastien Montagne (mont29) changed the subtype of this task from "Report" to "Bug".
Bastien Montagne (mont29) moved this task from Backlog to Bugs (Modifiers) on the Modeling board.

So just to clarify. keyframing the wind velocity is not currently possible with the Ocean modifier?

I was trying to animate a time lapse of the waves changing direction and speed over time. I figured out a work around by using many ocean modifiers and fading them in and out, but it seemed like all that would be unnecessary if I could just keyframe more properties within one instance of the ocean modifier.

If not many people are doing stuff like this I suppose it's a non issue, but I just wanted to share my opinion.

Anyway, thank you for taking a look!

Correct, most of the Ocean modifier's parameters are actually not animatable, since they are set only once in the solver at the init step of the simulation.