![]() ![]() Hopefully this could help someone else like me that wants to get it running. The install list could probably be reduced at somepoint, this is a huge install, but I went for brute force and didn't worry about disk space yet. Most recently, the PCSX2 team has announced that the emulator will be fully embracing a 64-bit codebase while dropping support for 32-bit systems, and that it will also be adding a Direct3D 12. ![]() (system shell) is just a comment to myself that it was ran in a system terminal not a chrooted terminal. Sudo cp /etc/nf /var/chroot/etc/nf (system shell) Here is an example of 3 tested games: Ratchet: +12.36. So it wouldn't improve much performance on that aspect but there is a ton of 32 bit code that can be streamlined or plainly changed which would still give it an edge in performance or at the very least less unnecessary code. Sudo mount -o bind /proc /srv/chroot/xenial/proc (system shell) Another side note is that for normal PC games the internal resolution viewport but in PCSX2 case, it’s separated in Graphics Settings for upscaling and in General Settings where GS Window is, is the location of how big your viewport (window size) would be. Well PCSX2 in most cases doesn't use the 32 bit limits of RAM which is 4GB, I would even say it's rare to even see it use 2GB RAM. Sudo chroot /srv/chroot/xenial /debootstrap/debootstrap -second-stageĭeb xenial-backports main restricted universe multiverseĪdd-apt-repository ppa:gregory-hainaut/ Sudo debootstrap -variant=buildd -foreign -arch i386 xenial /srv/chroot/xenial/ 32 bit support was dropped after stable release 1.6.0. But this got it to install and launch a game. Not quite sure where to start looking for that. ![]() Posting my notes as I got it to run last night though it's not accepting input from my gamepad as of yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |