Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[shyney]

got a new mesa update today see screenshot .
@lepwn @serioustable @ragingATyou @shenrougu
can someone try if it works with the new mesa version

I have this version installed (21.3. and it sadly doesn't work. Though it is to be expected since the bug was apparently fixed during the end of last year (https://gitlab.freedesktop.org/mesa/mesa/-/issues/5754) so we'd need like the 21.10 or 21.12 vesion

This is weird because as it seems this issue was fixed with the mesa version 21.3.4 as it is written on the release notes here: https://docs.mesa3d.org/relnotes/21.3.4.html
As you can see from my screenshot the last update that my steamdeck made with the discover app was to update to mesa version 21.3.8 so it is even some versions above the bugfix release that should have fixed it!? The version 21.3.8 is also the latest release for the 21 version of mesa it was released on 2022-03-18 as you can see here : https://docs.mesa3d.org/relnotes/21.3.8.html . Did you opened the discover app and checked for updates before testing it?

[GeometryPrime]

got a new mesa update today see screenshot .
@lepwn @serioustable @ragingATyou @shenrougu
can someone try if it works with the new mesa version

I have this version installed (21.3. and it sadly doesn't work. Though it is to be expected since the bug was apparently fixed during the end of last year (https://gitlab.freedesktop.org/mesa/mesa/-/issues/5754) so we'd need like the 21.10 or 21.12 vesion

This is weird because as it seems this issue was fixed with the mesa version 21.3.4 as it is written on the release notes here: https://docs.mesa3d.org/relnotes/21.3.4.html
As you can see from my screenshot the last update that my steamdeck made with the discover app was to update to mesa version 21.3.8 so it is even some versions above the bugfix release that should have fixed it!? The version 21.3.8 is also the latest release for the 21 version of mesa it was released on 2022-03-18 as you can see here : https://docs.mesa3d.org/relnotes/21.3.8.html . Did you opened the discover app and checked for updates before testing it?

I've just gone and done exactly that - pulled up Discover, updated everything, and also updated the Steam Deck through its own updater in gaming mode, so it's all as new as it can be. Still happens, sadly.

[shyney]

got a new mesa update today see screenshot .
@lepwn @serioustable @ragingATyou @shenrougu
can someone try if it works with the new mesa version

I have this version installed (21.3. and it sadly doesn't work. Though it is to be expected since the bug was apparently fixed during the end of last year (https://gitlab.freedesktop.org/mesa/mesa/-/issues/5754) so we'd need like the 21.10 or 21.12 vesion

This is weird because as it seems this issue was fixed with the mesa version 21.3.4 as it is written on the release notes here: https://docs.mesa3d.org/relnotes/21.3.4.html
As you can see from my screenshot the last update that my steamdeck made with the discover app was to update to mesa version 21.3.8 so it is even some versions above the bugfix release that should have fixed it!? The version 21.3.8 is also the latest release for the 21 version of mesa it was released on 2022-03-18 as you can see here : https://docs.mesa3d.org/relnotes/21.3.8.html . Did you opened the discover app and checked for updates before testing it?

I've just gone and done exactly that - pulled up Discover, updated everything, and also updated the Steam Deck through its own updater in gaming mode, so it's all as new as it can be. Still happens, sadly.

Can you open up the discover app -> installed apps and confirm it is running mesa version 21.3.8?

[shyney]

Hi - yep, just confirming that this looks like a crash in the driver.

got a new mesa update today see screenshot .
@lepwn @serioustable @ragingATyou @shenrougu
can someone try if it works with the new mesa version

I have this version installed (21.3. and it sadly doesn't work. Though it is to be expected since the bug was apparently fixed during the end of last year (https://gitlab.freedesktop.org/mesa/mesa/-/issues/5754) so we'd need like the 21.10 or 21.12 vesion

This is weird because as it seems this issue was fixed with the mesa version 21.3.4 as it is written on the release notes here: https://docs.mesa3d.org/relnotes/21.3.4.html
As you can see from my screenshot the last update that my steamdeck made with the discover app was to update to mesa version 21.3.8 so it is even some versions above the bugfix release that should have fixed it!? The version 21.3.8 is also the latest release for the 21 version of mesa it was released on 2022-03-18 as you can see here : https://docs.mesa3d.org/relnotes/21.3.8.html . Did you opened the discover app and checked for updates before testing it?

I've just gone and done exactly that - pulled up Discover, updated everything, and also updated the Steam Deck through its own updater in gaming mode, so it's all as new as it can be. Still happens, sadly.

Ok forget what I said the 21.3.8 version is just the flatpak version inside the desktop mode. I think its just beeing used for flatpak apps? But if you go to game mode you can see under Settings -> System -> Video Driver that the current stable release of SteamOS is using the latest branch version 22.0.0 from 2022-03-09 (https://docs.mesa3d.org/relnotes/22.0.0.html).

This Version also contains the bugfix for starsector as you can see from the release notes.

 So on both sides flatpak and OS-side are using a version that already includes the commit that fixes starsector to crash. So this crash is probably not because of mesa?

[lepwn]

Any news on the issue ? 
It would seem that the drivers are not to blame,after all.
Valve gave me no further information in my support discussion with them.
It's really sad that this game can't be played because of such a simple looking bug.

[Alex]

Ah - the error log makes it clear that the crash is in the graphics driver. Unfortunately it looks like the driver fix that was supposed to resolve this - and maybe actually did on other hardware? I just don't know - didn't work on the steam deck.

[cmdr_rockman]

I've been able to reliably repro this crash by starting a new game with the explorer start. 100% of the time a crash occurs in the first tutorial battle the moment a missile hits the pirate ship.

Only settings I changed were to disable static and whiteout in settings.json.

I could make a video if that would help!

@Alex would updating native/linux/liblwjgl64.so to the latest LWJGL release be possible? https://github.com/LWJGL/lwjgl3/releases It might give us better error logging.

I tried setting

Code

-Dorg.lwjgl.util.Debug=true

but get a error in a popup window before the launcher appears on startup:

Code

Fatal: Stack underflow (1284)

. Here's the terminal output for that:

Code

./starsector.sh
0    [main] INFO  com.fs.starfarer.StarfarerLauncher  - Starting Starsector 0.95.1a-RC6 launcher
2    [main] INFO  com.fs.starfarer.StarfarerLauncher  - Running in /home/deck/starsector-linux
2    [main] INFO  com.fs.starfarer.StarfarerLauncher  - OS: Linux 5.13.0-valve15-1-neptune-02197-gf6ec7ad3762a
2    [main] INFO  com.fs.starfarer.StarfarerLauncher  - Java version: 1.7.0_79 (64-bit)
14   [main] INFO  com.fs.starfarer.settings.StarfarerSettings  - Loading settings
19   [main] INFO  com.fs.starfarer.loading.LoadingUtils  - Loading JSON from [ABSOLUTE_AND_CWD: null (data/config/settings.json)]
148  [main] INFO  com.fs.starfarer.launcher.opengl.GLLauncher  - Assuming native monitor resolution is 0x0
[LWJGL] Xrandr extension version 1.6
[LWJGL] Using Xrandr for display mode switching
[LWJGL] XF86VidMode extension version 2.2
[LWJGL] Initial mode: 800 x 1280 x 24 @60Hz
307  [Thread-2] INFO  com.fs.graphics.K  - Using refresh rate:60
Sorted display modes:
597 x 373 x 0 @0Hz
Attempting to set displaymode: 597 x 373 x 0 @0Hz
[LWJGL] Pixel format info: r = 8, g = 8, b = 8, a = 8, depth = 24, stencil = 8, sample buffers = 0, samples = 0
[LWJGL] MemoryUtil Accessor: AccessorUnsafe
542  [Thread-2] INFO  com.fs.starfarer.launcher.opengl.GLLauncher  - Maximum anti-aliasing samples: 8
556  [Thread-2] FATAL com.fs.starfarer.launcher.opengl.GLLauncher  - org.lwjgl.opengl.OpenGLException: Stack underflow (1284)
org.lwjgl.opengl.OpenGLException: Stack underflow (1284)
        at org.lwjgl.opengl.Util.checkGLError(Util.java:59)
        at org.lwjgl.opengl.DrawableGL.checkGLError(DrawableGL.java:82)
        at org.lwjgl.opengl.Display.swapBuffers(Display.java:617)
        at org.lwjgl.opengl.Display.update(Display.java:646)
        at com.fs.starfarer.launcher.opengl.GLLauncher.prepare(Unknown Source)
        at com.fs.starfarer.BaseGameState.traverse(Unknown Source)
        at com.fs.starfarer.launcher.opengl.GLLauncher$2.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[LWJGL] XF86VidMode extension version 2.2

[attachment deleted by admin]

[cmdr_rockman]

Is it possible to disable missile or weapon explosion effects? I'm just guessing that may be causing the crash.

[Alex]

@Alex would updating native/linux/liblwjgl64.so to the latest LWJGL release be possible?

I don't think so, LWJGL 3+ isn't backwards-compatible with LWJGL 2.

Is it possible to disable missile or weapon explosion effects? I'm just guessing that may be causing the crash.

It's not, but it seems unlikely that this would help. Whatever is causing the crash is likely just the *first* thing that's causing the crash; it'd probably just be something else if it got past the initial thing. It's not doing anything particularly fancy for those, anyway...

[cmdr_rockman]

Thanks for the details Alex!

I spent quite a long time trying different options from https://docs.mesa3d.org/envvars.html seeing if I could prevent the crash. Particularly these options:

Code

MESA_EXTENSION_MAX_YEAR
MESA_GL_VERSION_OVERRIDE
MESA_GLSL_VERSION_OVERRIDE
AMD_DEBUG

Nothing I tried helped but I didn't have a particular strategy in mind.

In case anyone wants to try Here's my starsector.sh launch script:

Code

#!/usr/bin/env bash

export LIBGL_DEBUG=1
export MESA_DEBUG=flush
export MESA_EXTENSION_MAX_YEAR=2013

# export MESA_GL_VERSION_OVERRIDE=3.3
# export MESA_GL_VERSION_OVERRIDE=2.1
# export MESA_GLSL_VERSION_OVERRIDE=330
# glxinfo
# exit 0

export MESA_EXTENSION_OVERRIDE="-GL_AMD_framebuffer_multisample_advanced -GL_ARB_bindless_texture -GL_ARB_color_buffer_float -GL_ARB_sparse_buffer -GL_ATI_meminfo -GL_ATI_texture_mirror_once -GL_EXT_depth_bounds_test -GL_EXT_shader_image_load_formatted -GL_EXT_shader_image_load_store -GL_EXT_texture_mirror_clamp -GL_NVX_gpu_memory_info -GL_NV_alpha_to_coverage_dither_control -GL_NV_shader_atomic_int64 -GL_NV_vdpau_interop -GL_EXT_window_rectangles"

export AMD_DEBUG=info,mono,ps,vs
# export AMD_DEBUG=mono

# radeonsi_dri.so locations:
# Find existing files with: find / -iname "*radeonsi*dri*.so" 2>/dev/null

# /usr/lib/dri/radeonsi_dri.so
# /usr/lib32/dri/radeonsi_dri.so

# Untested:

# /home/.steamos/offload/var/lib/flatpak/runtime/org.freedesktop.Platform.GL32.default/x86_64/21.08/6b4c056fca05e4ffa9ed980eab780e8f35440cdec9d41b36f29ac1619faf8f74/files/lib/dri/
# /home/.steamos/offload/var/lib/flatpak/runtime/org.freedesktop.Platform.GL.default/x86_64/21.08/c8f81b502d8a867a532896330988485f68e94a2cbb4c26ae98b1b2811b566f7e/files/lib/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/var/tmp-MLV8N1/usr/lib/i386-linux-gnu/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/var/tmp-MLV8N1/usr/lib/x86_64-linux-gnu/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/var/tmp-MLV8N1/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/var/tmp-MLV8N1/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-96UMO1/usr/lib/i386-linux-gnu/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-96UMO1/usr/lib/x86_64-linux-gnu/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-96UMO1/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/dri/
# /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-96UMO1/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/
# /var/lib/flatpak/runtime/org.freedesktop.Platform.GL32.default/x86_64/21.08/6b4c056fca05e4ffa9ed980eab780e8f35440cdec9d41b36f29ac1619faf8f74/files/lib/dri/
# /var/lib/flatpak/runtime/org.freedesktop.Platform.GL.default/x86_64/21.08/c8f81b502d8a867a532896330988485f68e94a2cbb4c26ae98b1b2811b566f7e/files/lib/dri/

# Override with:
# export LD_LIBRARY_PATH=/var/lib/flatpak/runtime/org.freedesktop.Platform.GL.default/x86_64/21.08/c8f81b502d8a867a532896330988485f68e94a2cbb4c26ae98b1b2811b566f7e/files/lib/dri/

cd ~/starsector-linux/
./jre_linux/bin/java \
 -server \
 -XX:CompilerThreadPriority=1 \
 -XX:+CompilerThreadHintNoPreempt \
 -Djava.library.path=./native/linux \
 -Xms1536m \
 -Xmx1536m \
 -Xss2048k \
 -classpath janino.jar:commons-compiler.jar:commons-compiler-jdk.jar:starfarer.api.jar:starfarer_obf.jar:jogg-0.0.7.jar:jorbis-0.0.15.jar:json.jar:lwjgl.jar:jinput.jar:log4j-1.2.9.jar:lwjgl_util.jar:fs.sound_obf.jar:fs.common_obf.jar:xstream-1.4.10.jar \
 -Dorg.lwjgl.util.Debug=false \
 -Dorg.lwjgl.util.NoChecks=false \
 -Dcom.fs.starfarer.settings.paths.saves=./saves \
 -Dcom.fs.starfarer.settings.paths.screenshots=./screenshots \
 -Dcom.fs.starfarer.settings.paths.mods=./mods \
 -Dcom.fs.starfarer.settings.paths.logs=. \
 -Dcom.fs.starfarer.settings.linux=true com.fs.starfarer.StarfarerLauncher

There is a bunch of overrides for different games on the steamdeck defined in /usr/share/drirc.d/00-mesa-defaults.conf
which is what gave me this idea to begin with. Things like this:

Code

        <application name="Rust" executable="rust">
            <option name="glsl_zero_init" value="true"/>
        </application>

        <application name="Divinity: Original Sin Enhanced Edition" executable="EoCApp">
            <option name="allow_glsl_extension_directive_midshader" value="true" />
            <option name="glsl_correct_derivatives_after_discard" value="true" />
            <option name="force_gl_vendor" value="ATI Technologies, Inc."/>
        </application>

        <application name="Metro 2033 Redux / Metro Last Night Redux" executable="metro">
            <option name="allow_glsl_extension_directive_midshader" value="true" />
        </application>

        <application name="Kerbal Space Program (32-bit)" executable="KSP.x86">
            <option name="glsl_zero_init" value="true"/>
        </application>

        <application name="Kerbal Space Program (64-bit)" executable="KSP.x86_64">
            <option name="glsl_zero_init" value="true"/>
        </application>

[shyney]

Good news! The latest Steam OS beta update, 3.3, includes graphics driver updates and I’m no longer crashing in the tutorials! I think we’re finally in the clear!

It seems that SteamOS 3.3 is going to fix this issue!

[GeometryPrime]

Can confirm SteamOS 3.3 fixes this - Starsector works great on this machine now!