Build (broken): 2025.33070 (Jul 16, 2026)
Last known good build: 2025.32280 (Jan 20, 2026)
OS: macOS, Apple Silicon (Apple M4)
License: Non-Commercial
slider-bug-build_33070.toe (6.7 KB)
Summary:
A Slider COMP handle only tracks the cursor while the timeline is playing. With the timeline paused or stopped, clicking the slider jumps its value to the click point, then the handle stops following the cursor for the rest of the held drag. Releasing and clicking again jumps to the new point but never tracks a continuous drag. Pressing play restores normal continuous dragging immediately. The same interaction works correctly in both play and paused states in 2025.32280. Builds between 32280 and 33070 were not tested, so the regression is somewhere in that range.
This reproduces both when interacting with the slider’s node viewer in the Network Editor and when the slider is shown in a floating Panel pane, so displaying it as a real panel does not work around it. That suggests the issue is in how panel interaction drives cooking while the timeline is paused, not something specific to the node viewer. Confirmed with a bare Slider COMP in a blank project, so it is not specific to any particular patch. A minimal repro .toe is attached.
Steps to reproduce:
- Open 2025.33070 with a new default project.
- Create a default Slider COMP and make its viewer active. Optionally also open a floating Panel pane pointed at the same slider.
- Press spacebar so the timeline is stopped and the frame counter is not advancing.
- Click and drag the slider handle across its range, in the node viewer and in the Panel pane.
Expected:
The handle follows the cursor for the full drag, the same as when the timeline is playing, in both the node viewer and the Panel pane.
Actual:
In both contexts the handle jumps to the initial click position, then freezes for the rest of the held drag. No continuous tracking returns until the timeline is playing again.
Additional notes:
- Occurs only with the timeline paused or stopped. Continuous dragging works normally while playing, in both contexts.
- Easy to miss because 2025 builds start with the timeline playing by default, so it only surfaces when a user deliberately pauses, which is common during offline editing work.