Skip to content
Discussion options

You must be logged in to vote

Nothing is corrupted. Current PadForge builds install usbip-win2 0.9.7.5 because it ships ARM64 drivers and 0.9.7.7 does not. PadForge supports Windows on ARM, and its ARM64 user base keeps growing, so that driver choice is staying.

Windows runs one version of that driver at a time. DS4Windows and VIIPER expect 0.9.7.7, which is why they stopped working once PadForge moved the driver to 0.9.7.5. PadForge does not track DS4Windows's driver versions and never will, and DS4Windows's maintainer has declined to support ARM64 (hbashton/DS4Windows#115).

That leaves a choice between the current PadForge and those two tools on this machine. Closing and locking this, since the decision is final.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by hifihedgehog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants