Go to desktop mode click audio in task bar and select off for the wrong one then it worked fine for
Go to desktop mode click audio in task bar and select off for the wrong one then it worked fine for me
E
EThis fixed issue for me
E@KyleGospo is there anyway to remap the home button pkus right joystick as mouse to another button plus joystick as my controller shuts off if holding home
Kcould try the remapper we bundle for that
Mthx bro
Xis there a recommended way to scrape things for retrodeck? the built in scraper for emulationstation is super slow, and for some reason, if I turn off my display and turn it back on, that causes Retrodeck to terminate itself
BIn gamemode, despite my dim settings under display my screen never goes black anymore (not even a backlit black). Is that standard behaviour?
BI should specify I'm on steam deck lcd bazzite 39 but the image is about 3 weeks old
HUnless you can set one of the back buttons as the guide button I don't think we can solve that as the shutdown is hard coded into the controller
CNice one https://github.com/ublue-os/bazzite/commit/a7af503577cf2b2aa0894d7d51c8001b9107dd69
- how long does it normally take for testing to get to prod?
HDoes that on kde too for me if I move or resize the window I'm recording so maybe related?
VI think it depends on the feature
VSome smaller features will be very quick
VBigger ones are going to be longer
Dhow do I know if my device supports HDR?
CThis might be a bit of a shitty take, but i never understood the hype with hdr - all my displays have hdr, just never really cared about it. Thought the jump would be as significant as 60hz -> 120/144hz but it was pretty underwhelming. OLED imo is a much higher jump.
ROLED is a higher jump but significantly more expensive and less accesible than HDR
His your steamdeck the oled version, if yes then it has HDR
other than that you will have to check your monitor specs
other than that you will have to check your monitor specs
RMy keyboard now works again.
RI have no clue why today from terminal it has decided to show me a pairing code and then would not accept ANY input. I reconnect it now and magically it start working again.
DI just have the regular steam deck
RI have no clue.
Dit's possible that an update fixed it
RRNope, it still won't pair from any graphical utilities
RAnd it is still the not previously working 5.70
RThese appeared when I could associate with the keyboard and had no input.
DI thought you said it got paired
RFrom bluetoothctl
RFor whatever reason.
RIt would not pair at all from KDE or SteamOS
R**Game Mode, i mean
Dit needs to be fixed
RThe HID failed to bind it, but I doubt that the issue is the HID itself.
RIt's probably still the bluetooth layer that was providing wrong data to it if you ask me.
RAnd now magically, no update, no reboot
Rhid-generic 0005:046D:B33D.0009: input,hidraw4: BLUETOOTH HID v28.03 Keyboard [Keyboard K480] on I have no clue on what is happening, but I hope that 5.71 will be merged as soon as possible.
RAt least I have one less variable to exclude.
Cout of curiosity, is there a plan on how to handle F40's dropping of x11?
Cjust going along with it or trying to keep it i your build?
Hi might remember wrong but i think i read somewhere when i first joined here that x11 would be kept around for nvidia if it was still needed at that point.
PI'm using the x11 session on bazzite, but when I open the games it shows me that I'm using Wayland
PI need x11 to play Star Citizen, because in Wayland Nvidia there is a bug in the cursor
KWe already ship wayland by default
Kthe plan is to just do it
Kif Nvidia still has issues by then I'll include the missing x11 session in nvidia builds
CYeah I know wayland is on there already and the default compositor. I mainly ask because I need to use x11 to get sunshine to work as it seems to find no encoders on wayland and I'm on amd
CI totally get not wanting to try and support a whole extra compositor though
