steam-for-linux
steam-for-linux copied to clipboard
ValveSoftware
[Overlay] Steam Overlay is glitched when playing Terraria.
Your system information
- Steam client version (build number or date): 1624650462
- Distribution (e.g. Ubuntu): Arch Linux with Plasma Desktop
- Opted into Steam client beta?: Yes
- Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:
When using Steam Overlay in Terraria, the overlay is broken and unresponsive. Others are also experiencing this issue.
- https://www.reddit.com/r/Terraria/comments/ms53o4/has_anyone_elses_steam_overlay_broken_like_this/
- https://www.reddit.com/r/Terraria/comments/mtkvme/help_manjaro_linux_steam_overlay_is_glitching/
Steam overlay is required to start co-op servers without manual intervention.
Steps for reproducing this issue:
- Enable Steam Overlay in Steam Client Setting.
- Start Terraria
- Hold SHIFT+TAB
Tried Solutions:
- Using Steam Non-Beta Client.
- Using Mesa-git ( 21.2.0_devel.141851.3a9716e6b1f-1)
- Enabling/Disabling K-win Screen Compositor(x11).
None of these methods have worked so far to fix the issue.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4191 is further along in evaluating this issue.
I have exactly the same issue but with unrailed, so it seems to affect more than one game
@Tau5 if I am not wrong, I believe a valve developer (Plagman) already knows about this issue.
This seems to affect (at least) FNA titles, I've seen it in:
- Full Metal Furies
- Rogue Legacy
- Escape Goat 2
- Streets of Rage 4
Here's a video of the corruption on an RX580, Mesa 21.1.4. Same issue appeared on an HD2000 Intel iGPU.
Found a workaround for Arch Linux users:
- Using the AUR, install amdgpu-pro-libgl
- Open Steam Client and Click on Terraria
- Add the Launch Option
progl %command%
Start the game and use Overlay.
Found a Fix for Arch Linux users:
- Using the AUR, install amdgpu-pro-libgl
- Open Steam Client and Click on Terraria
- Add the Launch Option
progl %command%Start the game and use Overlay.
It's more of a workaround than a fix. Using the mesa driver over amdgpu-pro is highly preferred for most applications.
@crumblingstatue
$ glxinfo | grep "OpenGL vendor string" | cut -f2 -d":" | xargs
AMD
I am using the open drivers for everything except for Terraria, hence the launch option.
https://wiki.archlinux.org/title/AMDGPU_PRO#How_to_ensure_you_are_using_AMDGPU-PRO_driver
My point was that you shouldn't have to use AMDGPU-PRO for Terraria either. Hence a workaround, rather than a fix.
This is also a problem for Intel Iris (i7-1165G7) with Celeste. Both on Wayland and Xorg.
Same here, with a RX 570, using Zorin OS and Pop OS (Both based on Ubuntu)
Another workaround for FNA games is using -gldevice:Vulkan, but I have found that causes Terraria to crash. Celeste has yet to crash on me with that setting.
Another workaround for FNA games is using
-gldevice:Vulkan, but I have found that causes Terraria to crash. Celeste has yet to crash on me with that setting.
Can confirm that Terraria crashes with this launch option. The game loads and the Steam overlay works fine, but the game randomly crashes while playing.
This bug is now confirmed as affecting the Steam Deck - if this bug is not fixed soon, many games will fail to render at launch.
The Steam Overlay is a separate window so it gets its own plane on the Steam Deck so, I doubt this is the same issue @flibitijibibo
If the Steam deck is affected by this it means that this issue is probably going to get a lot more attention, which will hopefully fix it.
Where does it say it affects the Steam Deck? The graphics side of the overlay shouldn't run its hooks there.
We appear to be running into the same issue as before where GL_COORD_REPLACE affects all rendering - this was fixed in radeonsi a few years ago as far as I know. The overlay is affected on desktop regardless of hardware, but for the Deck's gamescope instance in particular we're seeing untextured geometry from the game.
Going to work around this in FNA 21.10 I think... if a game affected is not in this list, please add it:
- Apotheon
- Capsized
- Cryptark
- Gateways
- Shuggy
- Growing Pains
- Soulcaster 1+2
- Escape Goat 1+2
- AVNT
- Rogue Legacy
- Dust: AET
- Blueberry Garden
- Fist Puncher
- Skulls of the Shogun
- TowerFall Ascension
- Bleed 1+2
- Rex Rocket
- Wyv and Keep
- Wizorb
- Mercenary Kings
- Flinthook
- Sequence
- ~~Salt & Sanctuary~~ Updated! (See fna-win32 branch, ignore the name...)
- ~~Charlie Murder~~ Updated!
- ~~The Dishwasher: Vampire Smile~~ Updated!
- Hidden in Plain Sight
- Quadrilateral Cowboy Art Book
- Full Metal Furies
- Flotilla
- Unexplored
- SUMICO
- Little Racers STREET
- ~~FEZ~~ Updated! See public beta branch.
- ~~Steel Assault~~ Updated!
- ~~Streets of Rage 4~~ Updated!
- Star-Twine
- Celeste
- Unrailed
- Terraria
- Chasm
- Staxel
I'll try and update all except the last 4 within the next month (I still have a script from the last time I updated 35 games at once...). For those last 4, please let the developer know that they will need to update to FNA 21.10, which releases on Friday. This will be a pretty massive deployment that will take a long time, so if you want to move it along faster...
This issue is not overlay or Steam related. It can be reproduced by doing gamescope -w 1280 -h 800 -O eDP-1,DP-1 -- ./FEZ directly in from a tty with no Steam running at all.
Could be a radeonsi/Gallium regression in Git (latest stable Mesa is okay), might need someone to check while I keep an eye on Steel Assault this week.
On https://gitlab.freedesktop.org/mesa/mesa/-/issues/4191 the developers claim it is not a Mesa issue. I don't know what the truth is
It's possible that the original bug and what Ethan mentioned in the last few comments could just be different issues.
Turns out it's a combination of both - the overlay does still likely need to reset GL_COORD_REPLACE state, but for the Deck in particular there appears to be a radeonsi regression that is worked around in the latest FNA3D. For games that are updated to 21.10 or newer it won't be an issue but it may be a concern for older games that may not have an active maintainer. The above games should produce a repro case if needed (with the exception of the FEZ beta and Charlie/Dishwasher/Salt, which I updated this morning, and Steel Assault which is launching today).
Deck just happens to use recent Mesa with no functional changes to GL rendering at the moment, so odds are it's a problem on Mesa main on recent AMD chips as well. Can you point us to the workaround so we can look at it from that side?
Workaround: https://github.com/FNA-XNA/FNA3D/commit/f8d0443568df6b57803b80a39c86a35047bd66dc
The previous version would enable point sprites and set GL_COORD_REPLACE to 1, since we only support point sprites with gl_PointCoord/gl_TexCoord[0]. Instead, we now wrap each glDraw* with the same two calls, enabling and disabling with each GL_POINTS draw.
The regression may have already been identified:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/5423
Commit in question: https://gitlab.freedesktop.org/mesa/mesa/-/commit/11d1309d8276768aca3f02ddd7cc57cdb323113c
Merge request for anyone that's self-building Mesa:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13105