Talk:PS2 Classics Emulator Compatibility List

From PS3 Developer wiki
Jump to navigation Jump to search

Salve, ice age 2 : Require config file to past intro loading screen. what should I do? Help me (Ps2 cfw 4.82 ferrox cobra 7.55 emulator Ps2 Classic. Tranks

SOLVED ~ Editing Issues

Whenever I try to save my changes, the page just loads then blank white screen, stuck at URL http://www.psdevwiki.com/ps3/submit/PS2_Classics_Emulator_Compatibility_List No changes are getting saved beyond that.

  • Hello Sciaa, thank you for using the List.
    • We, the Team behind this wiki, are aware about those problems and we are working to fix this as quick as possible. I decided to protect the Page for editing before there will be more serious problems and damages but thanks for informing this issue. So long this problem is still there, the List is only in "read mode" available. Thanks for understanding - (Roxanne 16th September 2018 - 22:04 CET+1)
  • Sciaa (talk) 21:12, 24 October 2018 (UTC) : I've tested a full page edit; I see the reported issue has been completely resolved and normal editing is back to normal. If allowed, I'll migrate the contents of individual templates (by letter heading) back to the main page of the list.
    • EDIT: Issue is still ongoing if large chunks of text are to be saved/published. --Sciaa (talk) 01:49, 27 October 2018 (UTC)
      • I will need to test something, please don't use the main Page for editing it and please return to each letter Template. I will test something to fix the problems as well. Thanks for understanding (Roxanne 06th November 2018 - 22:04 CET+2)
      • Hey, Roxanne, I suspect what's causing the freezing or stuck up issue when saving edits is using too much {{templates}} on a single page. --Sciaa (talk) 03:50, 23 November 2018 (UTC)


Finished Maintenance

  • While the Design from the Main List keeps unchanged, we moved every Letter into it's each own Templates. While the Main List keeps protected for editing, everyone is allowed to add and/or edit new Game Titles in each Template. When you click on "Edit" right after each Letter, you will get redirected directly to the Edit Page from the Template itself. The huge advantage should be that both the Design keeps unchanged and the List keeps completed while the load times for each Edit should be reduced dramatically. But there is more testing needed. Maybe Sciaa would be so kind to add his "Pending Entries" via this new system. The only disadvantage is that you can't edit several Letters in a row. You have to edit each Letter by it's own (one Edit for "A", one for "B", one for "C" and so on). - (Roxanne 20th September 2018 - 19:55 CET+1)
    • And yes, the 2nd disadvantage is that it can take some time your edits gets displayed on the Main List when you edit a Template. But further testing will show what we can do here. (Roxanne 20th September 2018 - 20:02 CET+1)
    • Thanks, Rox for your update. No Edit Link for each letter list shows for me yet. (Sciaa)
      • They are the same Link right after each Letter.
      • No edit link after each letter -- even after I logged out and logged back in. -Sciaa
      • Ohh! Okay, I get it now. One has to do "View Source" > Expand "Templates used on this page" > Click "(edit)" beside "Template:PS2 Classics Emulator Compatibility List/(letter placeholder).
        • There is no need to go to „View Source“. Just use the „Edit“ Link right after each Letter from the Main List.
        • I still don't have (even now) that "edit" link after each letter from Main List so I had to use View Source. Maybe when all's back to normal. -Sciaa
          • And now ???
      • Oh no, the changes I made to "W" template (Way of Samurai and Way of Samurai 2) does not reflect on the "main list" page. -Sciaa
        • It seems that it can take up to roughly 12 hours. My edit from yesterday 8 pm is now on the Main List as well.
        • My Way of Samurai edits are now showing so yes, shows there's some delay for now. -Sciaa
          • Good to hear.

Changes 2021 july

I have some ideas for a few upgrades (practical and visual) related with the compatibility lists that affects several pages, are a lot of small details and i guess some of you will want to discusss them incase i missed something that coould be problematic or if you want to do some critic or suggestion. Later i will make a complete list of changes here to discuss them. I would like some agreement before starting doing the changes, if i dont see any feedback i will consider all you agrees with the changes--Sandungas (talk) 08:51, 16 July 2021 (UTC)

  • I my honest opinion, it would be more important to remove all the wrong and double titles and to clean up the list instead of changing it by design. Roxanne (talk) - 16th July 2021 - 16:51 GMT+1
    • I agree that {{Unplayable}} needs another color font but I recommend to make it white like it is for {{ps2classics}}
      • The Flagonly edit is good but I don't understand the changings for your "Jumptoletter" edits.
        • {{untested}} won't help much since people tend to add templates only for Games/Regions they also tested.
  • Im not sure what you mean, ive seen agrippa doing some changes related with the double titles and the style he is using is fine imo, i dont see any problem with it and i dont have any better idea to deal with it. The changes im proposing are unrelated with that, unless you want to propose some kind of rowspanning but that could be problematic for the sorting feature i added and confusing for wiki editors newcomers--Sandungas (talk) 16:31, 16 July 2021 (UTC)
    • {{unplayable}} and {{majorissues}} have the colors inverted with each other, and both uses a border that represents the state "pressed" because both are intended to represent something negative
      • Not sure if you mean the latest edits i made to the template {{jumptoletter}} or the whole purpose of it. Regarding the purpose, the initial goal was to clear-out the bottom of the tables. This way the wiki editor newcomers are going to find a lot of non-understandable stuff at top but the bottom of the table will be very simple. The first requirement was to use an argument to highlight the current page section but later i improved it a lot more because i realized it can be used in many other pages like: {{Template:PS2_Classics_Emulator_Compatibility_List}}, {{Glossary}} or other pages i could be missing and/or could be created in the future, also is intended to be used in all the other compatibility list pages for PS1, PSP, etc...
        • Let me try to show the problem first and try to think in reverse way, the question marks in the table cells are a problem, not only because they breaks the visual style, but mostly because doesnt represents anything at all, are exactly the same than keeping the cell empty, ive seen you made a template {{?}} to try to center the question mark a bit and give it a color but thats not enought imo because is just something visual, the root of the problem (not representing anything) is still there. I think the solution is to use the {{untested}} because it means that """The game was released for this region but nobody tested it""". In other words, is not intended to help the wiki editors, is a new requirement, everytime someone adds a new game he/she should take the effort to google and find for which regions was released and fill the table as a minimal with either {{untested}} or {{notavailable}}. Just to show you an example of what we can do with it, the other day i was checking for how many regions was published all the games from the # section and i know i could replace all the question marks from the # section by {{untested}} because i know the games was published for that regions, also note there was many notes at right that was telling "untested" and i had to add some more notes with the text "untested", and that was not practical, with the new template {{untested}} we could delete that notes with the texts "untested" at the right
  • As I said I don't like those ideas personally but I'm the last one here to block any new ideas etc., especially not since I don't maintain at this wiki anymore on a regular basis. If you feel comfortable with it, go on but I had other views in this list. - Roxanne (talk) - 16th July 2021 - 21:16 GMT+1
    • Regarding the "untested thing", this is what I mean. First we need to "clean" every Title on the whole lists which I know is huuuuuge work to do. But still who is interested when wants to add a Game to check if that Game got released in other regions or not or even if so, who is interested to test a Game from all three versions. If you check the changes in it's list, then you will recognize that only a very small amount of edits contains new entries for a Game, which got tested for two or even all three regions. Every other edit only contains a edit or a new entry for only ONE region mostly.
      • Aah now I see the difference in "jumptoletter", but still don't like it, sorry.
        • Oh btw the ? template wasn't created by me. It already existed before on PS4 wiki for other purposes.

I have been cleaning up the list for weeks. First of all, I want to remove the double/triple entries of the same games. I am following the hints Roxanne has posted some years ago on the PSX-Place. But I have restricted the brackets to the different revisions of the game (for example, MGS 2 Substance). The names for the different regional releases (or written in Japanese script), I am putting as a smaller, italic font below the first one (someone has started doing that already on the list). If the game is made by a Japanese developer and released worldwide, I am putting the Japanese name in the notes section. Second of all, I want to get rid of all external links in the notes section, because we have got a link to the aldostools database here. Third of all, I want to remove every "None" in the notes section too (or such words, like a "working", "without problems", etc.). Regarding the changes, I am not sure if they are conspicuous enough to the reader. --Agrippa (talk) 01:07, 17 July 2021 (UTC)

  • One tip from me I didn't listed in the PSX-Place Thread: When a Game is both released for PAL and NTSC but with different naming for both region, I always have chosen that region as a first where the Developer is also deployed and/or where the Game was released first. Bully is a good example here again since Rockstar Games is a American Developer, so I listed it on "B" and not on "C" for the PAL name. - Roxanne (talk) - 17th July 2021 - 12:45 GMT+1
    • I have been following this one accidentally, looks like. It is a good point to note too. I am not sure if the {{untested}} thing is needed. The "?" does the job for me. Changing the font colour of the {{Unplayable}} from black to white is a good idea.--Agrippa (talk) 12:35, 17 July 2021 (UTC)
  • Take a look at what i did here with the new template {{jumptoletter}}, the previous revision of the page had the same block of text repeated one time for every section (it was not doing the highlight in red for the current section), so this edit is an improvement, and it can be made in a relativelly simple way (i used the search-and-replace feature of notepad++), an small detail consequence of it is the bottom of the tables looks more simple, and as a bonus i reduced the page size in -12312 characters. The other edit i made here is because the template was designed to be used in it, i wanted to show you the results, is not like a huge revolution because visually and practically looks almost identical for wiki readers--Sandungas (talk) 13:07, 17 July 2021 (UTC). I decided to update the PSP page too, it was tempting because it had some minor problems and was relativelly easy to do, im not going to do it with CFW2OFW Compatibility List yet because is too much crowded, and im not going to do it either with the PS2 Classics Emulator Compatibility List because is needed to add more settings in the table headers to achieve the "3D" border effects im using in the guinea pig tests, probably i would need to talk about that borders later, but by now keep attention at how i configured the width and text alignments in the table header, is actually solving a problem of incorrect syntax (hard to explain, but there are attributes overriding each others in a nonsensic way imo), the way im doing it in this edit is more simple and the result is the same, unless im missing something... this way with a simple {| class="wikitable mw-datatable" style="font-size:85%; width:100%;" is better--Sandungas (talk) 15:19, 17 July 2021 (UTC)
    • Aah now I get it. Ok this makes things easier, although I don't like the visual design now abd I prefered the older one but this is again only me I guess. - Roxanne (talk) - 17th July 2021 - 19:41 GMT+1
      • About what visual design are you all talking about? Do you mean that "guinea pig" table below?--Agrippa (talk) 22:52, 17 July 2021 (UTC)
      • I guess she means the location of the "back to top" link but i think we agree at this point that location can be considered a minor detail that doesnt matters much, actually at some point back in 2017 we was displaying it in the same way im proposing now, with the "back to top" located at the right of the "Z". Also think in it this way, https://i.imgur.com/9s2YzIj.jpg from a practise point of view the old style had the row of letters and the "back to top" separated but very close to each other it was just a matter of moving the mouse a bit up or down so is not much diferent... but it makes sense to have all the "page navigation links" in the same bar with the new template {{jumptoletter}}, visually is fine, and is intuitive too--Sandungas (talk) 16:20, 19 July 2021 (UTC)
    • I was waiting for an agreement about using the template {{jumptoletter}} in the PS2 compatibility list but i cant wait indefinitelly, i been implementing it in the other compatibility lists for tests, works and looks fine so i did it for the PS2 compatiblity list too, now all the compatibility lists (ps3 domain) are using it, and one of the "legend" floating templates for PS1 (the other for PS2 is not using it yet) and i will make a new one for PSP to do some tests--Sandungas (talk) 12:40, 21 July 2021 (UTC)
  • Initially i was thinking in doing most of the related changes im proposing (after convincing you) in a single edit or a couple at most, but i changed my mind about it, is better to do the changes in steps because this way is easyer to see why im doing every change, next thing im going to do is to "fix" the text alignments in {{official}}, {{playable}}, {{majorissues}}, {{minorissues}}, {{unplayable}}, {{notavailable}}. If you take a look at the code you are going to realize whoever that made them was trying to align the texts to center, but is not working because all texts are displayed aligned to left inside the table cells. What im going to do first is to use a guinea pig template named {{ps2classic}} where im going to fix that problem, to add 2 more features i imagined yesterday (i want to be able to use them also "inline" in between standard texts outside of tables, and maybe i will also include a "abbr" text to add more info hidden), and im going to add also the settings required to generate that cool "3D border" visual effect--Sandungas (talk) 13:13, 21 July 2021 (UTC). The new template PS2 Classic--Sandungas (talk) 17:26, 21 July 2021 (UTC)
  • Agrippa, i dont like either the "None" texts at right of the tables (take a look at the PS1 compatibility list to see how it looks when used massivelly), but the problem we have is we need to dislpay something inside the "notes" table cell, otherway if we dont display anything it looks like nobody cared about that game, so what do you think about this new {{worksfine}} ?, is just a test, feel free to change the texts, colors, whatever, consider it is your guinea pig. It needs to be something generic in many ways, if you have other ideas about what to do with it let me know--Sandungas (talk) 17:26, 21 July 2021 (UTC)
    • Ok, I am still a begineer when it comes to the Wiki, I do not want to discuss a code issues therefore. But I am fine with the "jump to letter" changes you made. They are very good in my opinion and they do look better indeed. About the other suggestions:
  1. Yeah, the alignments have to be corrected to the center. And the Unplayable's font changed to white.
  2. I am not a fan of the "3D border" effect. It is just not convincing me at all in that guinea pig table.
  3. I do not think that we have to use a generic note that everything works fine. When the game is listed as a playable, it does mean to me that it works without a problem (as explained in the template at the top). When there is an issue, we add it into the notes column.
  4. I have a mixed feelings about the new PS2 Classics template. While it is well done and cute, that violet background does affect the clarity of the list. I mean, that saturated green does show the game is very playable, because officially released by Sony.--Agrippa (talk) 23:06, 21 July 2021 (UTC)
  • I just realized about a detail related with the location of the {{jumptoletter}} navigation bar. In few words, is going to be a lot more useful if we locate it at top-right corner of the tables (in the way im doing it in the guinea pig in this edit). The point is... try to do this sequence of actions: 1) Load the page for first time, so you are at most top 2) click in the link to the "T" section 3) Now try to click in other link of the navigation bar... oppps you need to move the mouse whell, damnit. The goal of locating the navigation bar at top-right corner is because we will have the bar always visible everytime we click in a new letter, so we can navigate the page by clicking multiple times in it without using the mouse whell (thats a great feature for lazy dogs). To be fair i have to say that the previous location of the "back to top" link at top-right corner was fulfilling that purpose (but i didnt realized about it so i was not taking it into consideration), and in some way i broke it when i moved the "back to top" link to bottom. But i was trying to be practical from the point of view of how the mediawiki markup/code was written, i was trying to simplify it, and what im suggesting now is also for practical reasons because i think is going to work great and is an improvement (in comparison with the previous table style used some weeks ago at top-right corner of the tables there was only a "back to top" link but no links to other page sections). Also, if we locate the navigation bar at top-right corner it makes redundat the other navigation bar located inside the Template:PS2 Classics Emulator Compatibility List. Think in it while taking a look at the page, if we relocate the navigation bar at top-right corners of the tables we are going to have the navigation bar from letter "#" visible since the first time we load the page. Btw roxanne, do you mind if i rename the template Template:PS2 Classics Emulator Compatibility List to Template:PS2CompatListLegend ?, im asking because we have 2 more in the collection of templates that are "children" of the compatibility lists, Template:PS2CompatListCounter and Template:PS2CompatListHeaders and im trying to follow a shorter naming convention--Sandungas (talk) 18:19, 26 July 2021 (UTC)
  • Please take some time to consider the problem im trying to explain in this edit related with the new template {{available}} im proposing to solve it. If at some point someone starts trying to complete the "availability" of some page sections in the same way i did in this edit with the games from the # section (in other words, without doing any test, just by googling) you are going to realize is a bit frustrating because there is some info (the existence of an untested game game for a specific region) that cant be represented in the actual compatibility lists. I added a couple of tables at bottom with examples from "real world" cases where it can be seen that by adding only the {{notavailable}} is not good enought because it leaves some room for speculation (the options 1 or 2 from the "Notes" column are the kind of deductive process most readers are going to do) but if we add the {{available}} then there is no room for confusion and allows to remove the weird {{?}} (hint: the {{?}} doesnt means anything, are pointless). The only reason why i decided to use the {{?}} temporally was because are configured with the data-sort-value="8", i needed it as a test to check that the new sorting methods was working fine, but in long term all the {{?}} needs to be replaced by other tags, and one of the good consequences of what im proposing by using the new {{available}} is that we can replace all them right now without need to do any test, the only thing needed is... time, pacience and care to check for how many regions was published every game in this link ---> https://wiki.pcsx2.net/Category:Games or https://wiki.pcsx2.net/Complete_List_of_Games. You know... as a minimal we can replace every {{?}} by either a {{notavailable}} or a {{available}}--Sandungas (talk) 02:25, 29 July 2021 (UTC)
  • As probably some of you noticed in my previous edits of the last days related with the compatibility lists i didn't changed any color of the "tags" that are actually in use, either in the tables themself of in the "legend". But now everything is ready to start implementing some changes that affects the colors. Long story short... i been playing around latelly with 4 different ways to applicate colors to the tags: "background color", "font color", "font shadow color", "border color". The only color changes im going to do now are the background color of the "PS2 classic" (background from green to blue), and the "notavailable" tag (background from lightgrey to darkgrey, and font to lightgrey), im going to update the hidden descriptions in the tags, update the "legend", implement also the new "counter", replace all the apparences of "official" by "ps2classic" and add some examples about how to use the new "available" in the compatibility list--Sandungas (talk) 20:53, 1 August 2021 (UTC)
    • As I said before, I am not a fan of the blue PS2 Classic tag. There is no need to introduce another "available" tag. There is a need to update the region exclusive games to lessen the amount of "?".--Agrippa (talk) 22:27, 1 August 2021 (UTC)
    • The "white logo/text on top of blue" is the design used by sony in the cardboard box of some PS1/PS2/PS3/PS4/PS5 bundles, and also in the PlayStation Store. In this case im using it to represent the store, i even added an icon with the white bag in the "tag" for the most noobs that doesnt understand what means the name "PS2 classic" and the cosequences of being labeled that way (it represents the best compatibility), in some of the experimental versions i was even adding a link to the official store just to be even more explicit but i remove it at some point because i thought it was excesive, anyway, i think the {{ps2classic}} represents very well that it was published in the store. The {{available}} is an improvement for the wiki reader because allows to give info to the reader that it was not posible to give before, is also intended to delete all the notes at right with the sentence "Untested", and in long term is a {{?}} killer--Sandungas (talk) 02:10, 2 August 2021 (UTC)
      • The "available" tag is not obvious to the reader. It has to be named just "untested". Its background has to be little more brighter, the same as the "?" sign tag in my opinion. Similarly, the "notavailable" and "available" fonts are not clear to me. I think we have to change the meaning of the "playable" tag. It has to be like the PCSX2 one equivalent and as the name itself does suggest - playable from the start to finish. Now, it is described as a "Works perfect without any noticeable error." Unfortunately, very few games are playable perfectly without any noticeable error. And never will be. Even the Sony released PS2 Classics have got a imperfect workarounds, just like slowing down the game to get rid of the jitter. When it comes to the new template, I think adding a symetrical grey table at the bottom to include the resource links would improve a look in my opinion. Just like expanding the width to equal the list's headers below.

Compatibility lists dependencies

Tags tests

  • This is the whole collection of "tags" related with the compatibility lists that has been modifyed latelly or are a candidate to be modifyed



Template:PS2CompatListCounter

  Playable  

Guinea pig tables

# · A · B · C · D · E · F · G · H · I · J · K · L · M · N · O · P · Q · R · S · T · U · V · W · X · Y · Z · Back to top
Logo PS2.png Game Name Europe.pngPAL-EU United States.pngNTSC-U/C Japan.pngNTSC-J Logo PS3.png Compatibility Notes
{{ps2classic}} Store logo mini.png PS2 Classic Template:Official PS2 Classics
{{ps2classic}} Store logo mini.png PS2 Classic Template:Official PS2 Classics
{{playable}} Playable Playable Playable Template:Worksfine
{{playable}} Playable Playable Playable Template:Worksfine
{{minorissues}} Minor Issues Minor Issues Minor Issues
{{minorissues}} Minor Issues Minor Issues Minor Issues
{{majorissues}} Major Issues Major Issues Major Issues
{{majorissues}} Major Issues Major Issues Major Issues
{{unplayable}} Unplayable Unplayable Unplayable
{{unplayable}} Unplayable Unplayable Unplayable
{{available}} Available
(but untested)		 Available ?
{{available}} Available
(but untested)		 Available ?
{{notavailable}} Not Available Not Available Not Available
{{notavailable}} Not Available Not Available Not Available

