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
[Error]: The setting name "Screen resolution" is misleading #9734
Comments
Question: is this feature needed at all? The only use I see for it is to take screenshots of a certain resolution, but that's a bit of a weak motivation. I don't see any other reason. If someone wants to play on a smaller window, they can minimize it and choose any size. |
If you enable "full screen" it will actually change the screen resolution (at least on Windows). |
we could instead disable the setting if anything other than "full screen" is used |
I never used full screen mode and didn't think it actually worked. Man learns all his life :D
I think that would be appropriate. But the question is, could this resolution change work also for a windowed game? Then choosing the resolution 1/2, 1/3, 1/4 should give a very good effect without blurring for screens with high resolutions. |
there's a gui zoom setting for that |
I like that solution. |
Or it could be renamed to "Window size" if it's not full screen? I at least still like to pick a resolution even though I use OpenTTD in a window, rather than dragging the window to an arbitrary size. |
Fair enough, that is enough to leave it in. What to name it really becomes bikeshedding .. what-ever you do, someone will complaint. So I suggest to just leave it as it is .. |
Version of OpenTTD
12.1 and earlier, possibly from 0.6.0-beta1 (r10704)
Expected result
This setting changes the window size, not the screen resolution, so it should be called "Screen / Window size" or "Gameplay screen / window size".
Actual result
The title of the option "Screen resolution" suggests that it changes the screen resolution, which is not true. This is confusing and misleading as to the actual function of the setting. Report #9717 is one confirmation of this issue. I also thought that was the way it worked.
Steps to reproduce
n/a
The text was updated successfully, but these errors were encountered: