Missing Animation Update for Surface Resolution U & V #59176

New Issue

William Reynish · 2018-12-11T11:10:07+01:00

William Reynish commented

2018-12-11 11:10:07 +01:00

System Information
Operating system: macOS 10.14.1 (18B75)
Graphics card: Intel Iris Plus Graphics 640 1536 MB

Blender Version
Broken: example: 2.79b release & 2.80
Worked: It seems to be a very old bug - never worked it seems

Short description of error
When keyframing the Surface U or V values, the viewport is not updated to reflect the changes

Exact steps for others to reproduce the error

Add a Surface object type
Insert a keyframe for the U or V values
Change frame and insert a different value
Scrub the playhead or play animation - the viewport does not update to reflect the value.

**System Information** Operating system: macOS 10.14.1 (18B75) Graphics card: Intel Iris Plus Graphics 640 1536 MB **Blender Version** Broken: example: 2.79b release & 2.80 Worked: It seems to be a very old bug - never worked it seems **Short description of error** When keyframing the Surface U or V values, the viewport is not updated to reflect the changes **Exact steps for others to reproduce the error** - Add a Surface object type - Insert a keyframe for the U or V values - Change frame and insert a different value - Scrub the playhead or play animation - the viewport does not update to reflect the value.

William Reynish commented

2018-12-11 11:10:07 +01:00

Added subscriber: @WilliamReynish

Sebastian Parborg commented

2018-12-14 18:48:06 +01:00

Added subscribers: @brecht, @ZedDB

Sebastian Parborg commented

2018-12-14 18:48:06 +01:00

@brecht who to assign this to?

Bastien Montagne was assigned by Brecht Van Lommel

2018-12-14 18:56:12 +01:00

Brecht Van Lommel commented

2018-12-14 18:56:12 +01:00

It's kind of random who to assign this to, feel free to reassign.

Bastien Montagne removed their assignment 2019-06-06 11:51:24 +02:00

Sergey Sharybin was assigned by Bastien Montagne

2019-06-06 11:51:24 +02:00

Bastien Montagne commented

2019-06-06 11:51:24 +02:00

Added subscribers: @Sergey, @mont29

Bastien Montagne commented

2019-06-06 11:51:24 +02:00

This is actually a topic for @Sergey I think… It’s not only affecting preview U/V resolution (cyclic toggle e.g. is not handled either), and it’s affecting all kind of obdata (geometry data-blocks) I think. At least am getting the same kind of non-update behavior when trying to key auto-smooth toggle and value of a mesh e.g.

@Sergey I guess those are missing relations in the depsgraph? This is not a regression though, so nothing like high priority task, just nice to check at some point. Or I don’t mind diving into this a bit more, if you can give me some hints of what to check.

This is actually a topic for @Sergey I think… It’s not only affecting preview U/V resolution (cyclic toggle e.g. is not handled either), and it’s affecting all kind of obdata (geometry data-blocks) I think. At least am getting the same kind of non-update behavior when trying to key auto-smooth toggle and value of a mesh e.g. @Sergey I guess those are missing relations in the depsgraph? This is not a regression though, so nothing like high priority task, just nice to check at some point. Or I don’t mind diving into this a bit more, if you can give me some hints of what to check.

Sergey Sharybin commented

2019-06-06 12:35:42 +02:00

@brecht, @mont29, the auto-smooth we should be able to fix. However, the curves/surfaces i'm not sure we can/should support.

Changing resolution on a Curve datablock goes and changes resolution on every spline. I don't think that would be a good idea to do such kind of updates from animation.
Cyclic and order i even more tricky, since they have some hidden inter-dependnecies via knots.
Cyclic will also affect handles, which might not be desirable as well.

Additionally, animating such settings makes it impossible to have motion-blur working for such objects.

Think it's easier and more predictable to simply consider those settings non-animatable rather that falling into this rabbit hole.

For the mesh settings i've created D5030.

@brecht, @mont29, the auto-smooth we should be able to fix. However, the curves/surfaces i'm not sure we can/should support. Changing resolution on a Curve datablock goes and changes resolution on every spline. I don't think that would be a good idea to do such kind of updates from animation. Cyclic and order i even more tricky, since they have some hidden inter-dependnecies via knots. Cyclic will also affect handles, which might not be desirable as well. Additionally, animating such settings makes it impossible to have motion-blur working for such objects. Think it's easier and more predictable to simply consider those settings non-animatable rather that falling into this rabbit hole. For the mesh settings i've created [D5030](https://archive.blender.org/developer/D5030).

Brecht Van Lommel commented

2019-06-06 12:38:20 +02:00

Fine with me to make these non-animatable.

blender-admin commented

2019-06-06 14:15:07 +02:00

This issue was referenced by 9e8e32e117

This issue was referenced by 9e8e32e1178983bb257bfeb79b05d0a1af07dc13

Sergey Sharybin commented

2019-06-06 14:23:09 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2019-06-06 14:23:09 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Missing Animation Update for Surface Resolution U & V #59176