Nuanulla
-
Posts
93 -
Joined
-
Last visited
Posts posted by Nuanulla
-
-
On 12/10/2023 at 9:21 AM, GothicRose_ said:
My L1 button broke and I don't know how and can't afford repairs rn (it's the Christmas season), I also just rather play with a keyboard and mouse too. I tried everything to get my keyboard and mouse to work on the game but nothing works.
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.
-
5 hours ago, Zeluno said:
Late to the party here, but
This doesn't seem to be working for me. I'd love maybe a step-by-step video or guide with images of @Nuanulla's method, if possible, but I understand if that is asking too much. Either way, when following the instructions outlined on page 2 of this thread/the linked Warframe thread, I'm simply not able to get WF to even launch. Could someone please help? Really miss playing with KBM. :(
You probably forgot to force a proton version for the non-steam game shortcut.
-
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:
QuoteSTEAM_COMPAT_SHADER_PATH="/home/deck/.local/share/Steam/steamapps/shadercache/230410" STEAM_COMPAT_DATA_PATH="/home/deck/.local/share/Steam/steamapps/compatdata/230410" %command% -cluster:public -registry:Steam
-
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.
-
10 hours ago, feralwolven said:
My bad i was shotgunning the response to some years old threads that were relevant. Didnt see this one had the solution i found. And those instructions are simpler yes, but i wanted to roll everything into one guide and many people ive encountered are new to steam with their steamdecks.
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.
-
1
-
-
On 2023-08-30 at 2:01 AM, feralwolven said:
its not a proton issue, and here is the workaround until DE fixes this https://steamcommunity.com/sharedfiles/filedetails/?id=3027980121
took me along time to figure this out so i must share it.Why would you post this here when there’s a better solution and simpler instruction on the second page?
-
On 2023-08-06 at 1:41 PM, PhysicsQuandry said:
I can confirm I just got this issue in Sneaky Sneak on Steam Deck (latest update on deck and game) with new default controls: upon interacting with the camera, no buttons other than pan controls work. Had to force quit the game through the Steam button, the only one that worked.
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.
-
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.
QuoteSteam Input is a service allowing Steam users to play any controller-supported game with the device of their choice. Steam Input will translates the user's input into something the game understands through either Gamepad Emulation, Mouse and Keyboard Emulation, or Steam Input API. [Source]
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.
QuoteI 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.
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.
-
3
-
-
4 hours ago, Wyvern69 said:
More specifically this is the problem:
On Proton 7 and below keyboard will not automatically prompt. Requires manual call. But at least custom controller layout still works.
Reverting to Proton experimental once again disables controller layout but now additionally causes any steam menu overlay including keyboard and home menu to be completely black. This only occurs after launching Warframe and no other game and persists even after the game is closed (I assume it's closed but honestly all I see is black so I have no idea).
Did you try Proton 8? Did you try just not forcing any compatibility layer?
-
@[DE]Taylor There’s a second temporary workaround: You can notify users that they may, for now, use any version of Proton 7.0 as Warframe correctly processes x-input with that Proton version (ex. Valve Proton 7.0-6, GE 7-55).
1. Open Warframe Steam Game’s Properties window
2. Go to “Compatibility” tab, Tick “Compatibility Layer” and select Proton 7.0-6
3. Open Warframe “Controller Settings”
4. Select Layout, scroll to Template tab, select “Gamepad with Mouse Trackpad”
Use STEAM + X to show keyboard when necessary. Hold STEAM button while using right-trackpad to use mouse and mouse left click when necessary.
The problem with your listed workaround is that, in certain cases, Warframe’s game elements may appear ‘widened’ or stretched horizontally while UI elements still appear as expected. This behavior appears in Windows handheld display (not on external display) and in Deck Desktop Mode. This behavior doesn’t appear in Game Mode.
-
2
-
-
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.
-
On 2023-03-07 at 3:17 PM, The1AndMany said:
- Your in-game settings will be reset to default. Easy enough to reconfigure them, but it's something to be aware of.
I don't have my Deck handy to check right now. But, I presume Warframe stores configs in plain text files locally, generating new files when old files are misplaced. On Steam Deck, due to presence of Proton prefixes, you might try adding the following launch option:
STEAM_COMPAT_DATA_PATH="/home/deck/.local/share/Steam/steamapps/compatdata/230410" %command%
Altogether, that's
STEAM_COMPAT_DATA_PATH="/home/deck/.local/share/Steam/steamapps/compatdata/230410" %command% -cluster:public -registry:Steam
Each individual game runs in its own Proton prefix. For non-Steam games, Steam auto generates a new proton prefix. Manually assigning the correct prefix to the game executable, now recognized as "non-Steam", should allow Warframe to find your original config files.
On 2023-03-23 at 4:51 AM, DatFruitBat said:Tried this but it doesn't run, is there something I'm missing?
Did you manually set a proton version under the "compatibility" tab?
-
1
-
Hate to break it to you all, but DE is unlikely to ever fix this issue. It's been an issue since the days when the Steam Controller was still in production. Besides the Steam Controller, there are numerous threads on this forum here and on Warframe's subreddit that bemoan input issues and DE's botched integration of Steam input. Further, full respect to all of DE's staff, but they've undoubtedly seen this and many other threads regarding this issue, and their silence and lack of transparency regarding improvement of game inputs can only mean this issue is not a priority at all no matter how inconvenient and non-standard/unusual this issue is.
This is only the tip of the iceberg on the quirkiness of DE's prioritization of game issues. Simple stuff like remembering passwords for login is missing despite this "feature" being present in various other games such as Valorant—and many players will be quick to glorify the developers, praising a supposed lack of "feature" as a feature in itself, thereby depriving themself of a better experience that outweighs "security."
But back on topic: if anyone is still searching for a way to play Warframe with KB+M whether it be on Steam Deck or elsewhere without interference from Warframe itself, see if this Reddit comment will help:
QuoteAdd Warframe.x64.exe as a non-Steam game and add -cluster:public -registry:Steam as the Launch Options for the shortcut. Rename this shortcut so you know that it's the non-SIAPI launch method.
-
2
-
-
On 2022-10-05 at 5:04 AM, Citan666 said:
Same. I was very happy to start back playing with my friends, but spending several tries first on login issue, then trying to play with gamepad both ended as big disappointement. Even missed the free Warframe because of that (didn't try to play during that event).
Please DE put resolving this issue as a priority, I mean, I'm pretty sure I'm not the only one that (would) love playing Warframe but cannot appreciate any because in spite of your best efforts for people used to TPS/FPS on computer keyboard + mouse is still king.
I really hope it's fixed before my friends finish completing all content they had missed since 2 years ago, since they grind hard it won't take them long now. xd
JIC you can use an external BT controller and set layout as using one of Valve's default controller templates. Warframe's default template doesn't work because it uses 'joystick mouse' rather than 'controller joystick' for said joysticks, which messes with sensitivity for the game. The template also omits many benefits of using the controller, such as d-pad menu navigation. Basically, just use Valve's default gamepad template, and Warframe should be 100% playable.
-
1
-
-
For all still following, the linked Reddit post may be your solution. I haven’t tested it yet myself for Warframe. Note that there are two links which should already be sufficiently described in the post. The first link should theoretically work based on my response above. The disabled on-board controller should then no longer allow the game itself to interfere with kb+m controls. The second link automates the process.
-
I have this issue as well. After searching around the forums, it seems to be a result of an issue a couple years old where the game locks-in to controller-mode if a controller is detected on game start. Unlike many other games, Warframe doesn’t allow you to switch between input types on the fly (beyond changing cursor type to mouse). So, if you want to use kb+m, the only solution is to start the game without a controller attached.
But, take a look inside the game’s properties in desktop mode and you’ll notice that “Steam Input” is set to “always required.” Further, the on-board controller can’t be “disconnected” due to the wired or built-in state. So we can probably conclude on why the issue occurs, but not how to fix it.
-
1
-
-
Did anyone else lose all their codex scans and thus can't properly use the simulacrum now?
(also, all my junctions have been undone)
-
On an economic standpoint, releasing Excal Prime would probably make DE lose money rather than earn more or even earn less.
-
This has been fixed already
-
The default idle animation for operators is to sorta "look back". This is 'it' doing it in the transmission, which is definitely a bug.
-
Argon Scope
-
Same here. No colors but I can scan though.
I just can't figure out what I've scanned and havn't scanned now when in a mission.
-
My condolences.
-
1 minute ago, Nekothika said:
spam ? you serious ? I have ideas, i post them in appropriate section ... should I shut my mouth or ... my fingers ?
Okay okay. I just personally would consolidate all 6 posts into one thread within Feedback\General.
But I won't blame you since I'm not in charge here.
Steam Deck + Keyboard and Mouse
in UI
Posted · Edited by Nuanulla
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.