AOoo so the recent update fixes it then
CRebooted and everything
CWhat’ wsi do btw
ANice! This is interesting
AMy understanding is that it does some config related to the fps limiters
ADid you also test to see if the fps limiter is working as expected now?
CGimme a sec bazzite’s been stuck on boot for a while lol
CRan into the previous prob again tho with the env setup, it basically defaults to 72 when you open a game for the first time, but then once you move the fps limit from 144 to something else back to 144 it seems to go to 144
CDoesnt seem to be happening with the env
ADid you mean without the env setup?
CYep
AHrm, so the env setup does fix something there then
Cw8 actually, it’s also happening without
CIm so confused mate haha
AOh, lol. So the fps limiter is still a bit wonky. Ok, let me try testing without the env var and see what happens
AYou're on the latest testing branch?
AThanks for helping with testing out the fix btw
COk just gonna list out the scenarios
- without env
Framerate inputs are 15, 30, 60, off
If framerate limit is off, when u open up a game, it goes to 72, switch it to 60 then back to off then it goes to 144
With env
U get access to 72 and 144hz input
But u still run into the same issues as the above
- without env
Framerate inputs are 15, 30, 60, off
If framerate limit is off, when u open up a game, it goes to 72, switch it to 60 then back to off then it goes to 144
With env
U get access to 72 and 144hz input
But u still run into the same issues as the above
CSo weird man
CYe im on latest of testing afaik
CI tried it again, 144 seems to work, “off” acts weird
CFuck
CI changed the refresh rate
CIt did the old tv screen line thing
ANote that you should be able to use 60hz
A...just none of the values in between
ASo I usually tap on my screen for to toggle between refresh rates
CDid a reboot seems to have reverted
CWelp, Mini heart attack right there
AOk, so you need the env var for refresh rate limits
ABut WSI doesn't seem necessary
TRestarting after an update in game mode now adds a 5 minute timer on
Job ostree-finalize-staged service/stop runningTTimer just got updated to 10 min but moved on by 6 min. What’s happening during this process?
TThe normal display during this time is the Bazzite logo and a spinning wheel
T
TThen these popped up. Sorry for the poor quality on the last one. Didn’t know it was coming up
T
T
TAnyone else experiencing the same after an update?
MA service is failing to stop on shutdown. When bad behavior occurs the spinner (Plymouth) backgrounds and shows the text interface so you can see the issue.
Which image are you. Date and branch.
Which image are you. Date and branch.
Rsame here
Rtesting
Tdate: today - branch: testing
Tlet me see if restarting without a pending update takes just as long
Tyep, it appears to do the same even without a pending update
T(just faster)
Ryeah, journald-flush seems to get stuck
MIf you have the previous image please try that.
If not please rebase back to previous date.
If not please rebase back to previous date.
MFunny enough. Please check the journal as well to see if anything is popping up on why it's failing.
A@Kyle Gospo think we could add
export STEAM_DISPLAY_REFRESH_LIMITS="60,144" for the legion go? as far as I can tell, it's working flawlessly on my LGO with the latest testing branch