Bureaucrats, ninja, Administrators
67,564
edits
User talk:Ngng: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1,517: | Line 1,517: | ||
Examples it can range from shaking screen to problems with the texture to even the lightning. It's just to make it more obvious that [Not an issue] means that the user should ignore it because it's nitpicky but the 2nd meaning is that they have to change some settings. To give a situation: User has problem with a car game where the lights are broken, for the developers there is a workaround and is not deemed a bug, the only thing you have to do is change a setting like skipdraw or an upscaling fix or whatever but if he skims through it for him the issue is not fixed and is pretty major but either sees [Fixed] or [Not an issue]. That's why i want to separate it that [Not an issue] can mean two totally different aspects. | Examples it can range from shaking screen to problems with the texture to even the lightning. It's just to make it more obvious that [Not an issue] means that the user should ignore it because it's nitpicky but the 2nd meaning is that they have to change some settings. To give a situation: User has problem with a car game where the lights are broken, for the developers there is a workaround and is not deemed a bug, the only thing you have to do is change a setting like skipdraw or an upscaling fix or whatever but if he skims through it for him the issue is not fixed and is pretty major but either sees [Fixed] or [Not an issue]. That's why i want to separate it that [Not an issue] can mean two totally different aspects. | ||
:I really tried to understand this, but I can't. As a surmise, are you tring to say that definition of non-issue is too broad right now and we should define what kind of "issues" should fall into this category? I can only agree with that, I just couldn't do it myself because of the reasons stated above. As far as my wanted it to be from the start: | |||
* An issue is an undesirable game behavior which manifests itself with the default PCSX2 settings. The only settings changed from their defaults should have more compatible values (for example, full clamping instead of normal clamping). An issue should also be absent on the original PS2 hardware. | |||
** A major issue prevents a game to be playable, completable or manifests itself as a crash of the emulator. This issue is often cannot be worked around (unavoidable). | |||
** A serious issue detracts/distracts from the game experience in a way that may completely ruin its enjoyment. This issue may have a workaround. | |||
** A minor issue is any other issue that "may annoy but never frustrates", or it could be a small visual artifact of no significance. | |||
* An "non-issue" aka "note" is either a known game bug replicatable on the original PS2 hardware and stated here with workaround for users' convenience or an issue that is caused by a PCSX2 misconfiguration but commonly used without problems on other games. | |||
:As for examples, I may not call this recent [https://wiki.pcsx2.net/index.php?title=Amplitude&curid=133&diff=95291&oldid=87226 issue] an issue at all (isn't full boot should be a default way to play?), but I didn't change it. Plus there's a problem with DirectX vs OGL and hardware vs software. People create issues active only in DirectX, but shouldn't they play in OGL by default or are DirectX issues also helpful? Same with hardware mode issues -- are they legit? | |||
:I'd accept PCSX2 team decision here, if you have time, please address these questions to them. Although in my opinion every definition should be allowed for some leeway (we're not enforcers and not in the army here). --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 19:43, 30 August 2020 (UTC) | |||
== Dividing Chinese language in the infobox into Simplified Chinese and Traditional Chinese == | == Dividing Chinese language in the infobox into Simplified Chinese and Traditional Chinese == | ||
| Line 1,527: | Line 1,536: | ||
Regards, [[User:SiuMing|SiuMing]] ([[User talk:SiuMing|talk]]) 04:17, 30 August 2020 (UTC) | Regards, [[User:SiuMing|SiuMing]] ([[User talk:SiuMing|talk]]) 04:17, 30 August 2020 (UTC) | ||
:Howdy! It's nice to see someone from the region with the less accurate data on the wiki. It's really hard to find a source of a good Asian PS2 info, I tried to complete and correct Korean data from the official Sony site, made a lousy job no doubt, but it's ever harder with Chinese. | |||
:There's no separate Chinese regionbox template in the infobox, all Asian serials go to the NTSC-J regionbox (so no separate Taiwanese+Chinese). A separate template is relatively easy to add, but I'd advise against it for two reasons: (1) there aren't too many PS2 game titles with Traditional Chinese support to warrant its own regionbox (correct me if I'm wrong here) and (2) We could also add many more regions like Australia (different but compatible PAL type), Korea (NTSC-K), Brazil (PAL-M), even some European countries (like PAL-G, etc.), this would make it a fine mess. The current system is simple: North America (NTSC-U), Asia (NTSC-J) and the rest of the world (PAL), I'd like to keep it that way. | |||
:Nevertheless, we can correct region box caption to address your concerns, so instead of "Region: NTSC-J" it would say "Region: NTSC-J/C/K" or "Region: NTSC (Asia)". Each serial can have a note (like this [[LuluRara vol.2: Powered by Ziller.net|Korean only title]] has notes "(Korea)"). What say you? --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 19:43, 30 August 2020 (UTC) | |||