Downloads:

14,494

Downloads of v 0.0.5-alpha7345:

491

Last Update:

18 Sep 2018

Package Maintainer(s):

Software Author(s):

  • RPCS3 Team

Tags:

playstation emulator

RPCS3

This is a prerelease version of RPCS3.

  • 1
  • 2
  • 3

0.0.5-alpha7345 | Updated: 18 Sep 2018

Downloads:

14,494

Downloads of v 0.0.5-alpha7345:

491

Maintainer(s):

Software Author(s):

  • RPCS3 Team

Tags:

playstation emulator

  • 1
  • 2
  • 3
 RPCS3 0.0.5-alpha7345

This is a prerelease version of RPCS3.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

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

>

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

>

To uninstall RPCS3, 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 rpcs3 -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 rpcs3 -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 rpcs3 installed
  win_chocolatey:
    name: rpcs3
    state: present
    version: 0.0.5-alpha7345
    source: STEP 3 URL

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


chocolatey_package 'rpcs3' do
  action    :install
  version  '0.0.5-alpha7345'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: rpcs3,
    Version: 0.0.5-alpha7345,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller rpcs3
{
   Name     = 'rpcs3'
   Ensure   = 'Present'
   Version  = '0.0.5-alpha7345'
   Source   = 'STEP 3 URL'
}

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


package { 'rpcs3':
  provider => 'chocolatey',
  ensure   => '0.0.5-alpha7345',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install rpcs3 version="0.0.5-alpha7345" 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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.
Description

The History of RPCS3

RPCS3 is an open-source Sony PlayStation 3 emulator and debugger written in C++ for Windows and Linux. The project began development on May 23rd, 2011 and currently supports modern Vulkan, Direct3D 12 and OpenGL graphic APIs. The emulator is capable of booting and playing hundreds of commercial games. With each and every contribution and donation, more and more games are becoming closer and closer to either booting or full playability.

RPCS3 was founded by programmers DH and Hykem. The developers initially hosted the project on Google Code and eventually moved it to GitHub later in its development. The emulator was first able to successfully boot and run simple homebrew projects and was then later publicly released in June of 2012. Today RPCS3 is dubbed one of the most complex video game console emulators of all time with an endless goal to effectively emulate the Sony PlayStation 3 and all of its aspects.

The Never-ending Goal

The goal of this project is to experiment, research, and educate on the topic of PlayStation 3 emulation that can be performed on compatible devices and operating systems. All information was obtained legally by purchasing PlayStation 3 hardware and software. Additional information was obtained from various sources on the internet that include but is not limited to system hardware and software documentation. Most of this information can be found on the PlayStation 3 Developer Wiki.

RPCS3 is not designed to enable illegal activity. Piracy will not be tolerated. Any users conversing about piracy upon joining the Discord server, forums or GitHub community will be re-directed elsewhere. Remember, the best way to play PlayStation 3 games is to play them on the original hardware. For now.

The Controversy of RPCS3

RPCS3 has been seen by many as an impossible feat in the eyes of gamers and programmers. Many fraudulent PlayStation 3 emulators and console emulators in general have clouded the public eye of the impossibility of PlayStation 3 emulation and the ability to emulate the console without a high-end computer. RPCS3 stands true as development progresses, system requirements become lower and more games become a playable reality.

In March 2014, Cinema Blend's William Usher wrote "A lot of gamers originally thought that the complexity of the PlayStation 3's Cell architecture would have prevented it from being emulated." In the same month, Eurogamer's Elio Cossu also wrote "The emulation, even at such an early stage, was a remarkable achievement, considering the complexity of the hardware of the PlayStation 3."

tools\chocolateyinstall.ps1 
$content = Join-Path (Get-ToolsLocation) 'rpcs3'
$target = Join-Path $content 'rpcs3.exe'
$shortcutdir = @{$true='CommonPrograms';$false='Programs'}[($PSVersionTable.PSVersion -gt '2.0.0.0')]
$shortcut = Join-Path ([System.Environment]::GetFolderPath($shortcutdir)) 'RPCS3.lnk'

# This package must be installed in a low-privilege location. I could not get
# it to run in the default %PROGRAMDATA%\Chocolatey\lib location. I was forced
# to use the old-style "tools" location.
Install-ChocolateyZipPackage `
  -PackageName 'rpcs3' `
  -Url 'https://github.com/RPCS3/rpcs3-binaries-win/releases/download/build-ed8aa774bb59e7d155af95b52e9e7894c8777780/rpcs3-v0.0.5-7345-ed8aa774_win64.7z' `
  -Checksum '94D64C77299DD2A96F4066E2EE538D4EEA686D05D9E153DE05BD15802E89C59A' `
  -ChecksumType 'SHA256' `
  -UnzipLocation $content

Install-ChocolateyShortcut `
  -ShortcutFilePath $shortcut `
  -TargetPath $target `
  -WorkingDirectory $content

New-Item -Path "$target.ignore" -Type 'File' -Force | Out-Null
tools\chocolateyuninstall.ps1 
$shortcutdir = @{$true='CommonPrograms';$false='Programs'}[($PSVersionTable.PSVersion -gt '2.0.0.0')]
$shortcut = Join-Path ([System.Environment]::GetFolderPath($shortcutdir)) 'RPCS3.lnk'

Remove-Item -Path $shortcut -Force | Out-Null

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
RPCS3 0.0.17-alpha12558 7 Friday, July 30, 2021 Exempted
RPCS3 0.0.17-alpha12549 11 Thursday, July 29, 2021 Exempted
RPCS3 0.0.17-alpha12537 10 Tuesday, July 27, 2021 Exempted
RPCS3 0.0.17-alpha12522 15 Saturday, July 24, 2021 Exempted
RPCS3 0.0.17-alpha12521 13 Friday, July 23, 2021 Exempted
RPCS3 0.0.17-alpha12519 11 Thursday, July 22, 2021 Exempted
RPCS3 0.0.17-alpha12518 10 Wednesday, July 21, 2021 Exempted
RPCS3 0.0.17-alpha12512 15 Tuesday, July 20, 2021 Exempted
RPCS3 0.0.17-alpha12507 18 Monday, July 19, 2021 Exempted
RPCS3 0.0.17-alpha12501 13 Sunday, July 18, 2021 Exempted
Discussion for the RPCS3 Package

Ground Rules:

  • This discussion is only about RPCS3 and the RPCS3 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 RPCS3, 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