User talk:Ngng: Difference between revisions

Jump to navigation Jump to search
12,693 bytes added ,  6 September 2020
m (Example of Not an issue)
(17 intermediate revisions by 3 users not shown)
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 ==
Hi Ngng,
I have recently joined this wiki but I used to edit other wikis outside PCSX2. I found that the language secction in the [[:Template:Infobox|infobox]] only have a single Chinese option instead of both Simplified Chinese (mainly only available in NTSC-C titles) and Traditional Chinese (mainly available in NTSC-J titles). Therefore, I would like to suggest adding two more language options (Simplified Chinese + Traditional Chinese) in the infobox, and deprecate the old Chinese value after all the games with this value has been changed.
I can change it myself but since you were the creator of that infobox, I would like to ask whether you have any concerns or I should not do this. I can provide more details if necessary as I have collected a few titles from these 2 languages/regions.
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)
::I suggest only separating NTSC-C out from NTSC-J, and keep others like you said. The main reason the actual region-lock implemented on PS2 console. i.e. An NTSC-J machine cannot play NTSC-C games, vice versa.
::By the way, actually my discussion is more focusing on the language (those country flags) displayed in the infobox, since Simplified Chinese and Traditional Chinese usually are more considered as different languages. Some games provided only Simplified Chinese version, some games provided both. What do you think? :) [[User:SiuMing|SiuMing]] ([[User talk:SiuMing|talk]]) 09:34, 1 September 2020 (UTC)
:I don't see how adding a Traditional Chinese language flag icon could be a problem from any perspective. Should I add the [https://en.wikipedia.org/wiki/File:Flag_of_the_Republic_of_China.svg flag of Taiwan] for this? I, however, will not be able to correct existing articles because of the scarcity of information, my main source for the languages is redump and it doesn't have a lot of Asian discs, so if you can correct at least some articles, please do.
::Sure, I can help on this part after adding the flag for Traditional Chinese. I think either Taiwan flag / Hong Kong flag or a mix of them will do. [[User:SiuMing|SiuMing]] ([[User talk:SiuMing|talk]]) 15:23, 3 September 2020 (UTC)
:As for isolating NTSC-C to its own regionbox (despite a region-lock), I still don't see a necessity. There are only so many games in this region, and regionboxes do not have to follow Sony's footsteps. As I said before, I can alter the name to be more descriptive to avoid confusion. --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 18:48, 2 September 2020 (UTC)
:: I am okay to keep the current design. My main suggestion is the language (flag) part only indeed. But I believe it is always a good idea if the name is altered for avoiding confusion :) [[User:SiuMing|SiuMing]] ([[User talk:SiuMing|talk]]) 15:23, 3 September 2020 (UTC)
:Done and done. I added Taiwan flag if you want to mix it with HK flag, it's [[:File:Traditional Chinese.png|all yours]]. I also updated every game that had Chinese flag to have the Mainland China flag. In all probability, '''SLAJ/SCAJ''' serials are Taiwan/HK related and '''SCCS''' are simplified Chinese versions, but there are a number of totally different cases. If you have any questions, please holler! --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 16:54, 3 September 2020 (UTC)
::Thank you! [[User:SiuMing|SiuMing]] ([[User talk:SiuMing|talk]]) 03:56, 4 September 2020 (UTC)
:You're welcome! --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 05:52, 5 September 2020 (UTC)
== Dropdown styles. ==
I don't want the Wiki to have testcases like this:
https://i.imgur.com/996Cbc8.png
It's a problem when people put it in the comments section, which is why the dropdown sections exist. Unfortunately the button being ugly is sad, but not a reason to completely remove the section.
As an alternative solution, I've looked into different ways of adding the settings dropdown menu.
=== Method 1 ===
{{TestingHeader|OS=Windows}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 10 Pro x64 (build 19041)
|CPU=AMD Ryzen 5 3600 @ 3.60~4.20 GHz
|GPU=AMD Radeon R9 280 @ 3 GB
|Revision=v1.7.0 (dev- )
<spoiler show="Settings" hide="Hide">
* '''Speedhacks:'''
** EE Cyclerate: 0
** VU Cycle Stealing: 0
** mVU Flag Hack: ✓
** MTVU: ✓
</spoiler>
|Graphics=GSdx 1.2.0 AVX2
<spoiler show="Settings" hide="Hide">
* Renderer: Direct3D 11 (Hardware)
* Internal Resolution: 4x Native
* Texture Filtering: Bilinear (PS2)
* Anisotropic Filtering: Off
* CRC Hack Level: Automatic
* '''Shader Configuration:'''
** FXAA: ✓
** Shade Boost: 50/50/60
</spoiler>
|Sound=
* SPU2-X 2.0.0
* LilyPad 0.12.1
|Comments=BIOS: USA 2.30,
|Tester=Ryudo
}}
{{TestingFooter}}
=== Method 2 ===
{{TestingHeader|OS=Windows}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 10 Pro x64 (build 19041)
|CPU=AMD Ryzen 5 3600 @ 3.60~4.20 GHz
|GPU=AMD Radeon R9 280 @ 3 GB
|Revision=v1.7.0 (dev- )
<span class="mw-customtoggle-Revision">'''[Settings]'''</span>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-Revision">
* '''Speedhacks:'''
** EE Cyclerate: 0
** VU Cycle Stealing: 0
** mVU Flag Hack: ✓
** MTVU: ✓
</div>
|Graphics=GSdx 1.2.0 AVX2
<span class="mw-customtoggle-Graphics">'''[Settings]'''</span>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-Graphics">
* Renderer: Direct3D 11 (Hardware)
* Internal Resolution: 4x Native
* Texture Filtering: Bilinear (PS2)
* Anisotropic Filtering: Off
* CRC Hack Level: Automatic
* '''Shader Configuration:'''
** FXAA: ✓
** Shade Boost: 50/50/60
</div>
|Sound=
* SPU2-X 2.0.0
* LilyPad 0.12.1
|Comments=BIOS: USA 2.30,
|Tester=Ryudo
}}
{{TestingFooter}}
=== Method 3 ===
{{TestingHeader|OS=Windows}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 10 Pro x64 (build 19041)
|CPU=AMD Ryzen 5 3600 @ 3.60~4.20 GHz
|GPU=AMD Radeon R9 280 @ 3 GB
|Revision=v1.7.0 (dev- )
<div class="toccolours mw-collapsible mw-collapsed">
<div style="font-weight:bold;">Settings</div>
<div class="mw-collapsible-content">
* '''Speedhacks:'''
** EE Cyclerate: 0
** VU Cycle Stealing: 0
** mVU Flag Hack: ✓
** MTVU: ✓
</div>
|Graphics=GSdx 1.2.0 AVX2
<div class="toccolours mw-collapsible mw-collapsed">
<div style="font-weight:bold;">Settings</div>
<div class="mw-collapsible-content">
* Renderer: Direct3D 11 (Hardware)
* Internal Resolution: 4x Native
* Texture Filtering: Bilinear (PS2)
* Anisotropic Filtering: Off
* CRC Hack Level: Automatic
* '''Shader Configuration:'''
** FXAA: ✓
** Shade Boost: 50/50/60
</div>
|Sound=
* SPU2-X 2.0.0
* LilyPad 0.12.1
|Comments=BIOS: USA 2.30,
|Tester=Ryudo
}}
{{TestingFooter}}
=== Method 4 ===
This is an older style I used to use, before the dropdown menus existed:
{{TestingHeader|OS=Windows}}
{{TestingEntry
|Status=2
|Region=NTSC-U
|OS=Windows 7 Ultimate x64 (SP1)
|CPU=Intel Core i5-4670K @ 3.40 GHz
|GPU=AMD Radeon R9 280 @ 3 GB
|Revision=
1.3.1-1578-g20e36f8
<small style="font-size:10px;">
:<b>Speedhacks</b>
* EEC: 0 & VUCS: 0
* mVU Flag: ON
* MTVU: ON
</small>
|Graphics=
GSdx 1.0.0 AVX2
<small style="font-size:10px;">
* D3D11 Hardware
* Resolution: 4x Native
* Enable FXAA: ON
* FPS: 60/60
</small>
|Sound=
* SPU2-X 2.0.0
<small style="font-size:10px;">
:* Module: XAudio2
:* Latency: 150ms
:* Sync Mode: TimeStretch
</small>
* LilyPad 0.11.0
|Comments=BIOS: USA 2.30, Runs very good. I noticed a few slowdowns in the game, but this was mostly during massive fights only when a lot of stuff was going on in the screen. 
|Tester=Ryudo
}}
{{TestingFooter}}
Method 2 is the cleanest looking one to me, it has no button nor any borders, while still maintaining a clean looking setup. -- [[User:Ryudo|Ryudo]] ([[User talk:Ryudo|talk]]) 09:42, 31 August 2020 (UTC)
:"I don't want the Wiki to have testcases like this: https://i.imgur.com/996Cbc8.png" -- Me neither, that's why I added a note about walls of text. Besides even this example looks better than a lot of text in the narrow "Graphics" column (which is encouraged now by the "How to contribute" article). I'm committed ''NOT'' to remove/alter current and future test entries containing those buttons, you seem to like, I just don't want to encourage people to use them. Let's keep my revision and see what will happen. If the walls of text will become bigger and messier than it will be an indication to alter the article again. Deal? --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 10:35, 31 August 2020 (UTC)
== SLAJ-25005: [[World Soccer Winning Eleven 6 International]] ==
I have taken a [https://i.imgur.com/lUeO2tk.jpeg photo] of it. I will also submit it to redump.org once I have the account and permission. I have changed it again. If you think it is still inappropriate, please feel free to undo my changes. --[[User:SiuMing|SiuMing]] ([[User talk:SiuMing|talk]]) 16:10, 6 September 2020 (UTC)
:Thank you! I'm just a bit overprotective when it comes to accepting nomenclature changes, I always try to verify it. It's not the first time though that the Internet is wrong, and probably will not be the last. :\ --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 18:01, 6 September 2020 (UTC)
67,565

edits

Navigation menu