Jump to content

Nuanulla

PC Member
  • Posts

    93
  • Joined

  • Last visited

Everything posted by Nuanulla

  1. if I could kiss you, i would. Still too bad that Warframe can't dynamically switch whether if Steam Deck is in desktop mode or if in-game input method changes. But this is still much better than I'd expected at all.
  2. I know you exaggerated the wording of your reply as such out of frustration. However, no one can help you with such little and vague information. If you can’t diagnose your issue for other people and not just for yourself to understand, I’d question how important this issue is to you. And, given that all of our Steam Deck models are the same hardware-wise and that I’ve recently used a mouse and keyboard with Warframe (latest Warframe, Proton 8.0-4, latest stable SteamOS), there’s obviously something that you’ve missed. Instructions in the past few pages are comprehensive. They will assuredly work unless either your Deck has another broken component or you have messed with your Deck software or settings beyond a threshold.
  3. You probably forgot to force a proton version for the non-steam game shortcut.
  4. Has anyone managed to redirect the shader cache path as well? I'm playing around with this command, though it doesn't seem to work:
  5. I dunno what you guys are on about. If the new update broke the non-SIAPI workaround, there's something wrong on your end. Maybe the default Proton version changed for Warframe and your non-Steam game shortcut is no longer in sync in this regard. I'm still successfully playing Warframe on Deck with mouse and keyboard.
  6. If you're so concerned about new Deck users and your "shotgunning the response", you still haven't bothered to rectify your guide's deficiencies after I quote-replied to you. 1. Warframe SIAPI IS NOT a broken integration. SIAPI was and is still an intentional decision. If anything, it is the layout's Steam Input Action Set that's deficient, not "broken" per se. You're misleading people on this point. 2. Stop quoting "-cluster:public -registry:Steam". This is a Windows solution, and one of if not the first sources of this solution (that I found) intended it for Windows users. It certainly works on Deck but is not ideal. You're making users waste space by generating an unnecessary second prefix while simultaneously losing all of their in-game settings. If you aren't deleting your guide, you should instead, for the sake of primarily Steam forum users, 1) simplify and correct your guide; 2) link to ProtonDB; 3) link to this Warframe forum thread.
  7. Why would you post this here when there’s a better solution and simpler instruction on the second page?
  8. Hold STEAM button and press left-trigger to invoke mouse-right-click. This should help you exit out of narmer security cams and allow you to exit mission from menu. The issue at focus of this thread appears to be a 'gameplay bug', strictly speaking, whereas the issue we're experiencing is an 'input issue' that DE has yet to fix. You can workaround the issue by disallowing Warframe from using SIAPI.
  9. The key part to understand, which I've also mixed up until now, is that there are (let's say) two primary control methods for Warframe: There's SIAPI and non-SIAPI. Under the latter, we can also classify sub-groups as KB+M and Gamepad. In-game, Warframe is unable to dynamically switch between SIAPI and non-SIAPI. Meanwhile, it's capable of dynamically switching between KB+M and Gamepad (as evident with the changing UI icons) when under non-SIAPI. SIAPI locks the player into Gamepad SIAPI-input. Non-SIAPI processes KB+M and Gamepad x-input. The other confounding factor is that people are mixing up Steam Input and Steam Input API. These are two different things. For Warframe, Steam Input processes Gamepad input to provide either x-input, KB+M input, or SIAPI-input. Hence, the issue isn't that Warframe is locking the user into controller inputs; Warframe is locking the user into SIAPI inputs. Yep, you'd be correct here. In contrast to Windows, and as I noted in my first reply in this thread, "Steam Input" is set to "Always Required" on Deck. That's why, without the workaround, Warframe expects SIAPI universally (whether Game Mode or Desktop Mode) while Windows escapes this issue outside BPM. STEAM+X global chord does actually make the keyboard pop-up. But, as I clarified above, Warframe on Deck by default will be expecting SIAPI keyboard input rather than 'normal', non-SIAPI keyboard input. This inability to understand non-SIAPI input, and the inability to dynamically enable/disable SIAPI while in-game, is why everyone got stuck on the login screen when Valve messed up SIAPI with one of their recent Steam Deck stable channel updates. The mess-up with SIAPI recently was Valve's fault. However, if Warframe didn't lock us into SIAPI, it wouldn't be as big of an issue as it was. As a testament to the inconvenience of this issue, Warframe isn't processing my Deck inputs during a Narmer Break mission since DE has forgotten to map or connect any of the 'security cam' inputs to their Deck default controller layout 🤦‍♂️. DE's default layout, using Steam Input SIAPI, works well on Proton-8.0 when compared to past months with Proton-7.0. BUT, in such cases with SIAPI bugs on Warframe's end, users would never be completely stuck if DE allowed us to disable SIAPI in-game.
  10. Switch from Valve's chosen Proton-8.0-3 to Proton-7.0-6. If DE's Steam-Input controller layout still doesn't work, generic layout (ex. Controller with Mouse Trackpad) will work. Use STEAM + X to open the keyboard when your cursor is blinking inside the password input field. DE Deck layout worked yesterday with Proton-8.0-3, and all functions worked perfectly whether in or outside menu in contrast to my previous experiences with the DE layout on 7.0-6. A recent Warframe update must have made SIAPI worse than it already is.
×
×
  • Create New...