Let's see...

- All my screens are at the same KDE-set scale, but they're all 125%, not 100%.
- I noticed this time that the menu bar on the leftmost monitor is also jittering up and down, though my guess is this is because a fullscreen window is jittering between monitors.
- Here's an event log ...

Console output. I've changed no settings from the default besides 'preferred video driver'.

Though I doubt this is relevant, the game still has the long-standing bug that it shows the primary display as display #3 (but starts up on #1 by default anyway?), while actually the KDE desktop setting is ...

I think this might only be an issue on Wayland. (However, the game is incredibly laggy (and blurry) on X11.)

Hi,

I'm having some trouble with my purchase.

I logged in to the website, went to the download page, and clicked 'buy' for Space age. This redirected me to Stripe, where I paid for a copy, but it ended up on an error page complaining about a missing zip code on my card.

I tried again. This time I ...

Factorio reliably starts up on the left-most display on my setup, by default. When I try to move it to screen 2 (i.e. the central, primary display)...

This happens: https://brage.info/75122881937__C9B04B3E-381C-4B0B-A05A-779CBB3A04DD.mov

The monitor change does actually take effect correctly, upon ...

This should be the one: https://brage.info/factorio-hdr-weirdness.log

I don't see anything unusual. The pixel format is still RGB888, so I would be suspicious of the compositor more than anything else. Though I don't think that could cause the weird shoreline rendering.

Well, it's marked as an experimental feature and the checkbutton literally landed yesterday, but I thought I'd mention anyway.

If you enable HDR in KDE6, as such:
https://usercontent.irccloud-cdn.com/file/AVuECqFo/image.png

Then the rendering of Factorio breaks fairly badly: https://usercontent ...

That is somewhat relieving.

O-kay...

I haven't yet played a full game with this, doing that this Friday, but I trust your integration tests. And/or the possibility that you don't mean "set *(unsigned int*)Wayland_ShowCursor = 0xc3c03148".

Ah, I see.

There's a lot of bugfixes to the code in question in 2.30.1, so you might want to consider that. I'll admit my setup is a bit rare at the moment, but it won't be staying that way; part of what I'm doing is searching for problems that can be fixed on the distro level. Though unfortunately ...

I was able to do that regardless. It's a little bit of a hack, but I suppose this is fine; I don't see any difference in game behavior from what's expected.

Pretty simple, just do this:


gdb ./bin/x64/factorio --write
# wayland_get_system_cursor does not exist.
# It is presumably inlined ...

Setting an XCURSOR_THEME does not appear to solve the problem.


svein@saya ~/factorio [1]> echo $XCURSOR_PATH
/nix/store/7brazl8m0rhc8yacpw98flwaxs5g12qz-plasma-workspace-6.0.0/share/icons /home/svein/.icons /home/svein/.local/share/icons /home/svein/.local/share/flatpak/exports/share/icons /home ...

NixOS, Plasma 6. Though as I said, this might be fixed upstream; it appears similar to https://bugzilla.redhat.com/show_bug.cgi?id=2165386, which isn't GPU-related.

I'd love to test a newer SDL version for you, except... I wound up rebuilding my OS with a newer SDL, then realised it's statically ...

I spot a lot of changes to that particular function, some in reference to crashes.

Factorio appears to have SDL linked statically, so I can't test it, but I suspect that updating to the newest SDL2 release might do it.

This is with SDL_VIDEODRIVER=wayland. Note that Factorio is unplayable without this set; the window blinks white several times per second during normal gameplay.

No mods are loaded. It reliably happens while scrolling the mod menu; I haven't gotten far enough to try gameplay.


svein@saya ...

Considering that it's a modded game, it's likely that you're running flib . If you are running it (it shows up as "Factorio library" in-game), try updating it to the latest version if it's not already updated. The library had a bug with translations that had almost exactly these symptoms, but was ...

> This may be a buffer bloat problem as once both the client and server have timed out, the host can still receive UDP packets 5-10 seconds later.

This is actually the client.

Definitely not a fan of the new icons. They're fine on the ground, but as an icon in my inventory they're frankly ugly.

If this is the changelog for .29, what's the one for .30?

It runs fine, and in headless mode actually about 20% faster than on my 1920X (impressive!).

But. This is a huge but. Using --benchmark on the same save and mod config, on both machines, I get a different checksum on the M1.

Connecting to a multiplayer sessions seems to have worked, however, so I ...