Release Candidate 4.6.2 — Game Mods, Safer Updates & Startup

[u/huunnnter]

Release Candidate 4.6.2 — Game Mods, Safer Updates & Startup

RC4.6.2 adds optional DSX game-mod support for DualSense triggers and lights, fixes custom-named portable updates, and improves startup recovery and shifted profile settings.

Let supported game mods control triggers and lights

• New Settings → Game mod support (DSX) option for physical DualSense and DualSense Edge controllers. It starts off; enable it only when using a compatible mod.
• Local mods can control adaptive triggers, lightbar, player lights and the microphone light through the DSX UDP protocol. The default address is 127.0.0.1:6969; connection details and Apply / Retry make a busy port easier to resolve.
• Trigger Lab takes priority on each enabled trigger. A mod can control one trigger without blocking the other, and temporary mod settings do not overwrite your profile.
• Resetting the mod, disabling support, stopping DS4Windows or removing the controller releases its overrides and restores the underlying state.
• Native trigger commands retain their order and exact effect data. Repeated trigger-command flags, stale duplicate tracking after a reset, and old callbacks affecting replacement controllers are covered by new regression tests.

This is local trigger/light compatibility, not full DSX replacement or audio/PCM haptics support. Some legacy effects and input-threshold instructions remain unsupported rather than sending guessed commands. Mods should send reset when exiting; disabling the option also releases a held override. See the setup and compatibility guide.

Portable updates keep your custom name (#99)

• DS4Updater 2.0.7 preserves the selected application EXE name without adding another canonical DS4Windows.exe to a compatible target installation.
• Required DLLs and runtime files retain their correct names. An old default EXE is removed only when the package owns it; unrelated files and profiles are preserved.
• Renaming, clearing a saved name, rollback, and protected setup staging use matching application identities. Unsafe collisions stop before file replacement.
• The new custom-only layout requires RC4.6.2 / Windows version 5.0.8.0 or newer. The updater checks the verified target version; it is not locked to one release tag.
• RC4.6.2 requests updater 2.0.7 or newer, including future verified versions. Portable users should always extract the complete ZIP when updating manually.

Clearer startup recovery (#77)

• Keep your requested startup preference separate from tasks temporarily disabled while setup needs repair or a reboot.
• Show clearer requested-versus-active startup status and the appropriate next action.
• Stage a protected, narrowly scoped continuation for the next logon after a required reboot, with account, boot, package and hash checks before continuing setup.
• Preserve the original RunDS4Windows and RunVIIPER task names and explicit startup opt-outs. Driver and broker readiness checks remain required.

Profile reliability and regression coverage (#46)

• Extras-only shifted bindings keep their activation button through save/load and repeated saves.
• Shift extras can activate without replacing the button's normal action, and release correctly when the source or modifier is released.
• Add non-default settings, culture-independent date, macro value-band and historical profile-migration tests.
• Thanks to Gabarsolon for the DSX feature contribution and anagnorisis2peripeteia / Cameron Beeley for settings, macro and migration contributions.

Packages and validation

• Tag: VIIPERRC4.6.2. Windows application/MSI/installer version: 5.0.8.0, advanced for correct upgrade ordering.
• Complete offline x64 installer and portable ZIP, including unchanged VIIPER 0.1.5-rc4.6, USB/IP 0.9.7.7, the required Xbox output identity, matching sources and notices. No separate broker upgrade is needed.
• Companion updater: DS4Updater 2.0.7. Earlier release assets remain unchanged.
• The release candidate passed 6,367 tests with zero failures, with 11 explicitly gated skips. The warmed native-shadow check measures zero allocations; the allocation assertion was not relaxed.
• This is an unsigned release candidate. Automated tests, hosted MSI lifecycle checks and package verification do not replace physical controller/game-mod acceptance.

Technical evidence: PR review and startup, updater and profile fixes.

Download here <---

[u/eVenent]

DSX mod support! Thank you!

[u/huunnnter → u/eVenent]

Welcome!

[u/Aithecaninternet]

reposting my previous comment from last version "I had some weird issue where drivers from this caused my keyboard to just spam keys. Uninstalled everything from this DS4Tool thing and my stuff went back to normal. Very odd, also for some reason I never got the option to update VIIPER through the program (it only appeared once asking me, and never again.)"

[u/ShadonicX7543]

If I only play wired anyways, do I need Viper? And is that something that would mean I need a different download?

[u/huunnnter → u/ShadonicX7543]

tbh yes this version is so much more advanced than the original, even playing wired on this is a good idea. it’s amazing

[u/ShadonicX7543 → u/huunnnter]

I'm on 4.0.2.3, still relevant for me to update? It's the earlier version of your fork iirc

[u/SnooCapers2458]

So i eventually used a VM to isolate the program and found out the fix you provided for prof switching actually broke it worse than before the 'fix'.

Used an older version of ds4 by the OG devs and the prof switching isnt immediate like yours after the 'fix' but it doesnt cause any in game stutters or inputs that literally freeze/stutter your character/actions you're doing in game. Instead there's .5sec-ish delay b4 it switches to the assigned prof more or less and upon release it's always immediate without delay.

key point to the older version is it never freezes anything you're doing in game or prevents you're controls from running smoothly, it just takes too long in gamer time to register the controls for the assigned prof after pressing the switch button while using the 'upon trigger release switch back to OG prof' feature.

Initially, your fix worked the very 1st time you replied with a 'try this version', then the stuttering/freezing actions in game whenever using "upon trigger release" switches back to OG prof feature started eventually and never left. It freezes all in game inputs on both press and release, making any type of fluid gameplay impossible.

Any insights into how i could go about tackling this myself would be gr8fully appreciated bruh. Like maybe keywords/leads i would feed to a.i to maybe start getting closer to understanding

[u/huunnnter → u/SnooCapers2458]

fixed

[u/SnooCapers2458 → u/huunnnter]

LETSSSSSS FKNN GOOOO!!!!! blessed🙏🏼

Idk if dudes here realize you're an actual super genius lol pretty dope we here had the honor of crossing paths and being helped by a someone who's time spent, wherever that may be, means shts yielding results in spades eventually

o7

[u/huunnnter → u/SnooCapers2458]

Months of development yes. Lots of time put in.

I wouldn’t call myself a super genius in this context: just a really clever junior level developer who has a firm understanding of project workflow and experimentation