search

libretro / LRPS2

GNU General Public License v2.0
159 stars 47 forks source link

PCSX2 works itself but not in Retroarch (EDIT: SSE4 required for now) #247

Closed albertto56 closed 1 year ago

albertto56 commented 1 year ago

Hi.

I can run PS2 games without any problem directly from the PCSX2 emulator (stable version 1.6.0), but when I try to execute them from Retroarch, it shut down. All the directories in system folder are ok, so I don't know what's happening.

Here there's attached the log file.

Regards.

retroarch2022_12_2920_50_16.log

worst001 commented 1 year ago

the same

LibretroAdmin commented 1 year ago

I think newer versions of PCSX2 (as in, newer than 1.6.0 stable, which this libretro core is) need SSE4 as a mandatory feature on your CPU. The Phenom CPU in your log seems to not have that.

I don't know if over time we can make SSE4 optional. But for now it seems to be required else it will not run. It'd be interesting to do though since it would differentiate LRPS2 well from PCSX2 with increased backwards compatibility.

albertto56 commented 1 year ago

Maybe there's an early LRPS2 libretro core based on PCSX2 1.6.0 version that works with SSE2 ? I could test it on my computer...

P.S.: You should change the core info doc.

LibretroAdmin commented 1 year ago

my processor has SSE4 support and even so when starting the game the retroarch closes by itself

What CPU? It might still not have SSE 4.1 and/or SSE 4.2. Or for all we know you just don't have all the required BIOS files and it has nothing to do with this particular issue.

Again, it's a mistake to come in here and go 'oh I have the same issue too', when it might as well not be the same issue and when there is a lack of information being provided (and a lack of logs). What is being described here can be several unrelated issues.

We need far more thorough bug descriptions in the future. For now, closing this since all it does is cause confusion (and having a non-SSE4 codepath right now is not a priority, it might be in the future, right now there are more pressing issues at hand).

From now on we need way more thorough bug descriptions, with specs from your system, a log file if preferable, etc.