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
Launcher Not Working Properly: Game Window Resizing Issue #10
Comments
Lets check a few things (make sure you are using 1.0.6.0)
add the message box to print the screen width and height
Change 1920 and 1080 to your screen resolution My guess is the way i am auto detecting the screen monitor size could not always return the correct value depending on monitor layout. I will investigate this issue and see if i can find a fix |
Try this as a simple fix
With
|
I have replaced the stuff, and unticked the "Auto set game window size", but I have still the same behavior for my 1440p, but it works with 1080p. I could swear it was working last version, when I tested it for the Borderless-Guide on FAF. Changing monitor default resolution to make it work is not a suitable solution IMO. Many people using 1440p by default nowadays. Some even 4k. By my experience, your target audience are very non-tech-savvy people. In the best case, this tool should work out of the box with one or two clicks, because your average user will be overwhelmed when they have to change anything. You could even pull the default installation paths into the tool automatically for most of the game-paths, so users do not have to do it manually. It adds another layer of potential complication. |
if you re enable Auto set game window size
Does that fix the issue? "Changing monitor default resolution to make it work is not a suitable solution IMO. Many people using 1440p by default nowadays. Some even 4k." |
When attempting to start the game via FAF, the game window gets resized to a very tiny size and appears in the top left corner of the screen. I heard it from several people and can confirm it by my own testing.
The text was updated successfully, but these errors were encountered: