Xbox 360 and PS3 emulators are still borderline unusable on my new-ish PC. They're slow, glitchy, and/or hard to set up. Related to what the other commenter said, anyone who says these are good must have a lot of time to deal with it, whereas I just want the equivalent of sticking the disc into the console.
GameCube is the newest thing I've had a decent experience emulating, and even that isn't 100% unless it's Melee with the Slippi optimizations (n.b. did not try DS or Switch).
Oh sweet, thanks for the link. It sounds like it was harder getting things running on the XB1's tiny CPU vs running an emulator on monster dev machines, no surprise there! :-D
Hands down my favorite thing about my time at microsoft as an intern was just a random brown bag lunch with the engineers who did the powerPC emulator for xbox360 games on xbox one. It was an incredible talk and they went deep and were happy to answer questions.
I wonder about that too. New console supports only a subset of 360 games somehow, and with different enhancements.
The 360 could also play original Xbox games without much exception, but it was noticeably slower than the original. Halo 2 on 360 has a shorter render distance.
If you want to emulate a current console, try emulating the switch. I haven't looked into it much, but apparently it works better on modern hardware than on the switch itself. Not surprising given the switch aging hardware and power limit.
But the supposedly working Switch emulators only have experimental Mac support at best. Also idk if the CPU arch is really the hard part in general... we never got an Xbox 360 emulator for PPC Mac ;)
It's really surprising then that you had such a bad experience with PS3 emulation specifically at least, the i5 9400F was a go-to recommendation there for a very long time, basically ever since that processor's release (6 years ago).
It was in last August they bumped their system requirements to the i5 10400F. Nearly all of the games marked "Playable" in their compatibility list should be plug-and-play territory, with mint performance.
What were the games you tested with classified as? Did you try to seek help on their community space(s)?
I didn't try reaching out, I just wanted to play Shrek Forever After (for a very random reason) and gave up after 5 minutes of choppiness. Like I said, there's probably a fix, and I appreciate that there's community support, but I simply didn't have time. Especially because on the PS3 side, this was after waiting a while for RPCS3 to do its pre-run caching.
Given that game has been marked "Playable" years before your CPU has seen its initial release, and that there are no notes on its Wiki page, I'd expect it to run essentially perfectly out-of-the-box, short of some regression causing issues.
You should give it a retry sometime if you can / want to. That said, I should probably let you know that the community can be slightly hostile, and they will ask you do the legwork if it's not a misconfig but a suspected regression (they'll want you to bisect the build where the choppiness appeared). You'll also want to run the topic by the volunteers in the #help channel on their Discord before opening an issue ticket on GitHub, as their GitHub issue tickets are not for support, only for actual issue / feature request tracking.
GameCube is the newest thing I've had a decent experience emulating, and even that isn't 100% unless it's Melee with the Slippi optimizations (n.b. did not try DS or Switch).