The problem... {{?}} Template:PS2CompatListHeaders |- | 007 - Quantum of Solace || class="compatibility-tag"style="background:#9d9;color:#05b;box-shadow:2px 4px 6px hsla(0,0%,99%,.5)inset,-2px -4px 6px rgba(0,0,0,.2)inset"data-sort-value="1"title="Works perfect without any noticeable error."|Playable || style="background:#efefef; text-align:center;" data-sort-value="8" title="UNKNOWN. Please input data when possible" | ? || style="background:#efefef; text-align:center;" data-sort-value="8" title="UNKNOWN. Please input data when possible" | ? || Option 1) The person who added the {{playable}} for PAL region forgot about adding info for the other regions
Option 2) The game was published only in 2 regions, so one of the {{?}} needs to be replaced by a {{notavailable}}
Option 3) The game was published in the 3 regions, but the way how the actual compatibility list works doesnt allows to indicate it because the {{?}} doesnt gives any help to the reader |- | 7 Wonders of the Ancient World || style="background:#efefef; text-align:center;" data-sort-value="8" title="UNKNOWN. Please input data when possible" | ? || style="background:#efefef; text-align:center;" data-sort-value="8" title="UNKNOWN. Please input data when possible" | ? || class="compatibility-tag"style="background:#ddd;color:#888"data-sort-value="9"title="Not released for this region."|Not Available || Option 1) The person who added the {{notavailable}} for NTSC-J forgot to add another {{notavailable}} in one of the other regions. The game was published only in 1 region
Option 2) The game was published in the other 2 regions, but the way how the actual compatibility list works doesnt allows to indicate it because the {{?}} doesnt gives any help to the reader |} And the solution... {{available}} Template:PS2CompatListHeaders |- | 007 - Quantum of Solace || class="compatibility-tag"style="background:#9d9;color:#05b;box-shadow:2px 4px 6px hsla(0,0%,99%,.5)inset,-2px -4px 6px rgba(0,0,0,.2)inset"data-sort-value="1"title="Works perfect without any noticeable error."|Playable || style="background:#cccccc; color:#777777; text-align:center;" | Available... || style="background:#cccccc; color:#777777; text-align:center;" | Available... || This way indicates explicitly that the game was published in the 3 regions... but nobody tested 2 of them |- | 7 Wonders of the Ancient World || style="background:#cccccc; color:#777777; text-align:center;" | Available... || style="background:#cccccc; color:#777777; text-align:center;" | Available... || style="background:#777777; color:#cccccc; text-align:center;" | Not Available || This way indicates explicitly that the game was published in 2 regions... but nobody tested them |}

Guinea pig legend

  • Changes
    • Navigation bar removed, because we can access it from the top-right corner of "#" page section
    • Link to this discussion removed because is something temporal
    • I think is better to use a width different than 100%... just to difference it from the other tables of the page... lets say 95% or 90% is fine, i dont mind the exact value
    • The "Resources" text line at bottom is intended to add as many links as needed, there is no limits, feel free to add more, but try to short them
    • I need to short the first line of the description to 72 characters max in inline mode (and 95 in table mode)... because that same text line is used in the "tag" templates as hidden text
Other compatibility lists: PS2 Classics Emulator Compatibility List (on PS4), PCSX2 Complete list of PS2 games (on PC)
Resources: PS2 CONFIG Database (aldo), PS2 Widescreen patches archive (devina)
Emulation on PS3 (talk) · PS1 Emulation on PS3 (talk) [Compatibility list] · PS2 Emulation on PS3 (talk) [Compatibility list] · PSP Emulation on PS3 (talk) [Compatibility list]
PS2 Classic  Syntax for wiki editors: {{ps2classic}} Released for the PS3 at the PlayStation Store, the compatibility is certified by sony.
It works exactly like when you play it on a real PS2 Console, the compatibility is the same than {{playable}}.
Playable  Syntax for wiki editors: {{playable}} Works perfect without any noticeable error.
It works exactly like when you play it on a real PS2 Console, the compatibility is the same than {{ps2classic}}.
Minor Issues  Syntax for wiki editors: {{minorissues}} Framerate problems, audio/video desync, or other small and non-critical innacuracies.
It works fine and can be completed without any huge disadvantages for your gaming progress, the compatibility is very close to a {{playable}}.
Major Issues  Syntax for wiki editors: {{majorissues}} Very low framerate, screen flickering, glitched graphics, or some non-critical broken functions.
It just works but not good enought, it will be a pain for your gaming experience, the compatibility is far away from being {{playable}}.
Unplayable  Syntax for wiki editors: {{unplayable}} Critical problems, doesn't boots, freezes or crashes after some gaming progress.
It doesn't works and/or can't be completed because there are some critical problem at some point that doesn't allows to continue gaming.
Available  Syntax for wiki editors: {{available}} Released for this region, but nobody tested it.
This tag is intended to be used temporally to indicate the existence of the game for an specific region but with an unknown compatibility.
Not Available  Syntax for wiki editors: {{notavailable}} Not released for this region.
This tag is intended to be used in the regions where the game wasn't released, e.g: [PAL-EU] & [NTSC-U/C] of a game released only in Japan.
Retrieved from "http://www.psdevwiki.com/ps3/index.php?title=Talk:PS2_Classics_Emulator_Compatibility_List&oldid=60943"