Re: Pcsx2 0.9.8 Download

0 views
Skip to first unread message
Message has been deleted

Fanny Lococo

unread,
Jul 11, 2024, 9:16:55 AM7/11/24
to liotiwitchhunt

I installed PCSX2 with pacman and I remember being able to launch it from the command line with "pcsx2".
However I can't get it to work, it just says "command not found". I also tried installing from AUR but it's the same thing.
I didn't get any error message and both installations went by smoothly.
Then I tried adding the emulator to steam from the list but it doesn't show up, while every other application I installed does.

pcsx2 0.9.8 download


Download File https://vittuv.com/2yRPKy



Hello, so i have retroarch for a few weeks now and im having an issue when runing pcsx2 on retroarch. All the games i try to play start and all but imediately have an extreme lag and audio problems, not to mention a few bugged textures here and there. Now, when running pcsx2 by itself, everything goes as it should, no lag or any issues whatssoever so my guess is that it is some issue between the emulator and retroarch.

Im a noob in over my head, can someone with experience help me (in a sort of step-by-step way would be nice) install pcsx2 in 64 bit ubuntu 15? I read something about chroot, but also multiarch, being needed? I don't really know what either of those are or how to use them. is it possible to run it off a thumb drive as well?

Because of the complex nature of emulation, even if you meet the recommended requirements there will be games that will NOT run at full speed due to emulation imperfection, floating point emulation differences, issues with emulator itself or other problems.

In case you're having additional files with the .bin, make sure they're sharing the same filename or they'll be ignored.
So as an example let's say you have a SCPH-70004_BIOS_V12_EUR_200.BIN file with an EROM file, a ROM1 file and a ROM2 file, it should look like this:

The legacy memory cards folder is only used if Mcd001.ps2 and/or Mcd002.ps2 is detected in retroarch/system/pcsx2/memcards/ and the "Memory Card: Slot N" core option is set to "Legacy".
This can be useful if you were using an older version of the core that didn't use the saves folder yet, or if you transferred the memcards folder directly from standalone.

The current standalone development version is reported to be compatible with approximately 97.4% of 2,641 tested games as of August 2020. Compatibility means only that the game will not crash, lock up, or enter a loop; there can still be bugs, missing post-processing effects, textures, and shadows in many compatible games. This is especially the case in hardware mode; a slower software mode is available for bugs without workarounds. You can check compatibilirt list in here

I'll try to keep up as much as possible with upstream, but realistically releasing an update every few hours is not happening, especially if I'm going to be checking that it builds properly as one should. Most likely I will only be pushing new versions on weekends.

Also a reminder: if there are issues specific to this package (i.e. you tested the official AppImage and the issue is not present in the AppImage), report them here.This shouldn't happen often as I will try to maintain deps and flags in accordance with the upstream CI.

Btw, I just changed how pcsx2-git builds. Right now it directly patches and builds Shaderc in itself, apparently, the package idea wasn't the most popular, though I feel the separate package is a more stable way of handling this whole debacle with Stenz's patches.

Most likely, the problem was pcsx2 has switched to patched shaderc. The package aur/shaderc-non-semantic-debug is incompatible with extra/shaderc and will break other packages. I recommend not to use any package that uses it, currently aur/pcsx2 and aur/pcsx2-git.

@HurricanePootis The DISABLE_ADVANCE_SIMD option is misnamed (in my opinion). It does not disable avx. It probably did, a long time ago, and its use would have been appropriate for Arch/AUR because Arch supports only x86-64 (v1). But now upstream pcsx2 requires sse4 (v2). They also create "multi-ISA" binaries that use dynamic dispatch to support multiple versions (sse4, avx, avx2) of some functions when DISABLE_ADVANCE_SIMD=ON. Modern CPUs would be expected to use the avx2 version of those functions, but I have no way to confirm.

59fb9ae87f
Reply all
Reply to author
Forward
0 new messages