Celeste

Celeste

View Stats:
Luna May 28, 2021 @ 9:46am
Steam Overlay broken
I just decided to play Celeste again today, and noticed that the steam overlay is completely broken (screenshot[imgur.com]). It just renders solid colors instead of text. I'm on Arch Linux (fully updated as of posting), with GNOME, on the Steam Beta. From my testing, this happens only with Celeste, both on Wayland and Xorg (tried both because I saw this game has native Wayland support), and also when running the Windows build through Proton

This isn't a game-breaking bug, of course, but it's a bit annoying that I can't use the overlay
< >
Showing 1-9 of 9 comments
flibitijibibo  [developer] May 28, 2021 @ 4:47pm 
I know for sure the Steam overlay doesn't support Wayland yet, but X not working is unusual - since it affects multiple different builds I would file this as a Steam issue, we aren't doing anything unusual with frame presentation.
Luna May 30, 2021 @ 1:59am 
I did some more experimentation, and I found out that the overlay works when I run the game on an Nvidia GPU, but not when I run it on an Intel GPU. And I don't think this is a Steam issue, because I tried other games, and it worked fine in every game I tried
Silejonu Jun 29, 2021 @ 1:29pm 
Same issue here. Running Arch Linux, on GNOME Wayland with an AMD GPU (Radeon RX 570). This is the only game that I've encountered this bug with.
Last edited by Silejonu; Jul 16, 2021 @ 10:50pm
prezmop Jul 16, 2021 @ 2:39pm 
I did some experimenting and found a workaround.
It involves replacing libFNA3D with a newer version (i used 21.7, others untested) and forcing the game to use the vulkan renderer ( /gldevice:Vulkan in launch options).
It also seems to fix an (unrelated?) issue where textures sometimes won't load correctly. I understand that using Vulkan is not always an option, but i hope this helps.

EDIT: after some more testing it seems to introduce freezes. Would not recommend actually playing like this.

EDIT 2: The freezing issue could be related to my laptop.
Last edited by prezmop; Jul 16, 2021 @ 3:27pm
Silejonu Jul 17, 2021 @ 3:29am 
Originally posted by prezmop:
I did some experimenting and found a workaround.
It involves replacing libFNA3D with a newer version (i used 21.7, others untested) and forcing the game to use the vulkan renderer ( /gldevice:Vulkan in launch options).
It also seems to fix an (unrelated?) issue where textures sometimes won't load correctly. I understand that using Vulkan is not always an option, but i hope this helps.

EDIT: after some more testing it seems to introduce freezes. Would not recommend actually playing like this.

EDIT 2: The freezing issue could be related to my laptop.
Just forcing Vulkan rendering allowed me to use the overlay just fine. However, one has to wait the usual 5-10 minutes the first time launching the game for all the shaders to compile, or it will stutter like crazy. Even after that, I found that I still had some micro-stutters from time to time (every 5 minutes, I'd say), and I think some slight input lag. Actually, I'm not sure about the input lag as I didn't notice it at first, but once I reverted back to OpenGL, it felt a lot more responsive, and I got my last berry on the first try with ease, while I was struggling with Vulkan the second before. Maybe it was luck, I don't know, but I think I'll stay on OpenGL without an overlay for now.
Silejonu Jul 23, 2021 @ 10:02am 
Originally posted by flibitijibibo:
I know for sure the Steam overlay doesn't support Wayland yet, but X not working is unusual - since it affects multiple different builds I would file this as a Steam issue, we aren't doing anything unusual with frame presentation.
I just tested Towerfall and it has the exact same issue. I never encountered this issue on any other game apart from Celeste and Towerfall.
I'm having this issue too, on Arch Linux with a pretty old AMD GPU (Radeon HD 6350).
coin Sep 12, 2021 @ 9:12am 
Having the same issue, and there's nothing about it on PCGamingWiki. Here's my neofetch:
██████████████████ ████████ quinn@superae ██████████████████ ████████ ------------- ██████████████████ ████████ OS: Manjaro Linux x86_64 ██████████████████ ████████ Kernel: 5.13.13-1-MANJARO ████████ ████████ Uptime: 2 days, 19 hours, 43 mins ████████ ████████ ████████ Packages: 1155 (pacman) ████████ ████████ ████████ Shell: bash 5.1.8 ████████ ████████ ████████ Resolution: 1920x1080 ████████ ████████ ████████ DE: Xfce 4.16 ████████ ████████ ████████ WM: Xfwm4 ████████ ████████ ████████ WM Theme: Mojave-dark ████████ ████████ ████████ Theme: Mojave-dark [GTK2/3] ████████ ████████ ████████ Icons: Papirus-Dark [GTK2/3] ████████ ████████ ████████ Terminal: xfce4-terminal Terminal Font: Monospace 12 CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz GPU: AMD ATI Radeon RX 6700/6700 XT / 6800M Memory: 4056MiB / 23969MiB

Update: I'm also having this issue in Terraria. https://i.imgur.com/VuqMnzG.png
Last edited by coin; Sep 12, 2021 @ 11:24am
coin Sep 12, 2021 @ 3:56pm 
After searching the internet a bit, I found this.[github.com]
Here's a workaround for Arch users with AMD GPU's: install
amdgpu-pro-libgl
through the AUR, enter the properties for Celeste and add the launch option
progl %command%
.This is only a workaround because it is usually preferred to use the mesa driver over amdgpu-pro.
< >
Showing 1-9 of 9 comments
Per page: 1530 50