I don't recall ever seeing that, but if it exists it would have to be Jupiter hardware support
I don't recall ever seeing that, but if it exists it would have to be Jupiter hardware support
KSince that is the only thing that contains controller firmware and the updater for it
MI think I’m going to reinstall steamos to see if I’m imagining it or not
Motherwise I think it gets set to check when you boot the system once it creates the Sentinel file with the initial firmware update package.
Mthe controller update script itself is pretty clever, it detected the abnormality in my system and that it was running in an app so it automatically flashed the latest firmware for my system
MLet me know if you want me to grab any files from steamos mangohud while I’m at it
BQuestion that is probably answered but how impactull is the fsync Kernel in regards of the regular one? Especially on Deck?
Kchanges are mostly patches necessary for OLED deck
Ka lot of what it does otherwise we were already doing one way or another
Kso most users won't notice a major difference
CI setup the moonlight from flat hub and I'm getting crackling double audio streams. What about you?
Myep you’re right, there’s no such button in SteamOS.
Kmay exist only when an update is available
Kif you want to meet in the middle lmao
MThe only audio issues I’ve had have been 5-10 seconds of stutters every 10 minutes or so. It’s probably some part of your network setup. If you’re WiFi 6 try WiFi 5 or vice versa. Or 2.4ghz vs 5ghz
CHost is on Ethernet and deck is on WiFi 5
CI'm using sunshine
MNah I actually have no clue how they’re supposed to get triggered anymore lmao. I’m on SteamOS 3.5.10 and it flashed a week-old controller firmware version. December 6th instead of December 11th. No updates found when checking manually.
I think I installed pre-release firmware when I downloaded manually from evlaV yesterday
I think I installed pre-release firmware when I downloaded manually from evlaV yesterday
AWorks like a dream!
Knot able to reproduce this
KPlaying Crysis and seeing 16W draw atm
Koh hold on, this is a display issue
KCPU shows as 0W, GPU shows as 14W
M^^
Kthis isn't a 14W gpu. that's the actual APU's wattage
TYeah that sounds right.
Mmatches Nobara findings too
KI'm gonna let that work itself out upstream
Kno reason to spend time on it unless I can PR the fix
VOnly the best for bazzite users! /s
Mit seems like the sort of thing that might just start working after a random package update someday
Kprobably a mangohud update, we just build git master so whenerver it's fixed we'll have it same-day
Kthat or a gamescope update that changes what it passes to mangoapp
TAt this point Bazzite is life. The Deck was my last system to install it on so I'm commited to the wait.
Mdo you still have the frame time graph when you set the Steam performance overlay to notch 2 (the wide one)?
TI don't unless I set it to histogram.
Kempty space there
Klet me see what version of mangoapp valve is shipping
KI can always roll back
Mokay I think that was a mangohud update that got pushed yesterday. Nobara has the same issue.
Mdowngrading one version restored it for me
Malthough it may be two by now if GE pushed any additional updates
Kthis is the commit upstream is building
K
Kthis is everything new since
Kgonna guess frame_timing_detailed broke something
Krest are pretty benign
MI’ll have to compare that against the copr updates. I don’t know if that commit is the same or different from that steamOS mangohud update that changed how the graph works so it wasn’t all choppy
Msince that was working for a couple days on nobara
MAnd then yesterday was when it disappeared
