Jump to content

Field for simultaneous controller/mouse support?


Recommended Posts

Topic title.

 

I think it would be useful info, namely for those who have a Steam Controller and want to know if the support is there. Like for example, Rainbow Six Vegas doesn't allow the use of a controller and mouse at the same time but Half-Life 2 does. It would be nice to know if this is something that could be considered.

Link to post
Share on other sites

That could be a useful addition under additional information, but I don't know what description would work best.

 

The Hot Plugging field is for that, I think.

 

Hotplugging simply means the game will see a controller if one is connected after the game is already running. This is not the same as being able to use both together (and many games that support hotplugging do not support using both together, e.g. Bethesda's last few RPGs will disable most keyboard functions when controller support is active).

Link to post
Share on other sites
  • 2 weeks later...

I personally haven't been a fan of mixing the controller and keyboard/mouse when using steam controller, mainly because majority of games haven't been designed that way and drawbacks of not mixing are really minor, but I can see that it would be neat info to have for those who do mix them.

 

When I have been editing game articles, I only mention this if switching between methods requires some significant effort, e.g. needing to manually switch the method of input or even restart the game. I would almost say that noting under hotplugging should suffice, even if this isn't exactly hotplugging, it's still meaning switching to use controller while the game is running. 

Link to post
Share on other sites

Either way, this capability should not be noted under hotplugging unless it is actually applicable (hotplugging is a separate feature, but there might be a few games that support simultaneous input only if started with a particular control arrangement).

Link to post
Share on other sites

I was thinking aboout adding an "exclusive" state to the controller support propriety, but considering it's supposed to be about the state of controller support rather than the extent of it, a new propriety might be in order. How about "Hybrid controller support" or something similar?

 

EDIT : Come to think about it, there are a few proprieties related to Steam Controller compatibility that might be worth adding, like Native Steam controller bindings (The way XCOM2 and TF2 currently do it).

Link to post
Share on other sites

I was thinking aboout adding an "exclusive" state to the controller support propriety, but considering it's supposed to be about the state of controller support rather than the extent of it, a new propriety might be in order. How about "Hybrid controller support" or something similar?

 

EDIT : Come to think about it, there are a few proprieties related to Steam Controller compatibility that might be worth adding, like Native Steam controller bindings (The way XCOM2 and TF2 currently do it).

Input method switching may sound bit better as hybrid controller sounds like suggesting of multiple controllers usage. However switching would make games that require manual switching of controller to be true on table, which doesn't serve the purpose of using them simultaneously. Automatic input method switch? New field would also make it easier to note if game starts to change prompts at seizure level because of two differend inputs. 

 

Native bindings will be pain to do, especially when majoritys native bindings are basically slamming buttons as regular XInput controller and calling it a day without any testing or optimization for better controls. 

 

As for native support, which includes use of haptic feedback and button prompts, I did suggest including steam controller icons in prompt field, but apparently they are too similar to xbox ones and my made images were never accepted - not even as placeholders. So the "native support" section was my temporary solution to at least list the games. 

 

E: Also Xcom 2 support does seem more like marketing than native support. I do not own the game so can't test but as far as I have seen game still uses mouse and keyboard designed interface meaning also no steam controller prompts and haven't heard anyone saying anything about haptic feedback. I actually really love the haptic feedback from guns in CS:GO. 

Link to post
Share on other sites

Input method switching may sound bit better as hybrid controller sounds like suggesting of multiple controllers usage. However switching would make games that require manual switching of controller to be true on table, which doesn't serve the purpose of using them simultaneously. Automatic input method switch? New field would also make it easier to note if game starts to change prompts at seizure level because of two differend inputs. 

Now that you mention it, I think "Dynamic input selection/switching" is most fitting, since that's what most games actually do. In Bioshock Infinite, for instance, the game appears to technically have distinct keyboard-controller modes, but can receive input from both methods simultaneously (even though that messes with the prompts, as you just mentionned).

 

 

Native bindings will be pain to do, especially when majoritys native bindings are basically slamming buttons as regular XInput controller and calling it a day without any testing or optimization for better controls.

 

E: Also Xcom 2 support does seem more like marketing than native support. I do not own the game so can't test but as far as I have seen game still uses mouse and keyboard designed interface meaning also no steam controller prompts and haven't heard anyone saying anything about haptic feedback. I actually really love the haptic feedback from guns in CS:GO.

 

No, native bindings are precisely there so the steam controller doesn't have to emulate other input methods, and instead just communicate with steam controller-specific hooks in order to trigger in-game actions. While XCOM 2's interface still relies on mouse-control, actual mouse control is kept separate from scrolling, which can be done either via edge-scroll or by binding scrolling to the left trackpad. The game switches action sets on its own, with 3 different sets of actions and mappings depending on whether you're in the menus, on the strategic mac or on the tactical map and you don'T need to configure any of the keyboard and controller bindings in game for any of this to work, just like on other games with native support.

 

 

As for native support, which includes use of haptic feedback and button prompts, I did suggest including steam controller icons in prompt field, but apparently they are too similar to xbox ones and my made images were never accepted - not even as placeholders. So the "native support" section was my temporary solution to at least list the games. 

What you're describing here is native controller support, which is a valid thing to look for when judging a game, but ultimately unrelated to the SC (or at least, not exclusively).

Link to post
Share on other sites

Wait a minute gentlemen.

"Dynamic selection/switching" is surely a nice wording.

 

But why has there to be a selection/switch in the first place?

For everything I think, perfection would be just not caring (or if any, having a switch to turn the whole thing off like in source games).

 

For the records, analog keyboards are now a thing. Yes, sometimes I wonder if science tech has gone too far.

Link to post
Share on other sites

But why has there to be a selection/switch in the first place?

For everything I think, perfection would be just not caring (or if any, having a switch to turn the whole thing off like in source games).

Well that's why we are talking about this. Because the best case scenario is that game itself automatically switches it according to control method in use so that user doesn't have to care. But this is PC gaming, so that's not the case with many titles sadly. 

Link to post
Share on other sites

the best case scenario is that game itself automatically switches ...

Again, I don't see why a switch has to exist.

What's the matter with just accepting whatever input is sent?

Link to post
Share on other sites

Again, I don't see why a switch has to exist.

What's the matter with just accepting whatever input is sent?

Because when I try the game with the controller, I most certainly would not like to see keyboard promts give to me or not have any acceleration, smoothing or aim-assist on when aiming with bloody sticks. 

 

Maybe we are thinking it in the same way but you just aren't seeing it as switching. Basically the best goal is that the game just takes the input from the device you are actually using and you can just use whatever without need for settings menu or restarting. Thing is that for best user experience, game still has to change settings according to what is being used, most noticeable is the prompts given (which ironically most likely screws the steam controller if mixing inputs).

Link to post
Share on other sites

I most certainly would not like to see keyboard promts give to me or not have any acceleration, smoothing or aim-assist on when aiming with bloody sticks.

Uh, right points.

 

Maybe we are thinking it in the same way but you just aren't seeing it as switching.

Actually, I was writing "best scenario should switch on the fly.." when I realized I used the word "switch".

 

Though, now I'm thinking to those games with nothing similar (acceleration, prompts and aim assist are simply fixed) and.. what's there to make this switch noticeable?

Also: should we introduce a row for "game has controller aids"?

Link to post
Share on other sites

Uh, right points.

 

Actually, I was writing "best scenario should switch on the fly.." when I realized I used the word "switch".

 

Though, now I'm thinking to those games with nothing similar (acceleration, prompts and aim assist are simply fixed) and.. what's there to make this switch noticeable?

Also: should we introduce a row for "game has controller aids"?

You're right, though, that kind of wording would imply that the game has distinct "keyboard mode" and "controller mode" under the hood, which is not only beyond what the end user can or should know, it's also not the case for all games, which only treat it as an additionnal input method, so "switching" is hardly the best way to put it.

 

Really, all we need to convey is that using a controller doesn't disable the mouse and/or keyboard like it would in, say, Fallout 3/NV/4 or Skyrim and word it so "yes" is a positive awnser to that.

 

"Non-exclusive controller input", perhaps?

Link to post
Share on other sites
  • Found PCGamingWiki useful? Please consider making a Donation or visiting our Patreon.
  • Similar Content

    • By stepdaddy
      Configuration files for x360ce to enable support for Xbox One controllers in Assassin's Creed Director's Cut and Assassin's Creed II, including vibration.
      This is a more up-to-date version of the AC1 and 2 fix that improves compatibility with the latest build of x360ce (3.2.10.82) and Xbox One controllers.
      To install simply download and extract the contents of the zip file into the game's installation folder.
      x360ce is not required for the fix to function but is useful should you wish to make any configuration changes. Download the 32-bit (x86) version here and extract it to the same location as the other two files.
      Known issues: Fix does not support simulatenous trigger inputs. To workaround this issue disable "hold to lock" in the game's options menu (disabled by default). This issue only affects AC1 as AC2 does not appear to support "hold to lock" on PC.
      AC1-2-Xbox-One-Controller-Fix.zip
    • By Dandelion Sprout
      Currently, https://www.pcgamingwiki.com/wiki/Template:Infobox_controller seems a bit limited in its scope, and I have two proposals for additional properties to add to it, since I presume I lack editing rights for that infobox:
      1) Connection method. Whether a controller can be connected to PC by one or more of these:
      • USB (e.g. Logitech Gamepad F310, DualShock 3)
      • Bluetooth (e.g. Wii Remote, Xbox One Controller)
      • Wi-Fi (e.g. Nintendo DS, Amazon Fire TV Game Controller)
      • Custom port that require an adapter (e.g. GameCube controller, DualShock 2)
      Additionally, if it's desired, the USB category can be divided into:
      • USB-Mini (e.g. DualShock 3)
      • USB-Micro (e.g. Xbox One Controller)
      • USB-C (e.g. Switch Pro Controller)
      • USB non-Bluetooth dongle (e.g. Xbox 360 Controller's wireless revision)
      • Soldered USB-A (e.g. Trust GXT 540)
      I am not 100% sure how to handle controllers whose revisions have different connection methods. For instance, Xbox 360 Controller has two revisions; one with soldered, and one with USB dongle.
      2) Haptic feedback. Whether a controller has a rumble engine within it or not.
    • By Jigen123
      Uploading here because the author's website no longer exists.
      Original readme:
      Updated Version for Patch 01 1. Make a Backup of "need for speed shift 2\PakFiles\BOOTFLOW.bff" 2. Replace it with "BOOTFLOW.bff" from this zip file made by Garcias-Garage.de  
    • By Hman360
      This is an AntiMicro profile for the Spider-Man 2002 movie PC game for mapping the inputs that the game won't register in an XInput controller to the keyboard & mouse controls.
      You can import it into AntiMicro and set it to autorun with the SpiderMan.exe file in AntiMicro's settings.
      Specifically, the mappings are as defined below:
      Right Stick -> Mouse (default - camera)
      LT -> Shift (default - web action & recenter camera)
      RT -> Numpad 5 (default - web swing)
      The other inputs should be configurable in the game's gamepad settings, except the Left Stick which automatically is set to movement.
    • By Osprey
      Tomb Raider Mouse Helper
      v1.2
      for Tomb Raider 1-5 (1996-2000) by Core Design
       
      This Windows utility for the first five Tomb Raider games (I, II, III, The Last Revelation and Chronicles) runs in the background and provides mouse control in those games by converting mouse movements into key presses. This allows you to move the mouse to turn left and right and, while holding the right mouse button, look all around. It also enables firing with the left button, drawing weapons with the middle button and easily setting up WASD or ESDF control schemes.
       
      Features:
      Move the mouse to turn left and right (also can be used to rotate menus). Press and hold the right mouse button to look around (without moving). Press the left mouse button to fire and grab ledges (also can be used to select from menus). Press the middle mouse button to draw (and re-holster) weapons. Use the WASD (or any) keys to run, go backward and sidestep left and right. Scroll the mouse wheel or press left/right on it to rotate menus.  
      Instructions:
      Simply run TombRaiderMouseHelper.exe and then run the game.
      (Optional) Create a shortcut that will run the helper and game together:
      Click on the "Create shortcut" button on the helper's main window. Drag and drop either the game's shortcut or its .exe file onto the next window. (This will create a new shortcut that runs the helper, then the game, then exits the helper when the game exits)  
      Configuration:
      There are a few options that you can configure on first run, via the tray icon or via in-game hotkeys:
       Whether to minimize the GUI to the tray on launch. Default: Off. Applies only to running the helper by itself, not via shortcut. Toggle on to launch the helper silently to the tray.  Whether to exit when the game exits. Default: On. Applies only to running the helper by itself, not via shortcut. Toggle off to leave the helper running.  The sensitivity of the mouse. Default: the middle mark. It's recommended that you don't adjust this unless you find that you really need to. Whether to invert the mouse's Y axis. Default: On (because the game defaults to that) Toggle off to make panning up look up and down look down. Apples only to Look mode (holding the right button).  Whether to map keys to movement controls and other actions. Default: On. Toggle off or edit if any of the mappings are unwanted.  
      Notes:
      If the game is run as administrator, the helper must also be run as administrator in order to work. If you created a desktop shortcut from the helper's menu, then try running the shortcut as an administrator. All features will work as expected only if the game is configured to use the default keys. That's because this helper maps buttons and keys to those specific keys. For example, the left mouse button is mapped to the Ctrl key, which is the default key for Fire. If you change Fire to be a different key, then the left mouse button will stop working until you assign the Ctrl key to something else. If you want to disable these mappings, you can do so in the helper's menu. For example, if you've already configured the game to use WASD (or you prefer ESDF), you'll want to disable the WASD mappings. This helper works with the original DOS version of the first game (Tomb Raider I), but works better with the Windows version, which you can convert the DOS version to with the following instructions: https://pcgamingwiki.com/wiki/Tomb_Raider_(1996)#Run_the_game_without_DOSBox  
      Modification:
      This utility is simply a compiled AutoHotkey script.
      If you're not satisfied with the given mappings or functionality and would like to tweak them, the source script (TombRaiderMouseHelper.ahk) is in the "src" folder. You will need to download AutoHotkey from www.autohotkey.com to compile it. In the folder where you installed/extracted AutoHotkey will be a "Compiler" folder. In there is Ahk2Exe.exe, which you can use to compile your modified TombRaiderMouseHelper.ahk into a new TombRaiderMouseHelper.exe. An icon for you to use is in the folder with TombRaiderMouseHelper.ahk.
      You don't need to compile or worry about TombRaiderMouseHelperGUI.ahk (which mostly has code related to the GUI, not the game). It'll be included automatically when TombRaiderMouseHelper.ahk is compiled.
      For help with using AutoHotkey, see the help file (AutoHotkey.chm) that comes with it.
       
      Other:
      If you like this utility, you may be interested in these related uploads...
      SkyNET Mouse Helper: https://community.pcgamingwiki.com/files/file/982-skynet-mouse-helper/
      Outlaws Mouse Helper: https://community.pcgamingwiki.com/files/file/970-outlaws-mouse-helper/
      Dune II Mouse Helper: https://community.pcgamingwiki.com/files/file/955-dune-ii-mouse-helper/
      Warcraft Mouse Helper: https://community.pcgamingwiki.com/files/file/954-warcraft-mouse-helper/
      All (and any newer) uploads: https://community.pcgamingwiki.com/profile/3342-osprey/content/?type=downloads_file
       
  • Who's Online   1 Member, 0 Anonymous, 391 Guests (See full list)

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Forum Statistics

    1,491
    Total Topics
    8,074
    Total Posts
×
×
  • Create New...