Before I make some full fledged feature requests I just want to make sure that I'm understanding how all of this gamepad stuff works so far and that I haven't missed anything:
Is there a command in the same vein as .options or .host (.gamepad?) that I can call to just open the "Gamepad Setup" window directly?
Am I forced to use the "Gamepad Setup" window to actually map buttons on the gamepad so that they're recognized by the Dream Seeker? Right now using the new "Any" key macro I can detect keyboard inputs, but it doesn't register gamepad button presses unless they've been mapped in this menu.
As it stands, Dream Seeker's built in process for setting up a gamepad and mapping controls strikes me as being very confusing for both developers and end-users alike. The difference between the "Gamepad Setup" and "Gamepad Mapping" menus isn't readily apparent; I've never played a game that required me to first map my gamepad buttons to internal pointers for each command, and then open a completely separate menu and map those pointers to the actual key presses that I want. Is there some sort of benefit in having this be this a two-step process that I'm missing?
At any rate, what I'd really like to be able to do is to completely avoid using both the "Gamepad Setup" and "Gamepad Mapping" menus and just create my own gamepad mapping system. As far as I can tell, all that I'd need in order to be able to do that is to be able to detect the raw button press outputs from the attached gamepad. Even if I was only able to detect the raw outputs temporarily (via some sort of special winset command), it would allow me to create my very own version of the "Gamepad Setup" menu.
Sep 27 2016, 2:14 am