Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OBS uses Scaling set by the primary monitor but not the monitor that it is in #11858

Open
MeekGroundhog21 opened this issue Feb 13, 2025 · 0 comments

Comments

@MeekGroundhog21
Copy link

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

31.0.1

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/8TcOxfCc1aBtOfJZ

OBS Studio Crash Log URL

No response

Expected Behavior

  1. When primary monitor scaling is set to 100% and secondary is set to 150%, obs scaling should be set to 150% when on a secondary monitor
  2. When primary monitor scaling is set to 150% and secondary is set to 100%, obs scaling should be set to 100% when on a secondary monitor

Current Behavior

  1. When primary monitor scaling is set to 100% and secondary is set to 150%, obs scaling is set to 100% when on a secondary monitor

Image
Image

  1. When primary monitor scaling is set to 150% and secondary is set to 100%, obs scaling is set to 150% when on a secondary monitor

Image
Image

Steps to Reproduce

When primary monitor scaling is set to 100% and secondary is set to 150%, obs scaling is set to 100% when on a secondary monitor

  1. Right Click on Desktop and open Display settings
  2. Set the primary monitor Scale to 100%
  3. Set the secondary monitor Scale to 150%
  4. Open OBS and drag it to a secondary monitor

When primary monitor scaling is set to 150% and secondary is set to 100%, obs scaling is set to 150% when on a secondary monitor

  1. Right Click on Desktop and open Display settings
  2. Set the primary monitor Scale to 150%
  3. Set the secondary monitor Scale to 100%
  4. Open OBS and drag it to a secondary monitor

Anything else we should know?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant