![]() I do think these are far too many hoops to jump through just to get audio working for a game with your controller, but until Respawn and/or Microsoft releases universal drivers for these things, this is the way. This is required for everything to work! Do not change type to DualShock as it will not work. Note that DS4Windows emulates an Xbox 360 controller by default. Only issue was controller was too sensitive and I did have to adjust my deadzones using DS4Windows. If your controller is still not working please email. Running ScpDriver.exe will give you the option to uninstall the old driver.)Īfter installing the latest DS4Windows, audio and microphone worked in Apex as expected. If youre trying to get multiple PS4 controllers to work on PC, youll need to download DS4Windows. The only two solutions are to buy an expensive pair of Bluetooth. Even after I tried every device on that list the headphones did not produce any sound. In that folder is an uninstaller named ScpDriver.exe: I already had DS4Windows installed, but that didn't help, and I tried to switch the output sound to the Wireless Controller, but the device was not in the list of possible output devices. It should create a folder (in wherever you launched DS4Windows.exe) that says "Virtual Bus Driver". (If you need to do this, download the old version again, and click "install driver" when it prompts you. Make sure you uninstall the old version's driver. You need to use the latest version of DS4Windows, which can be found in this github repo: - The old version by Jay4Kings is no longer maintained. ![]() Never had this problem with my old computer and never am able to get wired working as every slight movement it disconnects and reconnects multiple times every second.I fixed this. I try it but no sound out from my ps4 controller headphone jack. You can set it as default device so it is always used when you have DS4 connected, Right click speaker on your taskbar and select sounds. Click speaker Icon on taskbar and select DS4 as playback device. Sometimes both controllers work for 3 seconds with Input Mapper but that's it, doesn't work any longer, I get a warning about 500ms latency and boom, disconnects. Make sure the DS4 is the sound output device. The moment you connect a 2nd controller the first disconnects. So I tried a program call Input Mapper and it works. Ever since that was installed, DS4 Windows doesn't even detect a single controller. I installed that, a cmd popped up then it was finished installing. ![]() I then try fixing it by downloading something recommended in a YouTube tutorial called Input Mapper HIDGuardian. It's not a controller issue either, both work fine by themselves. ![]() I tried again, around a minute later it happened again, the whole time I was pressing buttons on both controllers to make sure they wouldn't disconnect. A minute later, the 2nd controller disconnects and won't reconnect until I reboot. I go to connect a 2nd DS4 controller, DS4 recognises it fine, it connects, all good. I got DS4Windows installed, then connected 1 DS4 controller via Bluetooth, it works really well, long distance, no lag, just fine. Recently I got a new computer and it's motherboard is a Z390M Gaming Edge with bluetooth 5.0 support. Click advanced and then set the preferred device to Unified Virtual HID. Connect both controls via bluetooth and done, no issues. So what I did to fix the detection issue was to shut down DS4Windows and then go into Control Panel>Hardware and Sound>Devices and Printers and then right click on Wireless Controller in order to select Game Controller Settings. Previously I used DS4Windows on an alienware area 51 with no problems. With quarantine in action and my little sister now being homeschooled due to schools shutting down, I decided it was time to pull out the ds4 controllers and play some old ps2 games with her. I was using the original version that hasn't been updated since 2016. Make sure the Dual Shock controller is powered On. Edit: The new version of DS4Windows by Ryochan7 along with the driver it comes with, updated today, seems to fix the issue. Click on the Settings tab among the option running horizontally near the top of the app window. Try to stop starting the DS4Windows so that it connects to the controller. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |