Old School RuneScape C++ Client Install on Linux (Aug 2023)

Updated video (Feb 2024):    • Old School RuneScape C++ Install on L...  

https://wiki.realmofespionage.xyz/gam...

No Steam, no GE-Proton, no Flatpak, no Lutris. OSRS with the C++ client as-minimal as it can get on Linux with only wine (Staging), as integrated as possible, in-reproducible form! I also have notes here for native Linux OSRS RuneLite and RS3 NXT clients: https://wiki.realmofespionage.xyz/gam...

There's a particularly overkill script that uses Flatpak, Lutris, and GE-Proton, which I feel adds a ton more points of failure and security risks for seemingly no gain (people wonder why Jagex Accounts are being enforced). You guys are adding more dependencies and pulling in random assets online than OSRS uses in filesize with a complete cache :p

Jagex Launcher is a bit inconsistent with appearing on Wayland, but seemed fine from Xorg. Click-fighting it a little bit (and maybe restarting it) and pressing Play is all that's needed and it can be closed immediately afterwards.

If the game window is all black, go to Settings and change the scaling from Bicubic. I'm guessing it's an oddity somewhere with that, Intel, and zink, but Nearest Neighbor is best any way.

It's important to set an ideal framerate cap, and seemingly to not use a framerate cap in-game (set it Unlimited, unless you want 60 or lower caps). After fighting with vblank_mode=3, tearing, and other conditions between X and Wayland, I found that all tearing is gone without vsync on Wayland, and that setting a framerate cap near my screen's refresh rate (74Hz, so 75) works good enough to also not cause needless power load.

OSRS with the new C++ client works perfectly (silver) on Linux in July (and likely August) 2023!

If my notes don't work in some manner or if something can be improved let me know. I only assume Linux conditions close to what Fedora Linux uses (38 at the time), including GNOME and heavy bash usage.

Backup notes URL: https://web.archive.org/web/https://w...