https://bugs.freedesktop.org/show_bug.cgi?id=78585
--- Comment #8 from Pekka Paalanen <[email protected]> --- (In reply to comment #0) > I observed this behavior on the trunk version of weston (pre 1.5 release) > using the game SuperMeatBoy with both libSDL 2.0.2 and libSDL2 trunk. I was > able to duplicate this on the r600 driver with the drm backend and the X11 > backend. I only saw this behavior with two monitors. > > The game goes into fullscreen mode after launching and appears to run at my > native resolution of 1080p on the first monitor. I reconfigure the game for > 720p without exiting and the image shrinks down to the appropriate 1:1 size > on the first monitor with black borders around it. It does not appear > centered. Ok, so the problem here specifically is that it is not centered, right? You are not expecting it to cover both monitors? What scale do you expect? On Wayland, configuring resolution in the game will not work as you might usually expect. It becomes a hint to the compositor, and depending on the fullscreening style used, it may have various effects, including black borders and/or scaling. Normally the preferred style would be set in the compositor preferences, unless the application asks for a specific thing, but even then it is only a hint. Therefore it would be good to hear what exactly you expect to happen here. > When the game is exited with this new settings and re-opened the game again > goes fullscreen but now the image is scale up with the black borders around > it again and it spans across to the other monitor. On the X11 backend after > I move the weston compositor window the application shrinks down but the > weston menu bar at the top of the screen is then visible. The image is > still off center. On the drm backend the image continues displayed at the > wrong scale/position until the game is exited. The panel becomes visible, when the fullscreen window is no longer active. That is expected. Activating the fullscreen window again should make the panel go away. The other stuff however is unexpected. I suspect this might be partly a problem in SDL2. We'd have to see a Wayland protocol dump from the game. It goes to stderr, when you set the environment variable WAYLAND_DEBUG=client (only for the game, not weston). That dump will probably be quite long, so it will need someone to sit down and look at it for a while. There is no Xwayland involved, right? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
