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

4.2 dev5 - Borderless fullscreen window size is incorrect #82156

Closed
dogboydog opened this issue Sep 22, 2023 · 2 comments
Closed

4.2 dev5 - Borderless fullscreen window size is incorrect #82156

dogboydog opened this issue Sep 22, 2023 · 2 comments
Labels

Comments

@dogboydog
Copy link
Contributor

dogboydog commented Sep 22, 2023

Godot version

v4.2.dev5.mono.official [e3e2528]

System information

Windows 10, Nvidia RTX 3090

Issue description

I discovered this when testing the new integer scaling option in Project Settings.

image

The DisplayServer is reporting a window size that is not the same as the screen size in full screen mode. I wrote a MRP with a script which prints the screen vs window size.

The output for me is this:

Screen(1920, 1080)
Window: (1918, 1078)

The window is 2 pixels smaller in both dimensions than the screen size, which means even though the the screen size is divisible by the viewport size, integer scaling leaves black bars around the viewport. Is this a settings problem I have in my project and the repro or a bug? Maybe I'm misunderstanding something.

I get the same behavior on my Windows 11 laptop as well.

Thank you

Steps to reproduce

Run the attached project and observe console output / game appearance

Minimal reproduction project

windowsize_fullscreen.zip

@dogboydog dogboydog changed the title Borderless fullscreen window size is incorrect 4.2 dev5 - Borderless fullscreen window size is incorrect Sep 22, 2023
@bitsawer
Copy link
Member

Thanks for the report. Duplicate of #63500, see #63500 (comment) for more information.

If you are not planning on creating multiple windows, you should probably just use "Exclusive Fullscreen" mode.

@bitsawer bitsawer closed this as not planned Won't fix, can't repro, duplicate, stale Sep 22, 2023
@dogboydog
Copy link
Contributor Author

I see. Thank you

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

No branches or pull requests

2 participants