Cycled animation in NLA randomly sets animated property to incorrect value on certain frames #119360

New Issue

Albert-OShea · 2024-03-12T05:14:50+01:00

Albert-OShea commented

2024-03-12 05:14:50 +01:00

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.23

Blender Version
Broken: version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-03-05 20:16, hash: 49c723e1176a
Also broken in 4.0.2

Short description of error
The set-up:

I have a material that is reading a custom property via an Attribute node. The attribute controls the emission level of the material.
The custom property is being animated by a simple 'pulsing' action which has a Cycles modifier on the f-curve, allowing for a continuous pulse.
The action has been pushed down to the NLA and the strip has been extended by setting the frame End to 593.

Exact steps for others to reproduce the error

Open attached blend file and play the animation, watch for 1-frame flashes at these frame numbers: 339, 352, 443, 456.
At these frames, the animated custom property 'pulse' gets set to either the lowest value in the curve (0.123) or the highest value (1) at the wrong time.
Demonstration of the flashing shown in attached video.

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.23 **Blender Version** Broken: version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-03-05 20:16, hash: `49c723e1176a` Also broken in 4.0.2 **Short description of error** The set-up: - I have a material that is reading a custom property via an Attribute node. The attribute controls the emission level of the material. - The custom property is being animated by a simple 'pulsing' action which has a Cycles modifier on the f-curve, allowing for a continuous pulse. - The action has been pushed down to the NLA and the strip has been extended by setting the frame End to 593. **Exact steps for others to reproduce the error** 1. Open attached blend file and play the animation, watch for 1-frame flashes at these frame numbers: 339, 352, 443, 456. 2. At these frames, the animated custom property 'pulse' gets set to either the lowest value in the curve (0.123) or the highest value (1) at the wrong time. Demonstration of the flashing shown in attached video.

nla-wrong-value-frames.blend

820 KiB

Recording 2024-03-12 152255.mp4

548 KiB

👀 1

Albert-OShea added the