While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
-
Zink driver startup time squashed with new patches
- ShabbyX -
VR game Alien: Rogue Incursion releases late 2024
- doragasu -
Albion Online now officially launched in Europe and MEN…
- minidou -
The big hit medieval strategy game Manor Lords works we…
- TimeFreeze -
Zink driver startup time squashed with new patches
- based - > See more comments
Latest Forum Posts
- Weekend Players' Club 4/26/2024
- Mezron - Penguins in Gaming
- StoneColdSpider - Nintendo-style gaming, without Nintendo!
- Pengling - Free Steam Keys!
- robvv - Company of Heroes 2 Benchmark
- Vortex_Acherontic - See more posts
View PC info
https://steamcommunity.com/app/342560/discussions/0/1737715419910115747/
Not sure if it parses the output of the actual xrandr command. If so it might be possible to create a dummy xrandr that runs under Wayland and gives the appropriate output?
I don't have the game and there doesn't seem to be a demo available so I can't be of much help...
https://github.com/LWJGL/lwjgl/issues/118
and the workaround I described seems to work:
https://bugzilla.redhat.com/show_bug.cgi?id=1236389#c5
(Really crappy behavior from lwjgl!)
View PC info