Forums

Community: Linux Support 2.0 Thread is sticky

Quick find code: 409-410-916-65990459

[#ZXOK8RQIY]

[#ZXOK8RQIY]

Posts: 12 Bronze Posts by user Forum Profile RuneMetrics Profile
[#ZXOK8RQIY] said :
On a RX 580, the NXT client (flatpak) seemingly works fine, but sometimes my in-game screen while playing goes black. The game is still running though, and if I move my cursor around, game objects and things can still be interacted with, and text is still visible.

Is there something that can be tried to fix this?


This seems to be fixed by using the environment variable R600_DEBUG=nir (only applicable to AMD GPUs supporting NIR and using a open-source graphics driver)

For Flatpak:

Original message details are unavailable.
flatpak run --env='R600_DEBUG=nir' 'com.jagex.RuneScape'

09-Feb-2019 08:53:01 - Last edited on 09-Feb-2019 08:54:24 by [#ZXOK8RQIY]

[#N4GZNSR2I]

[#N4GZNSR2I]

Posts: 49 Bronze Posts by user Forum Profile RuneMetrics Profile
With NXT on Linux, I notice I'm not able to select MSAA for AA, but only FXAA. What's the requirements to be able to use MSAA?

Edit: It has to do with the Flatpak. The renderer command from the dev console from the flatpak reports Mesa 18.1.8, GL 3.0, and LLVM 6.0. I'm assuming the Flatpak is providing older libraries.

Running NXT natively reports Mesa 18.3.4, GL 4.5 (compat), and LLVM 7.0.1 (matches the versions used system-wide), and allows me to select MSAA.

I have a RX 580 and use Fedora Workstation 29.

24-Feb-2019 03:34:59 - Last edited on 24-Feb-2019 04:24:00 by [#N4GZNSR2I]

[#N4GZNSR2I]

[#N4GZNSR2I]

Posts: 49 Bronze Posts by user Forum Profile RuneMetrics Profile
Here's some assorted info:

- To be able to select the MSAA option, the OpenGL version reported to NXT seems to need to be at least 3.2 (this can be verified from the renderer command in the dev console)

- On a computer with a Intel GMA 4500MHD GPU, I needed both of these environment variables to get the game to start at all:

Original message details are unavailable.
MESA_GLSL_VERSION_OVERRIDE='130'

Original message details are unavailable.
MESA_GL_VERSION_OVERRIDE='3.0'


- To access the Developer Console when using GNOME, you need to unmap the Alt + ~ key from GNOME with the following command:

Original message details are unavailable.
gsettings set 'org.gnome.desktop.wm.keybindings' 'switch-group' "['disabled']"


- If using PulseAudio , the NXT client's volume may be lower than expected. This can be fixed by boosting the volume of the NXT client itself past 100%.

...Open the client (so that it's playing audio), and then run this command to find the Sink Input # of the NXT client (it'll be obvious with RuneScape names):

Original message details are unavailable.
pactl list sink-inputs


... and then adjust the volume of that input with this command (changing ## to the sink input number above and 130% to whatever you find ideal):

Original message details are unavailable.
pactl set-sink-input-volume '##' '130%'


- Using NIR for RadeonSI GPUs can fix random black-screen issues (I had them a lot on Burthope's agility course). It can also make initial shader compiling hitch the game hard (may vary depending on graphics software stack versions). The variable to try this is:

Original message details are unavailable.
R600_DEBUG='nir'


- Here's a non-optimal bash script to quickly get ping numbers to RS worlds:

Original message details are unavailable.
for world in {1..141};
do
res=$(ping world${world}.runescape.com -c 1 2>&0 | grep "time=" | cut -d' ' -f 8,9 | cut -d'=' -f 2) && echo World ${world}: ${res};
done


- I maintain personal wiki pages for setting up RS (main and OSRS), along with other things which can be found here:

Original message details are unavailable.
https://wiki.realmofespionage.xyz/games:runescape

25-Feb-2019 04:58:34

Decrypted
Aug Member 2016

Decrypted

Posts: 11 Bronze Posts by user Forum Profile RuneMetrics Profile
Getting this error on Linux Mint 19.1 Cinnamon

Installing: com.jagex.RuneScape/x86_64/stable from flathub
[####################] Downloading files: 29/29 3.9 MB (1.9 MB/s)
error: Failed to install com.jagex.RuneScape/x86_64/stable: Wrong size for extra data https://content.runescape.com/downloads/ubuntu/pool/non-free/r/runescape-launcher/runescape-launcher_2.2.4_amd64.deb

Any suggestions?

06-Mar-2019 11:30:11

Pinguicula

Pinguicula

Posts: 10,432 Opal Posts by user Forum Profile RuneMetrics Profile
Decrypted,

There are a few tickets about this on the Github page for this flatpak.
https://github.com/flathub/com.jagex.RuneScape/issues?q=is%3Aissue+is%3Aclosed

Looks like once in a while Jagex updates their DEB package of the NXT client resulting in the DEB package being a size that is different than expected by the flatpak so you get this error message. I think a flatpak maintainer has to manually check and update the size/hash of the DEB package for the flatpak to continue working. They don't have an open ticket about this issue right now. If someone opened a ticket about this I expect they'd fix the issue for you.

06-Mar-2019 16:56:03

Penny Drakis

Penny Drakis

Posts: 789 Gold Posts by user Forum Profile RuneMetrics Profile
Hello y'all, thanks for the flatpak, whoever created it and maintains it.

Anyhow, I am having an annoying problem with audio. The volume is fine, it's just that the audio is very choppy. It sounds very much like the effect used in the Beneath Cursed Tides .

I did try messing with /etc/pulse/daemon.conf in regards to resampling settings and it didn't seem to work but some time later, the choppiness suddenly stopped. I doubt what I did to /etc/pulse/daemon.conf actually worked, because it didn't do anything when I restarted PulseAudio and it is back to being choppy today.

EDIT : nevermind,
flatpak run --env='PULSE_LATENCY_MSEC=100' 'com.jagex.RuneScape'

works for me, I wasn't including the PULSE_LATENCY environment setting before.
Humility is self-destruction, pride is the destruction of all else. And He said, "
Let there be light.
"
And then there were none .

19-Mar-2019 03:33:02 - Last edited on 19-Mar-2019 03:38:53 by Penny Drakis

Nikki_Vista

Nikki_Vista

Posts: 3 Bronze Posts by user Forum Profile RuneMetrics Profile
Hey, Hikari, my husband's account Poncho_Vista got BANNED after following your instructions. He was just trying to help me play on chromebook and for some reason it flagged as an unappeal-able offence. I am scared to play on my Chromebook now. Any advice or help would be appreciated

20-Mar-2019 03:48:49

Quick find code: 409-410-916-65990459 Back to Top