@Lolonois Thank you very much for your feedback. I'll look into your suggestions :).

I have read about a similar issue in the forum, and the solution was to install the pulseaudio driver.
Before you try, back up your setup!

sudo apt install pulseaudio pulseaudio-utils

@dult-np ok I actually managed to compile but no rom would go past a black screen unfortunately. I guess we'll still have to stick to AetherSX2

I can't edit my post (understandable, im a newbie). But if I could, it would say

Edit: I figured it out- I had become error. I was trying to be fancy with my file pathing, and I forgot the adage- keep it simple

OK so this worked:

I added the following to runcommand-onlaunch.sh

rm /opt/retropie/configs/ps2/Config/cache/vulkan_pipelines.bin && rm /opt/retropie/configs/ps2/Config/cache/vulkan_shaders.bin && rm /opt/retropie/configs/ps2/Config/cache/vulkan_shaders.idx

It did not appear to like them on separate lines. Now when a game launches, it deletes those three files, and if I'm loading a PS2 game with AetherSX2 it re-creates them once the game loads, but then deletes them before the next game.

So this way those files never get bloated and not hog down any other games.

I managed to launch it without installing a full DE, here is what I did in case anyone is interested (although installing a DE is probably the simplest option):

Install xorg and xinit:

sudo apt install -y xorg xinit

In /etc/X11/Xwrapper.config set allowed_users=anybody

Add the current user (or replace with user that launches the command) to these groups:

sudo usermod -aG input,tty,video $USER

Grant access to the second tty to current user (this need to be repeated after a reset):

sudo chown $USER /dev/tty2

Now replace the command to launch the emulator in /opt/retropie/configs/ps2/emulators.cfg:

pcsx2-nogui = "xinit /opt/pcsx2-unstable/pcsx2-qt -fullscreen -nogui %ROM% -- :0"

It's important to use the full path /opt/pcsx2-unstable/pcsx2-qt and not just pcsx2-qt because the later is actually a shell script that calls the former and xinit doesn't like that:

cat $(which pcsx2-qt) #!/usr/bin/bash /opt/pcsx2-unstable/pcsx2-qt "$@"

And that's it. Launching a game will show the PCSX2 gui where we can choose the different folders for roms and BIOS. This step require a keyboard and ideally a mouse.

@Ashpool said in Dvd roms on PS2 emulator?:

AT mitu, I really adore your ability to keep calm and stay low/calm!)

Ditto

Okay I think I sorted it out.

I edited my xml files to remove any absolute paths and replace them with the old /home/<user>/RetroPie/roms/... equivalent line.
Then I deleted the <folder> lines from the bottom of the file.

Everything works again.

@mitu Spot on - I had to manually update the controls too (select the controller type in PCSX2), but now working completely as before - thanks so much for your help :)

Regards,

The Gent

@Crush said in Request: update pcsx2 install script to show CHD:

(PS: Is this the right place to make such requests?)

Yes, thanks for bringing this up, we'll add the extension to the ps2 system.

Hi @ExarKunIv and @retropieuser

I tried AetherSX2 with your Retropie-Extra script and unfortunatly it doesn't load on my Pi5. Kernel8 is activated and I already run PPSSPP and Dolphin with XINIT-WM and I got the good bios

here's my runcommand.log

https://pastebin.fr/138616

Now, I'm stuck. Do you know why it won't load?

Actually you CAN emulate the PS2 on the Pi 4, but the speed is abysmal and the legwork required is insane. The tl;dr version of the story is you need to install Windows 10 using Windows on Raspberry and run PCSX2. SOME games run at playable speeds, but not many. Disgaea 1 and 2, Kingdom Hearts 1 and 2, Final Fantasy 10, and Final Fantasy 12 are playable. There are likely more, but those are the ones I've tested.

I recommend you post your splash screen here:

https://retropie.org.uk/forum/topic/29132/splash-screen-ideas-discussion

@norstein said in pcsx2 won't install // unable to locate package pcsx2-unstable:

Maybe installing add-apt-repository should be included in the base installation, since it is used for several packages?

software-properties-common is installed by any *-desktop meta-package, what options did you choose during installation ?

@george-spiggott said in General Duckstation discussion:

Has anyone succeeded at running any games at 2x resolution at a reasonable speed? Even on an overclocked Pi4 doesn't seem up to this. This is certainly an emulator that will grow in usefulness as the capability of Raspberry Pis increase although I think I will probably stick with PCSX Rearmed in the short term.

I have been running a few games (spyro, ff1/2, crash bandicoot, ONE) at 4x res, with 32x msaa at over full speed (Vulkan hardware rendering). My pi4 is overclocked, but pretty much stock RetroPie.

@mitu said in Raspberry Pi 5 Speculation:

I don't think a Pi5 is in the works.

Given the timelines involved with designing and validating new hardware, especially when it involves chip design, we can be very certain that Pi 5 development is quite far along already. I know a Pi employee (jamesh, on the forums) mentioned already ~1 year before the Pi 4 was released that they had a good understanding of what the Pi 5 would be. I'd guess that at this point we're at most ~1.5 years from a Pi 5 release. I would hope to see it already this coming summer, but that may be a bit too optimistic.

Of course, the Pi 4 has still not peaked, since we're still waiting for Pi OS 64-bit, the full KMS video driver and Vulkan support. Personally, though, I believe the Pi 5 will in large part compatible with all the SW development work that's going on now, i.e. they will most likely keep the GPU very similar (at least from an architectural perspective).

It's pretty hard to speculate about what the Pi 5 will look like, but I mostly agree with @george-spiggott. Regarding using A75 cores, power consumption of the Pi 4 is already pretty much at the limit for what's practical when it comes to passive cooling. It's unlikely that they'd increase it further. This makes it challenging to provide a generational performance leap without going down to more dense manufacturing processes (such as 20nm or 16nm). So, I'd expect a process upgrade for the Pi 5. I also believe that at 16nm (and maybe also 20nm?) they will need to make some provisions to be able to keep the 3.3V I/O on the 40-pin header, since the silicon is not 3.3V tolerant. This will add cost and complexity.

My hope for the next Pi is that they're able to alleviate some bottlenecks in the design. It seems like memory bandwidth is lower than it should be, possibly because of internal bus limitations. My guess is that this is one of the reasons the performance of N64 emulation is still quite bad, despite seemingly not being particularly CPU or GPU limited on the Pi 4.