yeah well that’s not really a fix, that’s a workaround
yeah well that’s not really a fix, that’s a workaround
Jit would be best if someone could track the issues down
AKinda but not really. Depends on your purpose
AYes it would be great if it worked at the latest kernel
ABut the steam decks are the first x86 devices with a mobile display
ASo you can t expect 0 issues
ALegion go as well, but it only has 2 refresh rates
MGamescope has somewhat less ambiguous logging now, next steps are using Gamescope-git and a stupid amount of bisecting since it isn’t any of valve’s commits they added or dropped
Mif there hasn’t been any progress by anyone by the time I get back from traveling I’ll probably gather data and hit the Volvo button
ADo you know when they're moving to Wayland for the atoms?
AEven tho the overlay code is very simple
Mhaven’t seen anything mentioned or in the commits afaik
MI assume as a part of the drm refactor but who knows how long that will actually take
AI think there's a gamescope file where they moved the atoms but that's it
AFor wayland
Myeah haven’t seen movement on that on the Gamescope side, but I also have no clue how tf valve splits up their contractors’ and engineers’ time between projects
AHopefully we get a year out of the x11 atom business then
Mlast I heard they’re still plenty happy with x11 for their purposes overall
MI’m actually pretty curious to see how the OLED Deck handles plasma 6 HDR and what metadata it spits back out at you
MI still get a mismatch in luminance metadata between kernels on OLED Deck within Gamescope-session. Way easier to point to that in logs than “hey, look at my screen go black for .1 seconds vs .7 seconds” in a video clip with no helpful logs to back it up
Mtested 6.8-rc6 which should have all the relevant HDR stuff upstreamed and the metadata in my logs still didn’t look right compared to SteamOS, so I’m kind of hoping the two display issues within Gamescope are related
Dmy crappy little CLI tool works T_T automated non-steam game imports coming in hot!
Dit even correctly sets the compatibility tool, instead of dumping on steamtinkerlaunch, im going to ask the dev if he can just include this python library instead of whatever the hell he's doing with his bash script
Ayou cant, if its bash its bash and he cant repackage
Aif you figure out how to do the hero and capsule icons tell me
Aalso, this basic functionality is built into steam
Aby that meaning adding a desktop file to steam
Doh yea that's easy part
Dim about to push again, you can view the latest commit
Aif you want a command to add a desktop file to steam steam has that built in
Ait is also supposed to do icons
Abut it abuses me and does not
Doh i did it the hard way, by adding all my artwork to the config/grid directory, and the icon to the vdf lol
Di forgot about that command...
Ait cant edit them afterwards
Abut it can add them
Dwait LOL... i could've just have created .desktops
Dah well whatever this was a good exercise
AGitHub
The main UI for the Handheld Daemon. Contribute to hhd-dev/hhd-ui development by creating an account on GitHub.
Anow if i can only figure out why it doesnt add the images
Aeven the capsules are ready
Dtwo seconds lol
D
Dartwork is simple for the most part, with the exception for the icon, god i hate that both both binary vdf and ascii vdf both have the .vdf extension... its clear that valve is run by a former microsoft employee
Dah i spoke too soon, the icon is still broken, but anyway for the images you just gotta make sure to drop them here: ~/.steam/steam/userdata/<userdata>/config/grid
Dit might work if you also drop them in here: ~/.steam/steam/appcache/librarycache
Dbut that's not where steam puts them when you add non-steam games manually
AThat code was written 20 years ago
ALmao
AWhere does steam put them
AFor me it doesn't put them
