![]() Also on the Turbo setting I'm not sure if it makes every button faster but I definitely notice L1/R1 Being faster and my paddles (Official Sony Back Button Attatchment). I made 2 videos describing my settings on DS4Windows and Antimicro on my channel "ImABot" on Youtube. You can tell the difference on the analog sticks especially the right one! Its so smooth! Try it for yourself. As far as the "Current axis detection deadzone" setting, I cant really explain what it does to the controller but its definitely a major change switching from 20000 to 8000. Wow thanks for the detailed response, and thank you dearly for all your hard work on this project! I don't understand everything that you said, but I get most of it. It is a matter of refactoring and trying to fit those routines in the current DS4Windows mapping code. There are features that are available in Antimicro that I would like to have back in some capacity vmulti support would be a feature that I would really like to have again. The Qt threading and event model was heavily abused with that project and there is no equivalent that I have seen for. I look back at my old code in shame with the amount of spaghetti code that I wrote to get certain features working. Not sure how I feel about people still using Antimicro I have not used it myself since around 2018. When mapping against a DS4, using even lower values for the dead zone would feel better although I cannot think of what values felt good to me during testing. When mapping a stick to Mouse, I would usually use a lower dead zone value around 6000 as that felt better to me. The default dead zone for a stick would be 8000 since the value was based on the Xbox 360 controller. One last thing, unless something changed after I stopped working on it, "Current Axis Detection Deadzone" only affected the Game Controller Mapping window so that a secondary axis on a stick would not get detected when setting up an SDL mapping for a controller that is why the high value of 20000 was used by default. The mapping would oscillate between MAX and 0 constantly. Next up, I would think that setting a turbo on the button for that purpose would actually make things worse. ![]() I would need to see your profile to get a better idea if that is what is happening. Although with the current mapping routine, if you trying to override LS or RS coordinates with the buttons when no dead zone is set for the input LS and RS, the value from the input LS or RS will likely take priority and that value will be used even if a button is being held. It is treated as a bool in DS4Windows so a Button to Axis mapping is either 0 or MAX value. ![]() ![]() Firstly, there is no additional dead zone for the buttons. A lot of things mentioned don't make sense to me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |