| 00:59.29 | blast007 | macsforme: Warzone2100 and Lugaru exhibit the same issue |
| 01:02.57 | blast007 | gonna test with a slightly newer SDL2 quick (2.0.10 instead of 2.0.9) |
| 01:16.35 | blast007 | macsforme: it's probably gonna be a "grass is greener" situation, but I wonder if we'd have less issues with GLFW ;) |
| 01:17.47 | blast007 | "Support for multiple windows, multiple monitors, high-DPI and gamma ramps" |
| 01:18.50 | blast007 | hmm.. I guess one thing it doesn't do is sound |
| 01:20.02 | blast007 | just windows/monitors, GL context creation/management, and input (without force/rumble feedback support) |
| 01:35.32 | blast007 | okay, it's differently broken with SDL 2.0.10 |
| 01:36.13 | blast007 | now when I start BZFlag without a config, it starts with a resolution of 3926x1440 |
| 01:36.35 | blast007 | spread across both screens weirdly |
| 01:37.16 | blast007 | but the second option is 1366x768, which does then render fullscreen on the internal display |
| 01:43.57 | blast007 | warzone 2100 correctly shows resolutions for both display 0 and 1 |
| 01:44.57 | 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 |
| 02:01.09 | 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:37.55 | *** join/#bzflag spldart (~spldart@bzflag/contributor/spldart) |
| 02:37.55 | *** mode/#bzflag [+v spldart] by ChanServ |
| 02:38.51 | *** join/#bzflag Foo_man_choo (~spldart@c-73-155-11-165.hsd1.tx.comcast.net) |
| 03:30.48 | macsforme | blast007: can you think of a workaround? and do you know if it just affects Linux only? |
| 03:50.54 | blast007 | it didn't happen for me with idential hardware and setup on Windows 10 |
| 03:52.12 | 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. |
| 05:07.43 | 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 |
| 06:15.22 | 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 |
| 09:03.57 | *** join/#bzflag ukiki (ukiki@2600:3c03::f03c:91ff:fe70:30aa) |
| 13:12.00 | *** join/#bzflag fanta1 (~fanta1@p200300F76BCB2200781AEEFB48C693BE.dip0.t-ipconnect.de) |
| 16:18.51 | 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:24.21 | blast007 | ... okay, it actually behaves differently in Xorg depending on how I arrange the displays |
| 16:25.59 | 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:26.04 | blast007 | this is fun. |
| 23:05.25 | *** join/#bzflag Flash (~flash@2601:280:c200:4e39:c568:b979:c93d:90c3) |
| 23:05.25 | *** mode/#bzflag [+v Flash] by ChanServ |