Ryochan7
Future Request: Support for XBOX Series Controller
I have tried InputMapper, JoyToKey and AntiMicro but they nowhere near the capabilities of DS4Windows. I have used the trial on reWASD and even though its close to being as good as DS4Windows it falls sorts when it comes to macros and it costs 14$. I would love to the XBOX series controller working with DS4Windows!
Except for DS4Windows being able to map to a virtual controller, I would say that AntiMicro is more capable for many tasks than DS4Windows is; I was the original developer for AntiMicro. Anyway, support for Xbox controllers will likely never happen in DS4Windows or any future mapper I put out. The main problem is hiding the real Xbox controller from the system so double input cannot occur in games. HidHide tries to do it but it only seems to be able to hide the DirectInput interface while leaving the XInput interface open.
I have never tried it but I would assume it is possible since reWASD can supposedly hide Xbox controllers from the system. I still have a semi-functional Xbox 360 controller in my closet; the cable connection is very loose so it is easy for the controller to disconnect.
HidHide actually can fully hide Xbox controllers if manually doing so through HidHide CLI
The issue with HidHide failing to hide Xbox controllers is not in the driver but with the HidHide Configuration Client.
Still, yeah, having to manually go through the process of getting the device instances of interest every time one wants to hide Xbox controllers is tiresome
Except for DS4Windows being able to map to a virtual controller, I would say that AntiMicro is more capable for many tasks than DS4Windows is; I was the original developer for AntiMicro. Anyway, support for Xbox controllers will likely never happen in DS4Windows or any future mapper I put out. The main problem is hiding the real Xbox controller from the system so double input cannot occur in games. HidHide tries to do it but it only seems to be able to hide the DirectInput interface while leaving the XInput interface open.
I have never tried it but I would assume it is possible since reWASD can supposedly hide Xbox controllers from the system. I still have a semi-functional Xbox 360 controller in my closet; the cable connection is very loose so it is easy for the controller to disconnect.
Since you are the original developer of AntiMicro can you tell how this DS4W macro would be written in AntiMicro's macro section?
HidHide actually can fully hide Xbox controllers if manually doing so through HidHide CLI
The issue with HidHide failing to hide Xbox controllers is not in the driver but with the HidHide Configuration Client.
Still, yeah, having to manually go through the process of getting the device instances of interest every time one wants to hide Xbox controllers is tiresome
So its actually possible to hide an XBOX controller and then mask it as DS4 through some emulator ?
So if hiding is the only issue i would love to see get xbox gamepad support implemented. Iam a user of reWASD - which is a great alternative btw - for my xbox elite pad. Although reWASD is quite powerful, its feels not as smooth as DS4 - at least if i compare DS4 and reWASD with the ps5 edge attached. Plus it feels somehow bloated in comparison with DS4 Plus: Its not open source ..
So if hiding is the only issue i would love to see get xbox gamepad support implemented. Iam a user of reWASD - which is a great alternative btw - for my xbox elite pad. Although reWASD is quite powerful, its feels not as smooth as DS4 - at least if i compare DS4 and reWASD with the ps5 edge attached. Plus it feels somehow bloated in comparison with DS4 Plus: Its not open source ..
Since I made this post I moved on to AntiMicroX and I think it runs even smoother than DS4 which is already smoother than reWASD. When I want to execute the same macro multiple times, sometimes DS4W overlaps a little while no such issues occur with AntiMicroX. The only problem is the interface not being very user friendly, writting macros is harder for beginners but once you get the hang of it its wonderful.
AntimikroX is more about remapping buttons i might think. DS4 has heavily required features like adjusting dead zone, special actions, lightbar configuration, gyo, and so on
The initial intent of Antimicro was to have an Xpadder substitute for Linux for playing some games in Wine. Mass Effect 1 (2007) was a primary test case in the beginning of that project. Without action sets and some special actions (hold actions primarily), trying to play Mass Effect emulating KB+M would be virtually impossible.
The main focus with DS4Windows has mainly been to attempt to add more controller mapping functionality without adding major input latency in the process. For the most part, it has worked out but trying to fight the .NET Runtime has caused some unnecessary headaches and slowed down development more than it should. Current DS4Windows is still faster than the last Jays2Kings build of DS4Windows even though that build was my preferred option back in 2017. The macro system in DS4Windows has always been considered in maintenance mode as it has some major design problems that I do not want to deal with. The system would probably need a major rewrite to add any major functionality to it and it would not benefit me at all.
Since you are the original developer of AntiMicro can you tell how this DS4W macro would be written in AntiMicro's macro section?
Looking back at a portable build of Antimicro. Looking at the slot assignment windows, it does not look like there would be a way to pull that off. The wait times could be specified using the Press Time slot type or using some Pause slots. However, there is no specific KeyUp or KeyDown slot type so you would not be able to release the S key without releasing the A key as well; those keys would be considered part of the same slots partition. I do not know if AntimicroX would have changed the KB/M slot type to include different behavior for KeyUp or KeyDown only events. It should be doable without much work.
@Ryochan7 - Might there be a chance of implementing support für xbox controllers in any case?
The initial intent of Antimicro was to have an Xpadder substitute for Linux for playing some games in Wine. Mass Effect 1 (2007) was a primary test case in the beginning of that project. Without action sets and some special actions (hold actions primarily), trying to play Mass Effect emulating KB+M would be virtually impossible.
The main focus with DS4Windows has mainly been to attempt to add more controller mapping functionality without adding major input latency in the process. For the most part, it has worked out but trying to fight the .NET Runtime has caused some unnecessary headaches and slowed down development more than it should. Current DS4Windows is still faster than the last Jays2Kings build of DS4Windows even though that build was my preferred option back in 2017. The macro system in DS4Windows has always been considered in maintenance mode as it has some major design problems that I do not want to deal with. The system would probably need a major rewrite to add any major functionality to it and it would not benefit me at all.
Since you are the original developer of AntiMicro can you tell how this DS4W macro would be written in AntiMicro's macro section?
Looking back at a portable build of Antimicro. Looking at the slot assignment windows, it does not look like there would be a way to pull that off. The wait times could be specified using the Press Time slot type or using some Pause slots. However, there is no specific KeyUp or KeyDown slot type so you would not be able to release the S key without releasing the A key as well; those keys would be considered part of the same slots partition. I do not know if AntimicroX would have changed the KB/M slot type to include different behavior for KeyUp or KeyDown only events. It should be doable without much work.
Thanks for the answer mate, I already figured out how to replicate the Macro, you just have to go input by input using press time and pause, AntiMicroX might be powerful but isn't very new user friendly.
@Ryochan7 - Might there be a chance of implementing support für xbox controllers in any case?
I would like to know about It as well. I'm using moonlight and it send to the host a x360 virtual joystick, If DS4Windows could recognize that joystick I could change It to a DS4 joystick.
That reaource will be really usefull for me if be implemented.
Talking about hide or unhide the joysticks using hidhide, it's really possible by command line, I even wrote a short script to do it and it works, if you want know more about it, please text me.
I really hope to support XBOX. Now I use the custom adjusted curve and it can no longer adapt to other curves.
