23.0 Build 356: Playback Cursor Broken

8-BitRobin wrote on 12/17/2025, 7:53 AM

Updated this morning. Playback cursor no longer scrolls with playback on timeline while playing video. Makes editing a huge pain. Problem seems to occur more frequently on larger projects. This was not a problem in the previous build, and other posts on the forum are expressing similar issues. Any help would be appreciated.

Back to post

Comments

Bofus wrote on 1/17/2026, 5:41 PM

No problems with my machine with 356

RogerS wrote on 1/17/2026, 9:55 PM

Add envelopes and try minimizing and maximizing tracks. It's a problem for all systems though you may not see it depending on your workflow.

Joaqun-Barreiro wrote on 1/18/2026, 3:38 AM

Yes, I finally reinstalled version 302. Vegas should be much faster at fixing its technical issues when they're this serious.

paul-marshall wrote on 1/19/2026, 4:25 AM

Initially I didnt have problems with 356 but when I got deeper into editing the cursor bug appeared. I'm suprised and disappointed it's taking so long to fix it.

3POINT wrote on 1/19/2026, 4:34 AM

I'm suprised and disappointed it's taking so long to fix this bug.

I can imagine that Vegas team is working overtime to eliminate the issues in build 356, but I can also imagine that they want to be sure to deliver a build that has not to be withdrawn again. Meanwhile continue editing with build 302 and see build 356 as never been released.

Sjef-Verpaalen wrote on 1/19/2026, 9:49 AM

I had the same problem with the timeline indicator that did not move while running te video. Tried everything that was recommended. No success. But then I hit touched The Vegas Hub Login and believe it or not, the problem was over.

J-Toresen wrote on 1/20/2026, 9:17 AM

@Sjef-Verpaalen wrote:

I had the same problem with the timeline indicator that did not move while running te video. Tried everything that was recommended. No success. But then I hit touched The Vegas Hub Login and believe it or not, the problem was over.

This may be an important finding. I think you, or others (administrators of the forum?), should try to report your finding to VEGASDerek or other developers.

Jøran