Driver's "Limit modifier" does not correspond with "Frame range" restriction
Open, ConfirmedPublic


System Information
Win7 32 bit

Blender Version
Broken: 2.78a

Exact steps for others to reproduce the error
Cube is drived by Empty with "Limit modifier". Enable "Restrict Frame Range" option and "Limit" doesn't work anymore.



Ubuntu 16.04 64bits Blender 2.78a

Here, blend file works.

Frame Range specified goes from Frame01 to Frame40. And effect of limit modifier is limited to it.
No problem if I extend frame range.

Luca Rood (LucaRood) triaged this task as Confirmed priority.Dec 10 2016, 12:55 AM

I can confirm this.

The issue is that the modifier restricts its frame range by not affecting the fcurve outside the range from start value to end value on the fcurve's X axis, which is usually time, and makes it work as expected. However, in the case of drivers, the X axis of the fcurve is not time, but rather the input value.

Any thoughts on this @Joshua Leung (aligorith)?