The1AndMany

I already responded to this assertion in the other thread, but I'll do it again here to make sure everyone's on the same page: This is just plain incorrect. I dunno if it's different if you're running Windows, but at least on Steam Deck, launching WF from outside of BPM/Game Mode still forces you to navigate menus with the controller, and completely breaks the login screen due to the lack of an on-screen keyboard. (And no, the global chord of Steam+X to bring it up doesn't work in this case.) I still suspect this is due to WF checking for a gamepad once at startup, assuming that the player will be using that, not realizing that the Steam Deck controller can't be removed, and locking itself into controller mode. I don't doubt that you've had to deal with this forced controller interface yourself, and your frustrations seem genuine. I even agree with some of your suggestions on how to improve things. But please don't go around asserting something as true without verifying that it's accurate. You're only making it more difficult for those who are experiencing the issue first-hand to get it fixed. Edit: Upon further reflection, it's possible that if the Steam version of WF detects a controller on startup, it assumes it was launched from BPM, and forces itself into controller mode accordingly. I have no idea WHY it'd be coded that way, but it's at least possible, and might explain the confusion if true.

No offence, but that's pretty obvious. Potted history of my experience with WF on Steam Deck below: I prefer to play most shooters with KB+M if possible, so my first attempt (after some basic testing to make sure WF runs at all on Deck) was to switch to Desktop Mode and launch from outside of BPM. It still refused to let me navigate any menus with the KB+M, going so far as to completely break the login screen. Launching from BPM or Game Mode was at least functional thanks to the on-screen keyboard, but still forced me to navigate menus with the controller, and more-or-less broke text chat to the point that trading with other players became impossible. The workaround I ended up using was to link the WF executable as a "non-steam game shortcut" and use a launch option to bypass the Steam Input API. (See the link in my last post) As best I can tell, WF doesn't care if it's launched from BPM. It only checks once on startup to see if a controller is plugged in, and if so, assumes the player will be using that and locks itself into controller mode. And since the Steam Deck has a controller built-in that obviously can't be disconnected, that causes issues. Later on I decided to just use Windows for WF going forward due to AlecaFrame compatibility, and uninstalled WF from the Deck, including that workaround. At time of writing, I'm away from my main gaming rig for a few weeks, so I'm having to use the Deck again for the Recall: Ten-Zero event, and put up with the borderline-busted controller implementation. It's a shame, because aside from these controller issues, WF actually runs very well on Steam Deck. If DE were to fix it so that KB+M can navigate menus on Deck without a workaround, and if AlecaFrame were to add Linux support, I'd be more than happy to exclusively play it on Deck, and recommend that others do the same.

Update with call to action: DE is tinkering with their Steam Input configuration for Steam Deck specifically, let's make sure they're aware of this

Chiming in to highlight a particular issue for Steam Deck users. From what I understand, WF is hard-coded to lock itself into controller mode if it detects one plugged in on startup. Trouble is, this makes it impossible to navigate any menus (including the login screen) with a keyboard and mouse, and breaks text chat entirely. And because the Steam Deck has a controller built in, WF will always boot into controller mode. The current workaround is to use a "non-steam game" shortcut and launch option to bypass the Steam Input API (thread link: https://forums.warframe.com/topic/1319910-steam-deck-keyboard-and-mouse/?do=findComment&comment=12735044 ), but it'd be much better to have WF adapt control methods on-the-fly. Full disclosure: I don't play on Steam Deck anymore, because I use AlecaFrame and haven't had any luck getting that to work on linux.

Tried the Tamm herding anecdote while grinding for Pathos Clamps. A couple of them wandered a good distance away, into the area of the next bounty stage (find the hidden chest). While I was trying to get behind them, I was suddenly told I had abandoned the objective. I returned with the sheep, but didn't get the decree. I tried talking to the sheperd again, but the objective was immediately abandoned as soon as I took the request. Had to move on to the main Duviri bounty.