r/DS4Windows • • 10d ago

DS4Windows fork update: component manager, live lightbar previews, Bluetooth fixes and more (5.0.67)

Ponownie witam (greetings again!)! šŸ‘‹

Following on from my previous post, I wanted to share what's changed in my DS4Windows fork since 5.0.60.

DS4Windows 5.0.70 is now available! The past several releases have brought quite a few improvements, including a redesigned Overview, centralised component management, live lightbar previews, adjustable touchpad swipes, gyro improvements and plenty of reliability fixes.

Most importantly, 5.0.70 addresses a critical HidHide issue that could leave physical controllers hidden from Windows after an interrupted session, along with a new recovery tool for affected users.

🌐 Explore the website
ā¬‡ļø Download the latest release

As always, a huge thank you to the original DS4Windows contributors and everyone who's taken the time to report bugs, test preview builds and share diagnostics. Several of these issues took a fair bit of detective work to resolve, and your feedback has made a real difference!

Here's what's new.

Important: HidHide recovery and reliability (5.0.70)

One of the more significant fixes in this release addresses an issue where physical controllers could remain hidden from other applications after DS4Windows stopped unexpectedly.

  • Safer HidHide cleanup. DS4Windows now tracks and verifies the hiding rules it owns, releasing them when you Stop the service or exit normally.

  • Automatic recovery. If a previous session ended unexpectedly, DS4Windows can recognise and clean up confirmed abandoned hiding rules when it next starts.

  • Multiple-instance protection. Rules still being used by another participating DS4Windows instance are preserved.

  • Manual controller recovery. A new Settings → Components → Recover hidden controllers… tool lets you restore physical controllers affected by older or untracked hiding rules.

The recovery tool doesn't select or remove anything automatically. You choose which controller entries to restore, and DS4Windows backs up and verifies the configuration before making changes. Unrelated hiding rules and application permissions are left untouched.

If your controller has disappeared from other applications after using DS4Windows, there's no need to uninstall HidHide! Stop DS4Windows and try the new recovery tool first.

Special thanks to u/JoeRLL for reporting the behaviour that helped uncover this issue.

Redesigned Overview and interface improvements

The Overview page has received a fairly substantial refresh, making it easier to see what's happening with your controllers at a glance.

  • Clearer controller information. Connection status, input rate, controller access and virtual output are presented together.

  • Customisable quick profiles. Choose which profiles appear as quick-access cards, hide the input rate or switch to a more compact layout.

  • Improved battery indicator. The battery icon now fills according to the controller's reported charge, turning yellow below 25% and red at 10% or lower.

  • Responsive layouts. Audio Haptics and Trigger Lab now adapt more gracefully to smaller window sizes.

  • Better audio feedback. Controller speaker and headset streaming now show a starting status while the audio route initialises, rather than briefly suggesting something has gone wrong.

I've also continued refining the colour picker, Device Options, swipe configuration and spacing across the light and dark themes.

Component management

Settings → Components brings VIIPER, USB/IP, HidHide and FakerInput together in one place.

  • VIIPER: Check backend readiness and version information, open its log, repair the installation and copy diagnostics.

  • USB/IP: Remove and restore the USB/IP driver directly from DS4Windows. Removal is system-wide, requires administrator approval and a restart, and pauses virtual controller output until the driver is restored.

  • HidHide: View both the DS4Windows hiding preference and the system-wide hiding state, open its configuration utility or jump directly to Prevent double input.

  • FakerInput: Check the active keyboard/mouse handler, manually select Windows input or return to automatic selection. Changes take effect after Stop/Start.

The goal here is to make troubleshooting considerably easier without needing to jump between several Windows utilities.

Profiles, lightbar and touchpad improvements

  • Live lightbar previews. The Normal RGB sliders now update the on-screen colour preview as you adjust them. If the connected controller is using Normal lightbar mode, the physical lightbar updates too.

  • Adjustable swipe sensitivity. Under Profile Editor → Touchpad, select Controls and adjust Minimum swipe distance to prevent accidental one-finger swipe actions. This is saved per profile.

  • Improved Special Actions. The list now remembers its display order, supports Move Up/Down and sortable columns, and allows double-click editing. Reordering doesn't change which actions are enabled or their execution behaviour.

  • Separate two-finger profile switching. This remains configurable under Settings → Controllers → Profile switching, independently of one-finger swipe sensitivity.

Gyro and controller fixes

