hrm, so gba worked no problem for me w/ dualsense edge emulation
hrm, so gba worked no problem for me w/ dualsense edge emulation
Awas able to boot into the game + use the d-pad right away
AIm looking into updating retroarch (it should already be up to date b/c I installed everything like 2 days ago) and it gave me an interesting error message "was not able to configure dualsense controller, using fallback" or something similar when opening the program
AExcuse the scuffed screenshot
Awell, i guess it at least recognizes it as a dualsense edge controller
Aquick question, if you open your QAM, and look at the Quick Settings, do you see an option to re-order controllers?
Asometimes the emulated dualsense edge gets registered as player 2
Adunno if that'd be related to your bug, but doesn't hurt to check
MOh I found my problem
MSteam input 
MIt works if you force all devices an then choose a deck layout
AUnfortunately not, dont see any options like that in that menu
Aaight, well that rules out one possibility
Acould you manually remap it? open retroarch in steam, then go to
Settings > Input > Retropad Binds > Port 1 ControlsAyou can choose
Steam Virtual Gamepad as the Device IndexAand then remap each key one-by-one
Anote, this is assuming you open retroarch through steam
MTested across both bazzite and nobara without any showstopper issues: https://copr.fedorainfracloud.org/coprs/matte-schwartz/sunshine/
MKyle, you might want to try throwing that in a testing build to replace the old nightly build artifacts that get pulled from GitHub
MFor me on nobara it works across even session or TTY switches, while bazzite seems to die between session swaps
MMaybe a product of GE’s session switching script? I’m not sure.
AThis program is very gross
AIf i manually remap it, I think the "core" profile overwrites it as soon as I open a game w/ mGBA
AI can make it recognize the dualsense edge by opening the game and toggling fps mode though 
Ayeah, retroarch gui sucks
Ayou're definitely in x-input mode, right?
A
AI havent changed this setting(to my knowledge), but im trying to double check. For whatever reason the light flashes seem to be blinking multiple times no matter what
Ableh, i wish lenovo made it more difficult to change input modes. it's possible to accidentally trigger it, a 1s hold is too short
Anot sure if it's your problem specifically, just a general issue that i've encountered multiple times before
Rgah my wifi cut out again
KVery strange
KI'll keep an eye out
KAppreciate the heads up
MIf anyone reports the same tell them to try a Deck community layout. It’s an issue with the default steam input layout.
KHey that's a win, as long as it's not in the kernel
Amisc side note, the issue we saw earlier with the unified refresh rate slider not correctly showing 144hz is most likely due to steam caching values of some sort.
i rolled back to an image without the gamescope patches, but the refresh rate slider still behaves as if gamescope is patched. I'm assuming it'll go away after a few reboots
i rolled back to an image without the gamescope patches, but the refresh rate slider still behaves as if gamescope is patched. I'm assuming it'll go away after a few reboots
Mmy guess would probably be the EDID file that gets generated and sometimes replaced
ALenovo legion go vs steam deck oled which u recommend the most to get but lenovo has same battery as steam deck oled
Adeck for better battery life + software support from valve
Algo if you want higher peak performance at the expense of battery
Abut also detachable controllers is a plus
VThey have the same battery capacity but the Deck lasts a lot longer
ADue to resolution right?
Amaybe a bit, but primarily due to chipset
VResolution, APU, No controllers to charge, less intense cooling system
VThere's a lot
Az1e uses up lots of power, and can go 2x the 15w TDP limit on the deck
AAlright I guess I will go for deck then
VLegion still has it's merits
VBattery just isn't really one of them
