-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Resize Output may override safe video resolutions #7754
Comments
Just going to add some context. Managing to get into this position using the UI is difficult. Small items, like 4x4 pix, will great out the button on current master. I can not manage to make a text source via the ui that is large enough to cause trouble. Pretty much the same with image, browser and image (wont let me add an image large enough). If its happening programatically via scripting, thats a different question. Not trying to dismiss the issue, just adding some information. |
Could you provide a regular working OBS log as well? The maximum texture size varies by GPU, so this may difficult for us to guard against. |
Apologies, I somehow missed the e-mail notifications for this. I'll add a log here from a clean start, additionally going through the following steps:
This, at the time of testing, sets the Base and Output resolutions to: 149349x111299
I think these are the most simple steps I get to it with my set-up (without manually adding text-content). |
Operating System Info
Other
Other OS
Gentoo Linux
OBS Studio Version
Git
OBS Studio Version (Other)
Latest Git master main etc. at this time.
OBS Studio Log URL
OBS Studio Log URL not possible since OBS Studio will not run at this point.
OBS Studio Crash Log URL
Not a crash or an URL but:
Expected Behavior
OBS Studio will at least start, ignoring the previous settings or prevent the funky resolutions to be selected in the first place.
Current Behavior
OBS Studio allows for funky resolutions and no starting again after having been closed.
Steps to Reproduce
Anything else we should know?
Noticed this while testing Pything 11 support. Going to work on fixing this soon I hope, but I also might not find the time for it so I figured I'll at least report it. ^^
The text was updated successfully, but these errors were encountered: