The architecture stack should be like this if possible: Game Controller -> My App -> Game/Application and Game/Application -> My App -> Game Controller. Cause currently the inputs are doubled.

Hi Justin, we're trying to allow for more support for primarily the DualSense controllers. One core feature that's already implemented in our Windows version is controller emulation. We allow for the DualSense to pretend to be a DualShock or Xbox controller for more capability with older and unsupported games. On Windows, we use low-level APIs such as HIDHide to hide the DualSense from the system, use the Windows equivalent of IOKit to grab exclusive access to it, and then Windows’s virtual controller framework to create a virtual controller that games see. Unfortunately, even with a custom DriverKit, we would be unable to feed the controller data exclusively or hide the controller from the Game Controller framework as it is too low-level and inaccessible for developers. And macOS simply does not currently have a virtual controller framework. If Apple were to add those features, we would love to update our app to feature these improvements. David

Interestingly System Settings is able to control how the Game Controller framework maps buttons through the Game Controller tab on MacOS. If Apple could at least expose those for developers it would allow us to do so much more. The best would be the ability to fake controller via VID:PID as on Windows.

The only thing we've been able to do is allow user to map controller buttons to keyboard and mouse and allowing them to use their controller in games that don't support controller input. But since we can't hide the controller from games that support controller input this feature can only work on games that don't support controller or can disable them.

Ok I've submitted a suggestion via Feedback Assist.

The feedback number is FB21643623. Thanks Quinn the Eskimo.