Seems to be working here. Maybe graphics driver I rolled back to 581 from 591 a week ago as 591 was breaking all sorts of things.

Here it goes left to right and scrolls when it hits the right side of the screen.

I'm not seeing any differences in build 356 with any previous version. It hits the right edge, the timeline scrolls to the next screen, and the cursor is on the left heading right. When it hits the right edge again, it does the same thing. The exact same way it worked in all previous versions. And I am using nVidia driver 591 as well.

I also have bug with broken playback cursor.

I have a work to do and I cannot do any editing due to this bug!

I tried to install it again, but without success.

Bug still exists.

There is no possibility to select previous version to make a downgrade so I've installed directly VEGAS_Pro_23.0.0.302_x64_DLV_DE-EN-FR-ES_250927_01-38_0D3BEAA0.exe

Reverted back to v302 and editing now works.

There is no possibility to select previous version to make a downgrade so I've installed directly VEGAS_Pro_23.0.0.302_x64_DLV_DE-EN-FR-ES_250927_01-38_0D3BEAA0.exe

Reverted back to v302 and editing now works.

 

Can you put the link in here, please.
Thank you

It's available on this forum too...

https://www.vegascreativesoftware.info/us/forum/patch-vegas-pro-23-build-302--149832/

PS. After reinstalling (even without restart PC) playback work properly and I can edit with v302.

i also have the same issue, and batch render script stopped working. geezis magix

@sean-nelson https://www.vegascreativesoftware.info/us/forum/batch-render-script-dead-after-upgrade--150476/

I tried to install it again, but without success.

Bug still exists.

@Mariusz-Litwinczuk I experienced the same playback cursor issue but it only affected a single project. Others played and edited fine. I was able to recover without reverting to b302 by copying and pasting the pieces of the problem project into a new empty one and continuing with that. Have no idea what the sticking point was. The original problem project didn't have a whole lot in it so working around the bug was not difficult once I guessed the trick.

Had the same issue and uninstalling then reinstalling v302 from the link here fixed it. Hope Magix fixes this soon!

"Everything works fine now" ... *Proceeds to go on a rant demanding money back*

Sorry, I had to giggle at that one.

Sometimes bugs slip through the cracks when releasing updates. Turning a bolt here can often break something over there, and finding every time that happens is tricky. Resolve has to deal with them sometimes too. They'll get it sorted soon.

"Everything works fine now" ... *Proceeds to go on a rant demanding money back*

Sorry, I had to giggle at that one.

Sometimes bugs slip through the cracks when releasing updates. Turning a bolt here can often break something over there, and finding every time that happens is tricky. Resolve has to deal with them sometimes too. They'll get it sorted soon.

Yes, it runs fine now, but after hours of stress, frustration, and having to roll back to an earlier version…
With every update, they fix one issue and introduce ten more—frame skipping, unresponsive pan windows, crushed blacks, and many others.
On top of that, there’s still no support for NVIDIA 422 decoding, even though every other software had it from day one of the RTX5000 series launch.
From my experience, this software should have been free, given how many problems it has.
If the next five updates are anything like this, it’s going to become completely unusable.

Thank goodness for Windows System Restore, which I run each time BEFORE I update any of my software! Yes, I, too, had the dreaded cursor freeze after updating to Build 356. I was successfully able to restore back to Build 302, which continues to work just fine, thank you! I'm on NVIDIA 581 but will try 591 to see if it works, as well. Funny how these things don't affect all of us...So now that this glitch has evidenced itself on most of our computers, would somebody please take the lead here and post when it is fixed and tested? I'm almost afraid to update VP anymore, as this is not the first time an upgrade has broken something!! THANKS, and happy editing back again with 302!

They are completely rebuilding the video engine from the ground up, that's why you're seeing new bugs pop up like this, growing pains... ironing out the kinks of a new system that replaces the dated 20+ year old system that VEGAS had been using previously. I personally am noticing big decode improvements in my 10 bit 422 AVC media in 23... to the point where as long as I'm using 2 cameras or less, I don't have to proxy on my aging system. That said, I have a 5090 in the mail (due today, actually), so I too look forward to 422 hardware decode. I'm sure they're working on it, I know they're working on this.

Same issue with the stuck playback cursor - incredible how such software-breaking bugs can slip through an update that literally takes 1 minute to find once you boot up the update... Makes me seriously reconsider moving to another editing software permanently.

For those having playback cursor issue, wonder if you do Reset Cache (Hold Ctrl+Shift while starting up VP23b356 and checkbox reset all cache), can this help makes more stable?

It's available on this forum too...

https://www.vegascreativesoftware.info/us/forum/patch-vegas-pro-23-build-302--149832/

PS. After reinstalling (even without restart PC) playback work properly and I can edit with v302.

 

Thank you! Going back to 302.

Same issue with the stuck playback cursor - incredible how such software-breaking bugs can slip through an update that literally takes 1 minute to find once you boot up the update... Makes me seriously reconsider moving to another editing software permanently.

But it's working on my PC so maybe it is working on theirs too. You do not give any info on your PC maybe there is some conflict going on. As an example NVIDIA driver 591 does weird things to my PC while version 581 is fine. You might find 591 is fine on your PC.