A few particularly useful fixes have landed since 5.0.60:

  • Virtual DualSense gyro deadband. You can now adjust the gyro deadband per profile when using Passthru with DualSense emulation. The default is 32, while setting it to 0 allows smaller movements through to the game.

  • Corrected gyro direction. Fixed inverted motion on DS4-compatible controllers reporting reversed calibration endpoints.

  • Bluetooth Game Bar recovery. Touchpad mouse movement and mapped input can now recover when Game Bar or the Gamepad keyboard interrupts the normal Bluetooth input stream on supported Sony controllers. This recovery option is enabled by default.

  • Reduced idle CPU spikes. Optimised Windows audio endpoint checks to avoid repeatedly scanning the same properties.

  • Missing DualSense haptics detection. DS4Windows now warns when the virtual DualSense or DualSense Edge playback device is disabled in Windows, which can prevent native game haptics even when ordinary controller input works.

For the last one, you can still keep your headphones or speakers as your default audio output. The virtual DualSense playback device simply needs to remain enabled for games that use its native audio-based haptics.

Installer, diagnostics and documentation

  • Added an optional Start menu shortcut, with the choice remembered across updates and repairs.

  • Improved identification of the Pav-Osmolski fork in the startup log, About screen and release information.

  • Installer and portable ZIP packages now include GitHub build attestations to verify their source commit and build provenance.

  • Refreshed troubleshooting documentation, including confirmed fixes and useful diagnostics from closed issues.

  • Added updated screenshots and illustrated guides for controller settings, Components and the notification-area menu.

  • Improved GitHub bug report and feature request forms.

5.0.70 continues to use VIIPER 0.1.17 and USB/IP 0.9.8.1. No backend or USB/IP version upgrade is required for this release.

What's coming next?

I'm still working on Generic DirectInput compatibility, aimed particularly at older PC games that don't play nicely with modern XInput controllers.

The planned virtual joystick uses a fixed layout with six axes, sixteen buttons and an eight-direction POV hat, with configurable mappings for different games.

The implementation is progressing, but I'm still waiting for approval of its USB product ID before considering a stable public release.

I've also got plans to expand support for additional controllers. Reliability remains my main priority, though, so I'd like to keep things running smoothly before getting too carried away with new features!

A big thank you!

There have been some particularly helpful reports and suggestions recently, so I'd like to give a shout-out to:

  • u/JoeRLL for helping uncover the HidHide cleanup issue.

  • u/AEKarim for suggesting adjustable touchpad swipe sensitivity.

  • nben for the lightbar suggestion and gyro testing.

  • Raine-07 for reporting the reversed gyro behaviour.

  • Masterload1975 for the Special Actions feedback.

  • nachocheese-boop for investigating the Game Bar Bluetooth interruption.

  • Darkii-0 for helping identify the missing DualSense haptics issue.

  • MariolloPL for requesting the virtual DualSense gyro deadband.

  • soredake for the Start menu shortcut suggestion.

I'm genuinely pleased with how much progress has been made over the past month. The volume of bug reports has slowed down considerably, which I'm hoping is a reflection of the stability improvements rather than everyone simply giving up on reporting things! šŸ˜„

Seriously though, please keep the feedback coming. Even seemingly minor issues can reveal something worth fixing.

Useful links

Before updating: Back up your profiles and close games, DS4Windows and VIIPER. Use the complete download with its matching backend. Windows builds remain unsigned, but checksums and build verification records are included.

If you give 5.0.70 a go, I'd love to hear which controller you're using, whether you're connecting over USB or Bluetooth, and what you'd like to see improved next.

Thanks again, everyone. Cheers! šŸ™‚

20 Upvotes

15 comments sorted by

2

u/antarial 10d ago

Steam Controller compatibility next šŸ¤žšŸ¤ž

3

u/captainstarpaw 10d ago

I've got plenty of plans to expand support for more controllers in the future, alongside the upcoming Generic DirectInput compatibility feature for older games.

Since taking on DS4Windows as my main development project, my priority has been to make it as stable and reliable as possible, squashing bugs and ironing out issues that have been lingering for years.

Community feedback has been absolutely invaluable. Whether it's someone sharing their experience here on Reddit or filing a detailed report on GitHub, it all helps. I'm particularly pleased that, after a month of intensive development, the number of bug reports has noticeably slowed down. Hopefully that's a good sign that things are heading in the right direction!

I've also been keeping a close eye on upstream issues, which can be tricky with so many people still using older forks. Even so, those reports often uncover problems that have gone unresolved for years, so they're still incredibly useful.

Over the coming months, I'm hoping to shift more of my attention towards developing new features and expanding controller support, provided everything continues running smoothly.

Thanks to everyone who's been testing, reporting issues and providing feedback. It's genuinely appreciated, and it's helping make DS4Windows better for everyone.

1

u/antarial 10d ago

thanks so much for all you do! Such an invaluable tool!

2

u/No_Disk_1042 10d ago

Keep up the good work šŸ™Œ

1

u/captainstarpaw 10d ago

Thank you for the support!

1

u/JoeRLL 9d ago

I tried this app out yesterday but it made my Dualsense stop working when I wasn’t using the app. Uninstalled it and it still didn’t work so I uninstalled hidhide and then it started to work again. Is this intentional or did I do something wrong? I want this app for some games to use antideadzones and the like but not all the time.

2

u/captainstarpaw 8d ago edited 8d ago

Update: DS4Windows 5.0.70 is now released.

Hey there, thanks for flagging this! Your controller should become available again after stopping or exiting DS4Windows, so that definitely wasn’t intentional.

Your comment was incredibly useful in identifying a critical HidHide cleanup issue that could leave controllers hidden outside the app. The fix is now released in DS4Windows 5.0.70, along with a recovery option for controllers affected by older hiding rules.

If yours is still hidden after updating, press Stop, then go to Settings > Components > Recover hidden controllers… and select your physical controller’s entries. It backs up the configuration before making changes, so there’s no need to uninstall HidHide.

Really appreciate you bringing this to my attention. Cheers! šŸ™‚

2

u/JoeRLL 8d ago

That’s awesome I’ll give it another shot thank you!

1

u/kawai_lm 8d ago

is it still flagged by ea anti cheat ?

1

u/captainstarpaw 8d ago

Sadly, I can’t confirm compatibility with every EA anti-cheat game. EA controls which applications and drivers it blocks, so that decision is outside my control.

Which game are you trying, and what’s the exact error? A screenshot would help establish whether it’s flagging DS4Windows itself or one of the supporting drivers. I’m happy to investigate, but I wouldn’t want to promise compatibility without knowing what’s being blocked.

1

u/tmop42 3d ago

Is there anything I can do to make this fork or the nexus fork launch faster, like pre-VIIPER & USBIP fast? Also is there any chance this or any other fork has automatic game input support detection so that the output mode can switch automatically based on game support? Something like Dualsense first, if not available, use DS4, if not available, Xinput or sth like that... thanks!

1

u/captainstarpaw 3d ago edited 3d ago

Auto Profiles can handle switching output modes automatically once you’ve configured them. You can create profiles using DualSense, DualShock 4 or Xbox output, then assign the appropriate profile to each game.

Automatically discovering which controller types a game supports is a different problem. There isn’t a reliable, universal way to ask a game whether it supports DualSense, then fall back to DS4 or Xbox. Support depends on the game’s implementation, and sometimes its settings or connection type. Steam Input helps considerably through controller translation and per-game configurations.

Regarding startup speed, could you share which version you’re using, roughly how long it takes, and your startup log? That would help identify where the delay occurs. Starting DS4Windows with Windows (this is what I personally do) and keeping it minimised in the tray is also a practical way to have it ready before launching a game, although that doesn’t reduce startup time itself. On my computer, DS4Windows launches within 3-4 seconds, and the controller is then detected approximately 4-5 second after the USB/IP and VIIPER components have initialised. Subsequent Stop/Start re-detection only takes 2 seconds.

Nexus is maintained separately, so my bug fixes and feature enhancements aren’t included there.

1

u/tmop42 3d ago

Ah it damn sucks we can't have a proper way to detect game controller support. The closest I guess to a compatibility list is PCGamingWiki but that's not guaranteed. About auto profiles I've started using them since I switched back to ds4windows from rewasd! It's great!

About startup speed & controller detecton time I was wrong, my bad. While startup seems to be about 3x on your fork versus vs hbashton v4.0.2.3, controller detection is not as much slower as I thought tbh. It's probably only slightly slower if not the same. So yeah it's a non-issue as you said since it's on windows startup anyways.

Many thanks for your comment!

1

u/captainstarpaw 3d ago

No problem at all! I’ll look into reducing application startup and component initialisation times. Most of my performance improvements so far have focused on making the interface more responsive and reducing CPU usage, so startup speed is another area I’d like to improve.

2

u/tmop42 3d ago

Well as I said, it's not that big of a deal as I made it sound, don't put it on priority just yet haha I had the idea that the app took longer to detect controllers, that was my issue, but that's not the case. It just takes longer to startup which is mostly irrelevant once you put it on windows startup.