Steam Overlay doesn't work in Warframe

[zainin]

Hi,

I saw in a Gamescope issue you wanted a log for this problem (although I'm not the guy you asked ;) ), so here you go:

Launching: env -u LD_PRELOAD gamescope -f --force-grab-cursor -W 3440 -H 1440 --hdr-enabled --adaptive-sync -- env LD_PRELOAD=":/home/zainin/Steam/ubuntu12_32/gameoverlayrenderer.so:/home/zainin/Steam/ubuntu12_64/gameoverlayrenderer.so"  "/home/zainin/Steam/ubuntu12_32/steam-launch-wrapper" "--" "/home/zainin/Steam/ubuntu12_32/reaper" "SteamLaunch" "AppId=230410" "--" "/media/storage-ext/Games/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point" "--verb=waitforexitandrun" "--" "/media/storage-ext/Games/SteamLibrary/steamapps/common/Proton 9.0 (Beta)/proton" "waitforexitandrun" "/media/storage-ext/Games/SteamLibrary/steamapps/common/Warframe/Tools/Launcher.exe" "-cluster:public" "-registry:Steam"

Everything works except for the Steam Overlay.

[HikariKnight]

works for me?

what i notice though is that your LD_PRELOAD is somewhat broken
LD_PRELOAD=":/home/zainin/Steam/ubuntu12_32/gameoverlayrenderer.so:/home/zainin/Steam/ubuntu12_64/gameoverlayrenderer.so"
i see it starts with : which might cause the issues

the only interaction that scopebuddy has with LD_PRELOAD is literally moving it to a different variable (LD_PRELOAD_REAL), unsetting it and then setting it again for %command% using that temporary variable (env LD_PRELOAD="$LD_PRELOAD_REAL" %command%)

i would say try figure out why the LD_PRELOAD is weird for you

[HikariKnight]

Alternatively @zainin if you can set your launch options in steam to echo $LD_PRELOAD > $HOME/for_scopebuddy_issue.log and run that once and send the contents of for_scopebuddy_issue.log here then that would be helpful too, i could maybe try sanitize the LD_PRELOAD and remove any : at the start or the end, but it shouldn't be scopebuddys job to do that when it does not modify it 😅

[zainin]

Well, it's the same value as in the scopebuddy log.

My Steam install isn't modified in any way, and outside Gamescope the Steam Overlay works fine in all other games, so I don't think it's the LD_PRELOAD that's the problem.

[HikariKnight]

Well, it's the same value as in the scopebuddy log.

My Steam install isn't modified in any way, and outside Gamescope the Steam Overlay works fine in all other games, so I don't think it's the LD_PRELOAD that's the problem.

i just tested the theory with LD_PRELOAD and youre correct it was not the culprit. however the only way i managed to replicate this issue was if i disabled the steam overlay in warframes properties, make sure it is enabled there.

For context i am also using GE-Proton 9-27 for warframe but any newer GE-Proton should work too, i just like using the oldest functional GE-Proton for warframe for support reasons (example: make sure you use at least this version or newer)

[zainin]

I'm on Steam's default, which is Proton 9.0-4, the overlay is enabled.

I tried exporting ENABLE_GAMESCOPE_WSI=0, which seems to fix the problem, but I didn't have time yet to test if it doesn't break anything else.

I tried GE-Proton 10-25, there's no difference.

[HikariKnight]

ENABLE_GAMESCOPE_WSI=0 will break HDR (requires running warframe with dx12)

can you provide me with your scb.conf and your scopebuddy config for warframe? so i can try them myself

[zainin]

Sorry for the late reply.
You're correct, this breaks HDR - I had some trouble testing because HDR in Proton was broken for a bit on latest Plasma...

Anyway, here's my config, everything else is on defaults:

SCB_GAMESCOPE_ARGS="--mangoapp -f --force-grab-cursor"
SCB_AUTO_RES=1
SCB_AUTO_HDR=1
SCB_AUTO_VRR=1

Also, with -e switch I can't start the game at all, I can hear it running, but the window doesn't appear, although I'm not sure this is related to this issue.

[HikariKnight]

sorry for the late reply
the -e flag breaks nested gamescope and scopebuddy should strip it in the current versions.

are you using wayland proton? i heard that using wayland support in proton breaks the steam overlay too (not sure about input)

[zainin]

Not really sure, do you know how can I check it?

I do run KDE on Wayland though, and the only issue I have is with the overlay in Gamescope.

[HikariKnight]

Not really sure, do you know how can I check it?

I do run KDE on Wayland though, and the only issue I have is with the overlay in Gamescope.

are you using GE-proton (or similar) with

export PROTON_ENABLE_WAYLAND=1