Please test whether macros work with "Use DInput only" option with your profiles. However, hiding the original controller and using UseDInputOnly option should NOT be used at the same time because then you would end up without any controllers (see )īut, your solution is quite interesting if macros don't work with "Use DInput Only" profile option. See this Wiki page for more info about "Use DInput only" option: not re-mapping DS4/XBox gamepad keys to another gamepad key) then "Use DInput Only" profile option can be used without hiding the original DS4 controller by "Hide DS4 Controller (=exclusive mode)" option or through HidGuardian driver. If you use pure "keyboard + mouse" output mapping (ie. This gives you the benefit of using DS4 by itself and still being able to use some (limited) keyboard and macro options. If a certain game doesn't use all of the controller buttons, you have more custom keys to work with. After that, you can set custom controls for buttons that have little effect on the game, such as using "Share" as "Alt+Tab" or Touchpad as special controls. This will allow you to use the DS4 controller without passing controls through the XBox virtual controller. Make a new profile with all buttons set to Unbound. It an also be stopped with the "Turn off DS4Windows Temporarily" option, but this disables all custom inputs for the game. Some people can fix this with the "Hide DS4 Controller" option, but it doesn't seem to work for everyone. This causes issues in the game where it is detecting both a DS4 and an XBox controller and causes our inputs to be doubled. This is fine and all, except when we are also using DS4Windows. Some games have native support for DS4 controllers. Looks long-winded in text I know, but it should only take seconds to do this.Īlso please note I only found this about half an hour ago and haven't restarted my pc since so it could just be mere luck until I do restart, then again having someone else try it would help confirm whether it's an actual fix or not.I hadn't seen it posted anywhere, so I'll post it here in case no one else knows. cycle 5/5 and the bar should turn red and mention that the controller is disconnected, then plug your controller back in and a yellow bar should appear again saying something about not being able to connect to exclusive mode, simply click the bar turning it into a blue bar that says connected using "shared mode" then re enter the game and it should work again. After you Alt-Tab unplug/disconnect your controller and go back onto InputMapper, there should be a yellow bar at the bottom that says "encountered read failure attempt */5". Once it's on launch DS3, wait until it gets to the "press any key" screen and Alt-Tab out. Anyway on to the fix, so make sure to have your controller plugged in/bluetooth connected with InputMapper running (just to note I have Exlusive Mode turned on in the settings). First, you'll have to use InputMapper rather than DS4Windows. Originally posted by Cloud6378:I've been tearing my hair out over this issue for weeks with both DS4Windows and InputMapper. Looks long-winded in text I know, but it should only take seconds to do this. I've been tearing my hair out over this issue for weeks with both DS4Windows and InputMapper.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |