<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - multiple monitor fullscreen images incorrect position/scale" href="https://bugs.freedesktop.org/show_bug.cgi?id=78585#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - multiple monitor fullscreen images incorrect position/scale" href="https://bugs.freedesktop.org/show_bug.cgi?id=78585">bug 78585</a> from <a class="email" href="mailto:rqsmith@gmail.com" title="Ryan Smith <rqsmith@gmail.com>"> Ryan Smith</a> <pre>(In reply to <a href="show_bug.cgi?id=78585#c8">comment #8</a>) > Ok, so the problem here specifically is that it is not centered, right? The scale also seems off. The bottom of the image is cut off. > You are not expecting it to cover both monitors? No, I am not expecting that. If it did I would expect it to scale in a way as to not cut off part of the image. > What scale do you expect? Assuming the game is using/outputting a 720p buffer when the resolution switch is done I would expect the scale to be 2x2. A useful default behavior would to be a fixed ratio scale to fit where the image is fit to fill most of one monitor. Most games seem to be intended to run on a single monitor. If that's not possible then the best thing to do would probably be to place the image centered on one monitor with no scaling applied. > 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. Should moving the window containing the representation of the screen cause a fullscreen mode to exit with the X11 backend? I did nothing to tell the game to exit fullscreen mode. > > 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? Just running with SDL_VIDEODRIVER=wayland. xwayland was not loaded in weston.ini. It is possible this a bug with libSDL but I wasn't sure who to report it to but I thank you for taking a look at it. I am attaching the debug logs you requested.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>