Go into the steam settings and make sure you have a button bound to open keyboard
Go into the steam settings and make sure you have a button bound to open keyboard
KI recommend x, that's the default
Csteam
is defaultx
KWith newer updates just X is also the same in the desktop layout
Calso if you got xbox controller,
xbox button + xAnd steam plus anything is a little harder on Ally due to a hardware flaw
KYou have to press Steam and then the button
Coooooh, friend mentioned that it's weird on the Ally
CCan I use the back buttons for that?
CYou should be able to
C
RYeah, saw a similar report on github, left feedback of this there also.
CThe remapping in steam is mad customizable
ROpened two days ago, interesting enough.
COH same here. When I am in discord VC and warframe it's mad sluggish on anyhting that is not the game. Putting the legion go in
Custom TPD mode seems to fix it mostlyCNot sure if it's how the Legion Go TPD modes work or smth else
ASomebody link the discord overlay
RGitHub
Steps to Reproduce Steps to reproduce the behavior: not sure i was installing rocm drivers and invokeai in the background, that might have caused it note that i wasnt in a call when it happened Exp...
AThat's bc it's 30w
Ccould it also be the way it handles the clock speeds on CPU and GPU between different modes?
ALmao no it's because you need to max out your device for it to work
CFair
ADoesn't have anything to do with gamescope it seems
AHow do you use it?
COh, it was in desktop mode
RI don't 
AThere's a little leftover bug before we can nix the Asus image
RJust disable the autospawn and I guess I'm good XD
ARandomly the ally after suspend will decide to be 10w
TI'm looking, but I;m on a work call currently
AUntil you plug it in agajn
ABut it's like 10% of the time
RYeah, it was nasty to discover this while doing other stuff.
RStill, it's fine. It's off now anyway XD
TWhat desktop env? I literally can't cause this
RKDE Wayland
RIt might have started when an odd xwayland window opened
ROdd in the sense that it was empty
RI closed it after like a couple of minutes.
RI had another xwayland client open on my desktop
TPegging 1 core/thread has been fixed in git but can't cause the memory leak right now. I'll get right on it after hours
RNo prob, take your time.
T(Just seen reply on github, sorry)
RYeah, no problem.
RIt might a xwayland correlated issue
RLiterally transparent, not visible. Just the window border was visible.
Tcould feasibly be discover overlay there, any window title?
RDidn't check, sadly.
NWhich is better for a handheld console Linux or Android just a question
TBut this implies that discover is loading through xwayland which is definatly going to break it in wayland
RI just did not think of anything in that moment.
