Cwhat does this solve again? - also is this on testing or stable
CIt appears to fix the 144 Hz and 60 Hz plus the fps limiters, testing it seems
KOk, audio popping should be fixed on testing with the workaround we did for min quantum removed
KAdditionally I've reworked how valve applies their wireplumber changes, which should have fixed the random audio crashing people were seeing
KFrom what I can tell, it was a race condition issue due to the changes valve makes requiring wireplumber read it's config from run
KInstead I applied the same fix we did for SE linux, where the original config is moved into usr/local and mounted back over top
KThen I simply changed valves code to replace the file in its original location and not in run
KThat means no hacking around in wireplumber
KAt the very least I've not been able to reproduce it, we'll see what happens
MNice, I could tell our audio setups were slightly different before based off some of the UI sound effects. I’ll have to try it again and see how it sounds now.
MI’ve found my way into the server of 
, I plan on reviewing the history and finding whatever I can on the refresh rate and HDR metadata for myself
, I plan on reviewing the history and finding whatever I can on the refresh rate and HDR metadata for myself
Hyou would need to do that using a live usb that lets you open up a partition manager you are comfortable with like gparted and rename it from there, as you cannot do it while the disk is mounted
CHas anyone used 3rd party sticks like the Gulikit ones on Bazzite? Does it have the thumbstick_cal script for calibrating the thumbsticks?
Hthumbstick_cal is part of bazzite
Honly works with deck hardware though as it is deck specific (meaning it also works with the guilikit sticks as they are deck compatible), so you cant calibrate controllers with it
CGot it, means I can still calibrate Gulikit sticks on the Steam Deck just as usual, thanks!
MValve branding, no installation is what I think they have on their mind.
R@Kyle Gospo when you have time, jupiter-config.yaml has dry-run: False missing as a parameter and break fan control.
R(Since their script load it when booting up)
RCheck in the Galileo one and you will immediately see what's missing, should be easily fixable with a small patch.
Rhere it is
Rfan_fix.patch503B
APreviously, when running a game at 144hz it would often artificially cap fps at 72fps max. The fps limiter would also be buggy and completely wrong. This should fix it
C144 hz seems to be working
AThis is with the script?
CYeah
CWas at 72 before reboot
CNgl tho not sure if it’s cause of the script 100% cause i also ran an update
CCan comment them out now tho to do a quick test
AYeah, you can remove the conf file in
~/.config/environment.d to revert the script's changesCLol dont thinj it changed anything
C144 seems to be working without that
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
