Sooo, I’m at a awkward point where I’m using both new input system and the old one.
I’m using new input system for “Feel”'s haptic feedback. And I’m using old input system for “Rewired”
The problem I met is, my game have multiple joystick on the same PC. And I couldn’t find a way to figure out which new input system’s gamepad with old input system’s gamepad. So I would often trigger the wrong vibration.
I couldn’t find the hardware Id for the new input system that would match the old system. Please Help.
Setting “Active Input Handling” to “Both” in the Player Settings will enable both to run side by side. Not supported on all platforms and not extensively tested/support but should generally work.
May I suggest an option where you can have “Active Input Handling” set to e.g. “Input System Package” for builds but “Both” for editor? I always find myself switching to “Both” mid-project because of Asset Store packages with examples or features we’re trying out, scripts from stackoverflow we drop in to quick-and-dirty test a prototype - so we need “Both” to have all these prototype features work correctly but then want “Input System” only for our final code. It’s just a bit annoying that if someone forgets to switch this before build, suddenly we have a useless system running in the background taking up CPU.
I have my “Active Input Handling” set to both but my EventSystem is complaining that the old InputManager is disabled, which it is not. Anyone have a fix for that? I’m on 2021.3.33f1
I’m using the new InputSystem for controller input and button binding in game, but my menus are all setup using older input scripts. If I hit that replace button then all of my mouse and keyboard input on my menus stop working. Just not something I want to chase around to find out what the issue is, and figured if Unity supported both I’d use it, but it looks like theres a few input related bugs around still.
Have you verified that the Standalone Input Module will in fact not work as it states? Because I seem to recall seeing a message like this in a previous project only for it to not actually matter at all.
It would be great if Unity enforced using #if defs for new assets that touch input to support both/either, so end users don’t need to resort to this because you’re right it’s annoying with so many assets. Or maybe they have a little Input utility by now?
