Downloads:

45,960

Downloads of v 3.0.2:

302

Last Update:

12 Apr 2021

Package Maintainer(s):

Software Author(s):

  • Travis Nickles
  • Jays2Kings

Tags:

ds4windows ps4 dualshock controller emulator foss

DS4Windows

3.0.2 | Updated: 12 Apr 2021

Downloads:

45,960

Downloads of v 3.0.2:

302

Maintainer(s):

Software Author(s):

  • Travis Nickles
  • Jays2Kings

DS4Windows 3.0.2

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Dependencies require reboot

To install DS4Windows, run the following command from the command line or from PowerShell:

>

To upgrade DS4Windows, run the following command from the command line or from PowerShell:

>

To uninstall DS4Windows, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade ds4windows -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade ds4windows -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure ds4windows installed
  win_chocolatey:
    name: ds4windows
    state: present
    version: 3.0.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'ds4windows' do
  action    :install
  version  '3.0.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: ds4windows,
    Version: 3.0.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller ds4windows
{
   Name     = 'ds4windows'
   Ensure   = 'Present'
   Version  = '3.0.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'ds4windows':
  provider => 'chocolatey',
  ensure   => '3.0.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install ds4windows version="3.0.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 12 Apr 2021.

Description

DS4Windows

Like those other DS4 tools, but sexier.

DS4Windows is an extract anywhere program that allows you to get the best
DualShock 4 experience on your PC. By emulating an Xbox 360 controller, many
more games are accessible. Other input controllers are also supported including the
DualSense, Switch Pro, and JoyCon controllers (first party hardware only).

This project is a fork of the work of Jays2Kings. You can find the old project
website at ds4windows.com.

DS4Windows Preview

Requirements

  • Windows 10 or newer (Thanks Microsoft)
  • Microsoft .NET 5.0 or higher
  • Visual C++ 2015-2019 Redistributable. x64 or x86
  • ViGEmBus driver (DS4Windows will install it for you)
  • Microsoft 360 Driver (link inside DS4Windows, already installed by Windows if
    you've used a 360 controller before)
  • Sony DualShock 4 or other supported controller
  • Connection method:
    • Micro USB cable
    • Sony Wireless Adapter
    • Bluetooth 4.0 (via an
      adapter like this
      or built in pc). Only use of Microsoft BT stack is supported. CSR BT stack is
      confirmed to not work with the DS4 even though some CSR adapters work fine
      using Microsoft BT stack. Toshiba's adapters currently do not work.
      Disabling 'Enable output data' in the controller profile settings might help with latency issues, but will disable lightbar and rumble support.
  • Disable PlayStation Configuration Support and
    Xbox Configuration Support options in Steam

Social

Twitter @ds4windows
YouTube
BitChute
BitTube.tv
Mastodon @[email protected]
Minds @ds4windows


legal\LICENSE.txt
From: https://raw.githubusercontent.com/Ryochan7/DS4Windows/jay/LICENSE.txt

LICENSE

This file includes licensing information for ds4windows

MIT License

Copyright (c) 2019 Travis Nickles

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

1.  Download the installer:

    x32: https://github.com/Ryochan7/DS4Windows/releases/download/v3.0.2/DS4Windows_3.0.2_x86.zip
    x64: https://github.com/Ryochan7/DS4Windows/releases/download/v3.0.2/DS4Windows_3.0.2_x64.zip

2.  You can use one of the following methods to obtain the checksum: 
    - Use powershell function 'Get-FileHash'
    - Use Chocolatey utility 'checksum.exe'
    - Using AU:
        Get-RemoteChecksum https://github.com/Ryochan7/DS4Windows/releases/download/v3.0.2/DS4Windows_3.0.2_x64.zip

3.  Compare to Checksum:

    checksum32: 1D6F0E6A999A78E58DCBD6501D8AB49B7AD9229544C7C6FE51A9BBCB2CF86F36
    checksum64: BB292C64A9A0D05E7747F6D9B54A0B040ABD89EB8D0B03992607A5090C1D2B80
tools\chocolateybeforemodify.ps1
$packageName  = $env:ChocolateyPackageName

$p = Get-Process -Name "DS4Windows" -ea 0
if (!$p) {
    Write-Host "$packageName is not running"
    return
}

Write-Host "$packageName is running, trying to gracefully shut it down before upgrade/uninstall"
Stop-Process -InputObject $p -Force
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition


$packageArgs = @{
  PackageName    = $env:ChocolateyPackageName
  FileFullPath   = gi $toolsPath\*_x86.zip
  FileFullPath64 = gi $toolsPath\*_x64.zip
  Destination    = $toolsPath
}

ls $toolsPath\* | ? { $_.PSISContainer } | rm -Recurse -Force #remove older package dirs
Get-ChocolateyUnzip @packageArgs
rm $toolsPath\*.zip -ea 0

$startupPath = [Environment]::GetFolderPath("Startup")
$startMenuPath = [Environment]::GetFolderPath("CommonPrograms")

if(Test-Path -Path "$startupPath\$env:ChocolateyPackageName.lnk") {
    Install-ChocolateyShortcut `
        -ShortcutFilePath "$startupPath\$env:ChocolateyPackageName.lnk" `
        -TargetPath "$env:ChocolateyInstall\bin\$env:ChocolateyPackageTitle.exe"
}

Install-ChocolateyShortcut `
  -ShortcutFilePath "$startMenuPath\$env:ChocolateyPackageName.lnk" `
  -TargetPath "$env:ChocolateyInstall\bin\$env:ChocolateyPackageTitle.exe"
tools\chocolateyuninstall.ps1
$startupPath = [Environment]::GetFolderPath("Startup")
$startMenuPath = [Environment]::GetFolderPath("CommonPrograms")

Remove-Item "$startupPath\$env:ChocolateyPackageName.lnk" -ErrorAction SilentlyContinue -Force
Remove-Item "$startMenuPath\$env:ChocolateyPackageName.lnk" -ErrorAction SilentlyContinue -Force
tools\DS4Windows_3.0.2_x64.zip
md5: F9997D98290092C5AF06E4ED0E491921 | sha1: 4A7B9283D18E3C3AC08E1CB1CC417F9419DBA605 | sha256: BB292C64A9A0D05E7747F6D9B54A0B040ABD89EB8D0B03992607A5090C1D2B80 | sha512: C78F7B335657A91F27EC4B83A99DC87A2A09D9223144BECBAAE8E437778C5A8841EFDE0F2D8FB39A7770E7CC740E50681975478C1CB9252BAE22128DCAE86965
tools\DS4Windows_3.0.2_x86.zip
md5: 18FC50836FD56011F236A7441A4E3233 | sha1: 4C4C63F08C84D8662A7F03A44741834345D7FFB6 | sha256: 1D6F0E6A999A78E58DCBD6501D8AB49B7AD9229544C7C6FE51A9BBCB2CF86F36 | sha512: 0E0A74B689062AD7C77FFE557AB17D7AC0CAA41E47CCB14D21EA821865623F57498A9E742D27A7AA40F0E2724FF450F052498EABE82DDF863D265799B855BDD7

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
DS4Windows 3.0.1 638 Saturday, April 3, 2021 Approved
DS4Windows 3.0.0 182 Friday, April 2, 2021 Approved
DS4Windows 2.2.15 640 Thursday, March 25, 2021 Approved
DS4Windows 2.2.14 155 Thursday, March 25, 2021 Approved
DS4Windows 2.2.13 398 Saturday, March 20, 2021 Approved
DS4Windows 2.2.11 229 Thursday, March 18, 2021 Approved
DS4Windows 2.2.10 488 Wednesday, March 10, 2021 Approved
DS4Windows 2.2.9 367 Friday, March 5, 2021 Approved
DS4Windows 2.2.8 389 Saturday, February 27, 2021 Approved

Discussion for the DS4Windows Package

Ground Rules:

  • This discussion is only about DS4Windows and the DS4Windows package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or DS4Windows, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus