You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Taking a look at xemu's current compat rating system, a large sum of the titles land in the "Playable Category" which isn't incredibly telling when it comes to how "Playable" a title is, I'd like to revise the project's current rating system to have an "Almost Perfect" or similar naming scheme for a segment of playable, that isn't "Perfect" but is "damn near close". I've played around 100 games on the emulator at this point and I can definitely say there are titles that are very very very close to perfect, with rather minor graphical or sound glitches that with our current rating system would land in playable, however it performs amazingly.
Incredible Hulk: Ultimate Destruction is such a title, I have more that aren't coming to mind, however this game runs amazingly, only lands in playable because of skybox flickering, and a slight graphical bug in the pause menu, cutscenes. however it runs at around 0-1 mspf, and with an uncapped framerate will run at near 400 fps on my gt710 system on w11 21H2.
I don't mind to do all the Backend PRs required to implement this.
The text was updated successfully, but these errors were encountered:
Taking a look at xemu's current compat rating system, a large sum of the titles land in the "Playable Category" which isn't incredibly telling when it comes to how "Playable" a title is, I'd like to revise the project's current rating system to have an "Almost Perfect" or similar naming scheme for a segment of playable, that isn't "Perfect" but is "damn near close". I've played around 100 games on the emulator at this point and I can definitely say there are titles that are very very very close to perfect, with rather minor graphical or sound glitches that with our current rating system would land in playable, however it performs amazingly.
I don't mind to do all the Backend PRs required to implement this.
The text was updated successfully, but these errors were encountered: