| blast007 | macsforme: Warzone2100 and Lugaru exhibit the same issue | 00:59 |
|---|---|---|
| blast007 | gonna test with a slightly newer SDL2 quick (2.0.10 instead of 2.0.9) | 01:02 |
| blast007 | macsforme: it's probably gonna be a "grass is greener" situation, but I wonder if we'd have less issues with GLFW ;) | 01:16 |
| blast007 | "Support for multiple windows, multiple monitors, high-DPI and gamma ramps" | 01:17 |
| blast007 | hmm.. I guess one thing it doesn't do is sound | 01:18 |
| blast007 | just windows/monitors, GL context creation/management, and input (without force/rumble feedback support) | 01:20 |
| blast007 | okay, it's differently broken with SDL 2.0.10 | 01:35 |
| blast007 | now when I start BZFlag without a config, it starts with a resolution of 3926x1440 | 01:36 |
| blast007 | spread across both screens weirdly | 01:36 |
| blast007 | but the second option is 1366x768, which does then render fullscreen on the internal display | 01:37 |
| blast007 | warzone 2100 correctly shows resolutions for both display 0 and 1 | 01:43 |
| blast007 | I kinda like the way they do it. they have the resolutions prefixed with the screen number, so for example, [0] 1366x768 or [1] 2560x1440 | 01:44 |
| blast007 | wait, scratch that, BZFlag doesn't work correctly with 2.0.10. I forgot that the debian package uses SDL 1.2, not 2.0. | 02:01 |
| *** Foo_man_choo <Foo_man_choo!~spldart@c-73-155-11-165.hsd1.tx.comcast.net> has quit IRC (Ping timeout: 250 seconds) | 02:36 | |
| *** spldart <spldart!~spldart@bzflag/contributor/spldart> has quit IRC (Ping timeout: 245 seconds) | 02:37 | |
| *** spldart <spldart!~spldart@bzflag/contributor/spldart> has joined #bzflag | 02:37 | |
| *** ChanServ sets mode: +v spldart | 02:37 | |
| *** Foo_man_choo <Foo_man_choo!~spldart@c-73-155-11-165.hsd1.tx.comcast.net> has joined #bzflag | 02:38 | |
| *** Foo_man_choo is now known as Guest94514 | 02:39 | |
| *** Zehra <Zehra!~Zehra@unaffiliated/zehra> has quit IRC (Quit: Gone for now.) | 03:20 | |
| macsforme | blast007: can you think of a workaround? and do you know if it just affects Linux only? | 03:30 |
| blast007 | it didn't happen for me with idential hardware and setup on Windows 10 | 03:50 |
| blast007 | I'll test some more tomorrow. I feel like it worked better in Warzone 2100, so I'm curious if they found a workaround. | 03:52 |
| macsforme | if there are superfluous events, I feel like that should be an easy workaround... if the window is showing up on the wrong screen, I have no idea what to do about that | 05:07 |
| blast007 | seems like it's the same upstream version of Warzone in both Debian 10 and 11, with just an extra patch to fix a segfault in 11 | 06:15 |
| *** ukiki <ukiki!ukiki@2600:3c03::f03c:91ff:fe70:30aa> has quit IRC (Ping timeout: 264 seconds) | 09:03 | |
| *** ukiki <ukiki!ukiki@2600:3c03::f03c:91ff:fe70:30aa> has joined #bzflag | 09:03 | |
| *** fanta1 <fanta1!~fanta1@p200300F76BCB2200781AEEFB48C693BE.dip0.t-ipconnect.de> has joined #bzflag | 13:12 | |
| blast007 | okay, warzone is just as broken with 2.0.10, at least using Xorg instead of Wayland. Let me compare with Wayland quick. | 16:18 |
| blast007 | ... okay, it actually behaves differently in Xorg depending on how I arrange the displays | 16:24 |
| blast007 | If I line up the top edge of the displays, it displays corrently full-screen on the internal display. If I align the bottom edge of the displays, it displays a glitchy window on the bottom left of the external display, but with the mouse aligned as if the windowsa in the top left corner | 16:25 |
| blast007 | this is fun. | 16:26 |
| *** fanta1 <fanta1!~fanta1@p200300F76BCB2200781AEEFB48C693BE.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 250 seconds) | 18:37 | |
| *** Flash <Flash!~flash@2601:280:c200:4e39:c568:b979:c93d:90c3> has joined #bzflag | 23:05 | |
| *** ChanServ sets mode: +v Flash | 23:05 | |
| *** Guest94514 is now known as Foo_man_choo | 23:27 | |
Generated by irclog2html.py 2.17.3.dev0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!