Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Simultaneaous Controller+Keyboard/Mouse (Mixed Input) support #12

Open
AL2009man opened this issue Jan 19, 2024 · 2 comments

Comments

@AL2009man
Copy link

AL2009man commented Jan 19, 2024

To give an bit of context, and this will be copy-pasted from the REFramework issue report:

Simultaneously Controller+Keyboard/Mouse, Mixed Input (or Hybrid Input for newer Ubisoft gaames) for short, is a Input Method that enables users to use the Gamepad and Keyboard/Mouse Inputs at the same time. Typically: this is used for something like Gyro Aiming (most Controllers like PlayStation and Nintendo Switch), Tracking Aiming (for Steam Controller or Steam Deck, in combination with Gyro or not), Gaming Keypads (Azeron, Razer), Analog Keyboard (Wooting Keyboard), physically using Gamepad and Mouse device, etc. You could say this is an Accessibility-related request.

for simplification's sake: I will be referring to "Mixed Input" going forward.

Normally, this method will/may introduce issues such as:

  • Controller/KB+M Button prompt flickers.
  • Mouse and Joystick Camera Input fights with each other.
  • Locks you to One Input Method
  • Joystick Camera Input starts to behave erratically.
  • Certain gameplay/UI elements (example: key gameplay functions like Sprinting and Interacting is broken in Metro Exodus, KB/M and Controller-specific UI behaves erratically in Sunset Overdrive)
  • Input Method's entire Aiming mechanic changes (in the case with Resident Evil 5)
  • quick off-topic: It's rare to find a game that allows you to use Mixed Input without conflict

For more detail; refer to this cohost post by Jibb Smart (Epic Games/Fortnite Dev, JoyShockMapper creator) in regards to Mixed Input.

Got it? ok, let's resume.

According to PCGamingWiki: Max Payne 3 seems to have mixed Input support, but when I finally got the chance to play Max Payne 3 (with the Fusion Mod 2.0, and thanks for providing Steam Deck prompts!), I've found at least four (thus far) specific issues that causes nuisances:

1. Gamepad button prompts flicker

Whenever you attempt to use Controller and Keyboard/Mouse inputs together: the Controller prompts will take priority over the KB/M inputs, but when you stop using the controller, the keyboard/mouse prompts will be in-use. Thankfully; there isn't any major QTE sequences, but for those who wanna play Max Payne 3 with Gyro Aiming functionality for the first time; it might be annoying to deal with the tutorial sequence.

2. Joystick Camera and Mouse Input will conflict with each other

similar to the first issue, but the camera inputs starts to conflict with each other. The current workaround is to rely on a Input Remapper (like Steam Input) and rebind the Right Stick as a Mouse Input.

8mb.video-0bW-E2KeUPjF.mp4

(due to file size limitations, here's an higher quality version)

3. Certain actions may not work due to conflictions

To continue from Issue number 2, certain actions like the Pause button or Dodge action (Keyboard only) may not work properly.

the most obvious example would be the Aiming Camera, as it will just freezes (despite the character's camera animation) whenever you stop moving (with the Left Stick aka whenever the Gamepad isn't active). thankfully, this doesn't happen for regular camera movement.

8mb.video-ZT3-dPdYbYWo.mp4

(due to file size limitations, here's an higher quality version)

4. Despite FreeAim mode: Target assist still kicks-in.

Max Payne 3 provides both Aim Assist modes: Soft Lock and Hard Lock, with additional toggles for both Target Tracking and Target Slowdown.

However, if using Bullet Time (I think it's distance-based?) or Shootdodge while using the controller: the Aim Assist system is still going to be active and will try to pull you in. I'll call it: "Bullet Time Assist".

This seems to happen whenever you use the Left Stick Movement. For Shootdodge: the easy workaround would be to let go the Left Stick Move after performing a Shootdodge.

unfortunately: I have no idea if Hardcore Free Aim mode is also affected by the hidden "Bullet Time Aim Assist" while Shootdodging, and I only have access to it on Multiplayer.

Update 1/22/2024: I can also confirmed that Explosion-based weapons like Grenade Launcher still has a far more aggressive Aim Tracking, despite having it turn off.


Within those reasons; I wonder if it's there's an way to make RAGE Engine to play nicely with Mixed Input? 🤔

While I don't have access to the rest of RAGE Engine-based games (specifically: GTAIV), I have heard words from others that it seems to affect other RAGE-based games too. in context of the FusionFixs: I'm doubting that GTAIV will also have this issue.

@RecklessGlue540
Copy link

RecklessGlue540 commented Jan 19, 2024

These conflictions could be caused by Steam Input.
For me at least, Steam Input does not work with non-Steam apps. I've got these same conflicts (the prompts flicker and the controller right joystick acts like a mouse in some form)...

If you have the game bought from RGL, you might just have to live with the game's native controller implementation... Although in my opinion, Steam Deck should behave different since it's SteamOS...

@AL2009man
Copy link
Author

AL2009man commented Jan 19, 2024

These conflictions could be caused by Steam Input. For me at least, Steam Input does not work with non-Steam apps. I've got these same conflicts (the prompts flicker and the controller right joystick acts like a mouse in some form)...

I've checked using my Xbox One Controller (Wired) and a Physical Mouse while disabling Steam Input completely. The same issue still occurs.


1/21/2024 Edit: to be more specific: the issues I've highlighted is not the result of Steam Input itself...as it can also be easily replicated by just using an Standard Gamepad and an Physical Mouse.

If you have the game bought from RGL, you might just have to live with the game's native controller implementation... Although in my opinion, Steam Deck should behave different since it's SteamOS...

it doesn't matter which version of Max Payne 3 you bought on a PC Storefront; when you just use a Input Remapper (think DS4Windows or JoyShockMapper) that does the same/similar thing Steam Input does, but I'll guarantee you that the same problem will occur on these third-party software regardless.

It's extremely rare to find a game's input system caused by Steam Input (usually: it's the Unity-powered games using the older Input System), and Max Payne 3 predates Steam Input and Steam Controller by 4 years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants