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

BorderlessFullscreen, and Fullscreen { use_size: false } window modes not working #414

Closed
forbjok opened this issue Sep 1, 2020 · 5 comments
Labels
A-Windowing Platform-agnostic interface layer to run your app in C-Bug An unexpected or incorrect behavior

Comments

@forbjok
Copy link
Contributor

forbjok commented Sep 1, 2020

When supplying a WindowDescriptor resource with mode set to either BorderlessFullscreen or Fullscreen { use_size: false }, the project will still compile and run but only display a large white rectangle instead of the actual game content.

Here's a minimal reproduction project: bevy-borderless-bug-repro.zip
(using the current 0.1.3 release of bevy)

Expected output always (as shown with window mode set to Windowed):
bevy-borderless-bug-repro_CLgYREQDpl

Actual output with BorderlessFullscreen or Fullscreen { use_size: false }:
bevy-borderless-bug-repro_PmL0mZbBXA

The same result can be observed by adding a WindowDescriptor resource with either of the broken modes to the Breakout example in the current bevy master branch, so this is not specific to my test project.

@karroffel karroffel added C-Bug An unexpected or incorrect behavior A-Windowing Platform-agnostic interface layer to run your app in labels Sep 1, 2020
@scriptandcompile
Copy link

looks like #278 popping up again. Need to go through #65 and #69 discussions still.

@akien-mga
Copy link

akien-mga commented Oct 6, 2020

I think I have a similar issue by running the window_settings.rs example with bevy 0.2.1 on Linux, Plasma desktop with KWin/X11.

My screen is 4K but configured to use 1920x1080p, when I run the window_settings example (which uses Fullscreen { use_size: false }), my display goes back to 4K but the active desktop area is only the top-left quarter (1080p).
The actual Bevy window is not visible, and none of the desktop elements can be interacted with. I have to go to tty2 and then back to tty1 to fix it, which lets me kill the Bevy app and then tweak the KDE system settings to go back to properly using the full monitor size in 1080p.

Removing the custom window_mode from the example fixes the issue. I'd advise doing that in the official example until this bug is fixed.

(If this would be better suited as it's own issue, please tell me.)

@cart
Copy link
Member

cart commented Oct 6, 2020

Hmm yeah that certainly isn't ideal. I've also hit that before. I agree that removing it from the example is a good short term fix. Long term we should fix this (either in the way we interact with winit, or in winit itself)

@cart
Copy link
Member

cart commented Oct 6, 2020

The example is now "fixed" until we can sort out a real solution.

@alice-i-cecile
Copy link
Member

This seems to have been fixed; please reopen this if you can reproduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Windowing Platform-agnostic interface layer to run your app in C-Bug An unexpected or incorrect behavior
Projects
None yet
Development

No branches or pull requests

6 participants