(06-28-2014, 03:07 PM)jhebbel Wrote: The app fully supports hot-plugging and you can already do that, its just not all games do, and that has nothing to do with us.
i guess my question was not understood, or maybe i don't understand something. so i'll walk through this again, this time without conjuring up words like hot-plugging, because apparently i don't know what that means.
so i go to play assassin's creed, lets say AC2, but i have the ds4tool running, it has an icon in the taskbar, so i know its good. i start the game and pick up the controller and oh no! its not on. i turn it on. but too late the game has already started and did not find the controller, and starting the controller, while it does put it in the right profile for the game, the game itself still wont find the controller until i restart the game, and this particular title will further punish me for not having the controller in last start by forcing me to use the keyboard to go into the settings so i can change the controller.
now what im asking is if i have the ds4tool running, why can't i have a option to have the xbox controller always on, and when the system finds the playstation controller the ds4tool could then simply map it to the xbox copntroller? lets review the above scenario again in that circumstance.
so i go to play assassin's creed, lets say AC2, but i have the ds4tool running, it has an icon in the taskbar, so i know its good. i start the game and pick up the controller and oh no! its not on. i turn it on. i navigate the game normally with the controller, even though the controller was started after the game.
is that understandable? not hot-plugging? what is it then cold-plugging? whatever the term, in this scenario (i'll quote my previous post) "would it be desirable to map an empty controller to the xbox controller so that it is always there?"