Can't move canvas around with spacebar after update to 29.1

jdj9x

New Member
Hey friends. I have just updated to ver. 29.1 and i can no longer move the canvas around with the spacebar. I can zoom in/out using the spacebar, but not move the canvas in a different position. "Lock Preview" is disabled. Any ideas?

Thanks.
 

jdj9x

New Member
I have updated OBS to 29.1 on another system and it is the same. i cannot move around the preview with spacebar. Can someone help please?
 

jdj9x

New Member
How is that supposed to work in the first place? The spacebar is just a button, down or up, and moving the canvas is at least a 2-dimensional proportional thing.

Before the update, you could move the canvas in any position you wanted on the screen, by holding spacebar + mouse and also zoom in/out. Now after the update, i cannot move it. it stays in the centre. i can only zoom/in out.
 

Suslik V

Active Member
I cannot reproduce the issue. But... now the panning only possible after the zoom in. Previously it was possible after zoom out too. Of course, the Preview Scaling needs to be set to Output or to Canvas. Or maybe I miss something.
 

DonjaZero

New Member
I cannot reproduce the issue. But... now the panning only possible after the zoom in. Previously it was possible after zoom out too. Of course, the Preview Scaling needs to be set to Output or to Canvas. Or maybe I miss something.

This is what I'm seeing, too, with 29.1.1 (64-bit) for Windows.

SPACE+MWHEELUP to zoom in, then left click while still holding SPACE to reposition. I cannot reposition after zooming out (SPACE+MWHEEDOWN), which makes this very tricky to get right.

I'm not 100% certain what the behavior used to be, as I'm new to OBS Studio, but it appears to have been possible to zoom out and then reposition at some point in the past (based on old video I found). If that's true, this seems like a regression.
 

Geelint

New Member
I'm in the process of finally upgrading to 29+ and can very much say I miss how this used to work
Here is an exact video example of what I'm assuming is being talked about here and would ask if this change could be reverted/bug fixed
 
Top