Is this only with Warframe? Do you use X11? If so, could it be defaulting to a lower Hz second monitor or something? I suffered with this for years until I swapped to Wayland. Just a thought.
this post was submitted on 18 Jun 2024
34 points (97.2% liked)
Linux Gaming
15493 readers
32 users here now
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
founded 4 years ago
MODERATORS
I'm on Wayland, so no X11 shenanigans going on here ๐ญ
You may have seen this already, but on the GloriousEggroll Github it mentions not having V-sync set to "Auto"
https://github.com/GloriousEggroll/proton-ge-custom?tab=readme-ov-file#notes
I had not seen this, but V-sync was off all the time :(
Playing on a 240hz monitor at 240hz or is it at the default 60hz? Could be as simple as a click of a button!
Monitor and game both running with 240hz set as refresh rate, game is also set to max fps at 360 but also have display refresh rate set to 240hz (yes, there were separate options for this)
Unlikely to help, but while you're experimenting: PROTON_LOG=1 PROTON_LOG_DIR="/tmp/" WINEDEBUG="-all" fixed some extremely annoying hangs during loading screens for me. Probably a 1 in a million chance it helps in your case, but who knows.
Edited the original post but might aswell comment it. I switched to GNOME (Wayland) and the FPS issue seems to be gone there. I ran the game with only the command line arguments "gamemoderun %command%" in steam and it seems to work properly. Very odd issue.
I see you're using MangoHud. Does your frametime graph look flat, or is it going haywire? In my case, I had games running around 120fps, but displaying at a rate that felt below 30. This was the case until I ran games with MANGOHUD_CONFIG="vsync=3". Could be worth a shot.
I will try this, the graph looks flat though.
Update: This did not solve the problem :(
In my experience this is almost always the compositor not properly syncing display frames with the game render frames. The best solution I've personally found is to run the offending game through game scope. It worked for Fallout 4 on my rx 7600xt gpu when I went to lock the fps to 60 (to avoid physics bugs, stupid Bethesda). Without game scope locking the frame rate caused horrendous stuttering despite solid fps.
I attempted to run the game using gamescope but I'm not very familiar with using it, I was unable to add gamescope to the steam command arguments and also running the game executable with the command through the terminal. I'm not sure what the error is or if I'm just not using gamescope correctly.
Should be something like - "gamescope -W 1920 -H 1080 -f %command%" I will also note that mine tends to crash/not launch if I don't put Mangohud arguments BEFORE gamescope. The w and h arguments are just width and height resolution, so set those to match your monitor. The "-f" is for full screen.
I removed all of my other arguments and tried to start with "gamescope -W 2560 -H 1440 -f %command%", when I start the game the "Processing Vulkan Shaders" steam pop-up shows up, and when I click "Skip" (as I always do) it just disappears, no error or anything, the "Play" button on steam just goes back to green.
Interesting. I haven't had any issues with gamescope for a long time... Back when it was new I definitely had issues running things with it... But it's been a long time since that's been the case. I can recommend running steam from a terminal and viewing the output after trying to run the game with gamescope. It might point you in the right direction.
Good info, I will try this tomorrow and report back.
Might be worth trying gamescope on another known working game too. Would help narrow down if it's gamescope itself or the game you're trying to use it on.
Got gamescope working but the issue still persists. I'm gonna try launching in different DE aswell as letting shaders fully compile.
Launching it in GNOME (Wayland) seems to fix the issue. Very uncertain what this issue was but it seems to be related to KDE.
(Also I did not let the shaders compile, so not a shader issue)
Weird! I'm running Bazzite kde (so fedora based, like Nobara but with different tweaks and it's atomic), and gamescope gives me zero problems. Might be some weird combination of software versions between gamescope and kde in your system. Or just a general kde config problem. I love kde, but all that customization can absolutely come at the price of stability at times.
What KDE/Kwin version do you use? Would be interesting to compare.