Version 3.1.8

[Ryochan7]

Implemented Touchpad Mouse Joystick output support. Virtual DS4 feedback fixes contributed by Nefarius

.NET Runtime x64
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.10-windows-x64-installer
.NET Runtime x86
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.10-windows-x86-installer

• Added working directory info for startup lnk file
• Display input slot number in Output Slots tab
• Force update TooltipText in GUI thread
• Implementation of Touch Mouse Joystick
• Fixed log message generation when virtual pad plugin fails
• Abstract post action stick axis state changing for use with Mouse Joystick routines
• Display some input device information in Output Slots section
• Added some device number checks in ProfileSettingsVM. Avoids test index
• Fixed Keypad Decimal mapping for FakerInput
• Fixes for virtual DS4 output feedback support from ViGEm project. Contribution by Nefarius
• Updated ViGEmClient and ViGEm.NET libraries. Contribution by Nefarius
• Virtual DS4 output feedback support re-enabled. Contribution by Nefarius

---

This discussion was created from the release Version 3.1.8.

[Yuki7k]

Got terribly high CPU usage constantly as soon as I updated to this version. 15% CPU usage constant..

[jojofofo36]

same for me

[Ryochan7]

Essentially the minimum supported version of ViGEmBus is 1.17.333.0. ViGEmBus 1.16.112.0 is only still available as an option for Windows 8 and 8.1 users because that is the last version of ViGEmBus that supports anything older than Windows 10. Since Microsoft is officially going to EOL Windows 8.1 in January 2023, there is really no reason to continue supporting ViGEmBus version 1.16.112.0 at this point.

I will try the latest DS4Windows in ViGEmBus 1.17.333.0 in the next day or so. If the same problem persists there then the root cause should be found and fixed if possible.

Latest release of ViGEmBus can be found at https://github.com/ViGEm/ViGEmBus/releases/tag/v1.21.442.0

Don't know if I will ever get around to making some sort of driver update checker in DS4Windows

[Ryochan7]

Can confirm this issue occurs when using ViGEmBus 1.17.333.0. Will have to investigate this further.

[subz6972]

I confirm the isue still occurs with ViGEmBus 1.17.333.0 with around 10% CPU usage.
Do we need to update VIGEmBus driver to 1.21.442.0 to bypass this issue ?

[Ryochan7]

Nefarius has made a fix to ViGEmClient to correct the issue for older versions of ViGEmBus. Haven't checked the update yet. The problem with the library looks like ViGEmClient did not account for older driver versions that do not have access to the new AwaitRawOutputReport calls. The library would create a new thread to call the driver routine and do a busy wait loop eating up a CPU core.

I will have to download the fix and bundle a new release later. You can update ViGEmBus to version 1.21.442.0 to resolve the issue as well.

[subz6972]

Thanks for your answer.
As you mentioned before, updating ViGEmBus to version 1.21.442.0 makes DS4Windows 3.8.1 working like a charm without any CPU surcharge.

[Basfet]

Gyro is broken for me in v3.1.8. All movements are transmitted at the x-axis only.
DS4v1 and ViGEmBus v1.21.442.0.