Forums
Community: Linux Support 2.0
Quick find code: 409-410-916-65990459
OSRS works fine on Linux today. Here's my notes for Jagex Launcher: https://wiki.realmofespionage.xyz/games:wine:jagex_launcher
Jagex Launcher currently at a minimum needs a 32-bit Wine prefix. Paired with those Electron flags, the launcher is a single-process 200MB RAM app that you can close as soon as you press Play (as long as OSRS/RL/RS3 window stays open, so does the log-in session).
It doesn't get easier than that
Basically it's a matter of sym-linking native Linux executable to the Windows ones Jagex Launcher launches. I never would have thought that to work so directly, but I got the tip from a Reddit thread and made some notes in my usual fashion for the set-up.
Jagex Launcher currently at a minimum needs a 32-bit Wine prefix. Paired with those Electron flags, the launcher is a single-process 200MB RAM app that you can close as soon as you press Play (as long as OSRS/RL/RS3 window stays open, so does the log-in session).
It doesn't get easier than that
Basically it's a matter of sym-linking native Linux executable to the Windows ones Jagex Launcher launches. I never would have thought that to work so directly, but I got the tip from a Reddit thread and made some notes in my usual fashion for the set-up.
11-Jul-2023 22:29:07 - Last edited on 11-Jul-2023 22:35:06 by Espionage724
I created separate notes for Jagex Launcher and OSRS by itself: https://wiki.realmofespionage.xyz/games:runescape
(can't link to the direct OSRS-specific page because forum text filters, but it's towards the top on the above page)
I like this approach much better than having all the games under the one prefix, and now I'm back to having a decent icon and desktop file
Works as-is for Fedora, and likely anywhere else with minor changes like where java is. Currently (unless the above page says different), my notes are not up-to-date for the C++ new client.
(can't link to the direct OSRS-specific page because forum text filters, but it's towards the top on the above page)
I like this approach much better than having all the games under the one prefix, and now I'm back to having a decent icon and desktop file
Works as-is for Fedora, and likely anywhere else with minor changes like where java is. Currently (unless the above page says different), my notes are not up-to-date for the C++ new client.
20-Jul-2023 04:15:38 - Last edited on 22-Jul-2023 18:01:04 by Espionage724
https://wiki.realmofespionage.xyz/games:runescape
As of July 23rd I have up-to-date notes for running the new C++ and legacy Java(?) clients through Jagex Launcher in the cleanest manner I'm aware of, and I can play from the C++ client without issue on Fedora 38.
I need 2-3 environment variables to get OSRS C++ working perfectly in Wine Staging:
PULSE_LATENCY_MSEC=400 solves audio glitching (even with Pipewire on F38)
vblank_mode=3 allows unlimited framerate option to Vsync (iirc it has to be 3 to force it instead of app-specified); very useful for screens above 60Hz, and I like it better even at 60Hz than the 60 FPS framerate cap.
MESA_LOADER_DRIVER_OVERRIDE=zink works around an odd FPS issue on Wayland on i915, but Jagex Launcher is inconsistent with functioning on Wayland. If you want to brag about running OSRS (and even RS3 NXT) with Vulkan, this is also nice for that
I'm on Fedora 38 and GNOME 44.3. I need to use the Xorg session for the best experience, and OSRS fullscreen requires this extension to fix tearing: https://extensions.gnome.org/extension/1873/disable-unredirect-fullscreen-windows/
The only thing that ideally needs looked into is the Jagex Launcher installer itself; it doesn't load anything on Wine (no obvious console error and no GUI), and I've been resorting to restoring a backup of the Jagex Launcher folder from a previous Windows install. If its ran with --window --verbose, it shows its own interesting console window, and it seems to use WebView2. Haphazardly messing with some winetricks notably dotnet48 and ie8 did cause the installer console window to show different stuff.
If a silent install flag is added to avoid needing to render the Installer at all, I believe that would be the most ideal solution; the launcher itself functions and renders fine as-is once the files are in-place, and seemingly it's just the Installer doing something not handled well.
As of July 23rd I have up-to-date notes for running the new C++ and legacy Java(?) clients through Jagex Launcher in the cleanest manner I'm aware of, and I can play from the C++ client without issue on Fedora 38.
I need 2-3 environment variables to get OSRS C++ working perfectly in Wine Staging:
PULSE_LATENCY_MSEC=400 solves audio glitching (even with Pipewire on F38)
vblank_mode=3 allows unlimited framerate option to Vsync (iirc it has to be 3 to force it instead of app-specified); very useful for screens above 60Hz, and I like it better even at 60Hz than the 60 FPS framerate cap.
MESA_LOADER_DRIVER_OVERRIDE=zink works around an odd FPS issue on Wayland on i915, but Jagex Launcher is inconsistent with functioning on Wayland. If you want to brag about running OSRS (and even RS3 NXT) with Vulkan, this is also nice for that
I'm on Fedora 38 and GNOME 44.3. I need to use the Xorg session for the best experience, and OSRS fullscreen requires this extension to fix tearing: https://extensions.gnome.org/extension/1873/disable-unredirect-fullscreen-windows/
The only thing that ideally needs looked into is the Jagex Launcher installer itself; it doesn't load anything on Wine (no obvious console error and no GUI), and I've been resorting to restoring a backup of the Jagex Launcher folder from a previous Windows install. If its ran with --window --verbose, it shows its own interesting console window, and it seems to use WebView2. Haphazardly messing with some winetricks notably dotnet48 and ie8 did cause the installer console window to show different stuff.
If a silent install flag is added to avoid needing to render the Installer at all, I believe that would be the most ideal solution; the launcher itself functions and renders fine as-is once the files are in-place, and seemingly it's just the Installer doing something not handled well.
21-Jul-2023 04:34:19 - Last edited on 26-Jul-2023 01:30:42 by Espionage724
Quick find code: 409-410-916-65990459 Back to Top