compat.cc: Revise Compatibility Rating System #1915
Conversation
| "Perfect", | ||
| }; | ||
|
|
||
| const char *playability_descriptions[] = { | ||
| "This title crashes very soon after launching, or displays nothing at all.", | ||
| "This title displays an intro sequence, but fails to make it to gameplay.", | ||
| "This title starts, but may crash or have significant issues.", | ||
| "This title is playable, but may have minor issues.", | ||
| "This title starts, but may crash, have significant issues, or be unplayable.", |
There was a problem hiding this comment.
Rather than "starts", maybe "makes it past any intro sequences"?
I can imagine that the difference between "intro" and "starts" could be subtle for folks who don't use English as their primary language. I wonder if there's much value in differentiating between "it shows a movie but you can't play" and "it gets to the main menu but you can't play"?
There was a problem hiding this comment.
I've honestly never really been super partial to "intro" and "starts" as they seem pretty synonymous with one another in general.
I'd possibly like to possibly rework those... but I will take your comments under advisement
There was a problem hiding this comment.
"In-game" is commonly used for other emulators' compatibility ratings, and is the equivalent to "Starts" for Xemu. It should be understood as "It goes in-game, but is not particularly playable due to performance issues or bugs that prevent progression".
| "This title starts, but may crash or have significant issues.", | ||
| "This title is playable, but may have minor issues.", | ||
| "This title starts, but may crash, have significant issues, or be unplayable.", | ||
| "This title runs but has noticeable issues, graphical, audio, or performance issues that may affect gameplay.", |
There was a problem hiding this comment.
nit, I think you can remove the first "issues," and just say "noticeable graphical, audio, or performance issues".
I wonder if "significant" might be better than "noticeable", since the new "Almost Perfect" would also mean that at least one issue was noticed.
There was a problem hiding this comment.
Yeah, didn't notice the doubling of words there. Will fix.
There was a problem hiding this comment.
Also, yes. Makes sense on the second part, "Almost Perfect" would delineate very minor issues, like flickering elements such as a skybox, or just a slight audio crackle, or whatnot that honestly doesn't impede gameplay or performance, just is a minor annoyance or deviation from how the game plays on hardware.
| "This title is playable, but may have minor issues.", | ||
| "This title starts, but may crash, have significant issues, or be unplayable.", | ||
| "This title runs but has noticeable issues, graphical, audio, or performance issues that may affect gameplay.", | ||
| "This title is playable with very minor graphical, audio, or performance issues.", | ||
| "This title is playable from start to finish with no noticable issues." |
There was a problem hiding this comment.
Should we try to clarify that "start to finish" means that the game can be fully completed with no issues? I.e., if you choose to finish after 10 minutes, you should not submit a "Perfect" report.
There was a problem hiding this comment.
I agree, this was just a baseline of the general idea I had, comments/criticisms are encouraged!
I do think that perfect, and possibly (almost perfect) do need a higher barrier of playtime to be classified as that. Almost perfect being maybe not 100% completion but more than 10-15 minutes of game time. Pretty hard to quantify how playable a game is in that span of time.
|
I think before doing something concrete I'd like to get Matt's perspective, it may honestly be worth revisiting intro/starts like mentioned previously due to how similar they are rating wise. It'd be nice if we considered possibly finding a way to store asserts to report in compat reports... but given previous discussions today I could just see forgoing this for just sending reports out and possibly webhook creating github issues for asserts with titles that have those issues. But that's just me spitballing |
Depends on xemu-project/xemu-website#177 , fixes xemu-project/xemu-website#176