#INCONTROL UNITY A B X Y UPDATE#

Some controllers/buttons do not have a held down state so it will only return true for the one frame in which it was pressed. You can query: InputManager.MenuWasPressed, though, which maps onto whatever roughly applicable buttons can be found. You should not be using these buttons in a generalized cross-platform capacity. Some controller specific buttons (like Start, Select, Back, OUYA, Xbox Guide, PS3, etc.) are not part of the standardized set of supported inputs simply because they do not work on every platform.The Native Input module circumvents this problem entirely. Thus InControl has no choice but to fire DeviceDetached events for ALL controllers and then fire DeviceAttached events for those remaining. When multiple controllers with the same name are used and one is detached, Unity does not report which one was detached.Every platform does, however, report all newly connected devices once the app is relaunched. If Unity's Input.GetJoystickNames() is updated by the platform while the app is running, it will work. Not all platforms trigger the DeviceAttached event correctly.

#INCONTROL UNITY A B X Y UPDATE#

There is no expectation of a fix or workaround in most cases unless a driver update happens to address it. This list is an attempt to enumerate some of the more glaring or quirky issues encountered, but these are not bugs, at least not in InControl. Other than Apple’s MFi controller specification, there is no standard for how controllers should work, or what controls they should have and how those behave. Sometimes they work partially or not at all. Every controller seems to behave slightly different on every platform. If you know anything about controllers and cross-platform support, you know that finding consistent, functional behavior is a fool’s errand.

Incontrol unity a b x y