Talk:The Legend of Zelda: Twilight Princess (GC): Difference between revisions

Jump to navigation Jump to search
Username rename (MaJoR => MayImilae)
No edit summary
(Username rename (MaJoR => MayImilae))
 
(12 intermediate revisions by 6 users not shown)
Line 7: Line 7:
Now about your "Disable Letterbox" code, it '''does not''' fall in any of those categories. And no, '''it's not''' related to Aspect Ratio codes because the game is supposed to letterbox during aiming and cutscenes and it only does that during these section. This code could be tagged as Aspect Ratio code if, and only if, the game '''always ran''' letterboxed, even with the widescreen code available. Since that's not the case, you're essentially disabling a game feature with this code, and thus, it's not allowed here, it does not fit in any of the categories above.  
Now about your "Disable Letterbox" code, it '''does not''' fall in any of those categories. And no, '''it's not''' related to Aspect Ratio codes because the game is supposed to letterbox during aiming and cutscenes and it only does that during these section. This code could be tagged as Aspect Ratio code if, and only if, the game '''always ran''' letterboxed, even with the widescreen code available. Since that's not the case, you're essentially disabling a game feature with this code, and thus, it's not allowed here, it does not fit in any of the categories above.  


So, unless you know of some emulation bug this code can overcome, '''do not''' readd it to this page. Furthermore, it's not the first time we have issues with AR codes here, expect more aggressive actions against those edits if you keep insisting, we're not GC Forever, WiiRD or CodeJunkies to have every AR/Gecko code listed here or to allow any code you may judge useful. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 20:06, 2 February 2016 (CET)
So, unless you know of some emulation bug this code can overcome, '''do not''' readd it to this page. Furthermore, it's not the first time we have issues with AR codes here, expect more aggressive actions against those edits if you keep insisting, we're not GC Forever, WiiRD or CodeJunkies to have every AR/Gecko code listed here or to allow any code you may judge useful. - [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 20:06, 2 February 2016 (CET)
----
----


Line 39: Line 39:


:''"And yes, I realize this wiki is not CodeJunkies, but if there ARE core graphical enhancements (like widescreen hacks, deletterboxing, blur removal, ghosting removal, higher framerate, etc), then I believe they should be listed here. It's not like I'm adding "infinite health" and "have all weapons" and "1 hit kill" codes here. Deletterboxing is a core graphical enhancement in my opinion."''
:''"And yes, I realize this wiki is not CodeJunkies, but if there ARE core graphical enhancements (like widescreen hacks, deletterboxing, blur removal, ghosting removal, higher framerate, etc), then I believe they should be listed here. It's not like I'm adding "infinite health" and "have all weapons" and "1 hit kill" codes here. Deletterboxing is a core graphical enhancement in my opinion."''
::Games that run letterboxed/pillarboxed '''all the time''' can have "disable letterbox" codes listed on their pages without any problem as they would be fitting the definition of Gecko/AR codes that allow wider aspect ratios. But as I said before (and above), '''that is not the case''' with Zelda TP, period. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 03:33, 4 February 2016 (CET)
::Games that run letterboxed/pillarboxed '''all the time''' can have "disable letterbox" codes listed on their pages without any problem as they would be fitting the definition of Gecko/AR codes that allow wider aspect ratios. But as I said before (and above), '''that is not the case''' with Zelda TP, period. - [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 03:33, 4 February 2016 (CET)
----
----


Line 93: Line 93:
   
   
:''"Again, we can change the wiki's rules and conventions (to allow for deletterbox codes, blur removal codes, film grain removal codes). It ain't rocket science. And I propose we do this."''
:''"Again, we can change the wiki's rules and conventions (to allow for deletterbox codes, blur removal codes, film grain removal codes). It ain't rocket science. And I propose we do this."''
::Fine. If you're starting the discussion here, none of the arguments you provided were enough to change my thoughts about this, so I'm completely opposed of allowing those codes on our wiki. You can go seek opinions of the other admins/active users ([[User:Kolano|Kolano]], [[User:MaJoR|MaJoR]], [[User:Lucario|Lucario]], etc), if the majority are in favour (which I personally doubt, given our past problems with AR/Gecko Codes) we can go further on this. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 17:40, 4 February 2016 (CET)
::Fine. If you're starting the discussion here, none of the arguments you provided were enough to change my thoughts about this, so I'm completely opposed of allowing those codes on our wiki. You can go seek opinions of the other admins/active users ([[User:Kolano|Kolano]], [[User:MayImilae|MayImilae]], [[User:Lucario|Lucario]], etc), if the majority are in favour (which I personally doubt, given our past problems with AR/Gecko Codes) we can go further on this. - [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 17:40, 4 February 2016 (CET)
----
----


Line 112: Line 112:
:Don't act like they SPECIFICALLY chose not to include it on purpose. We don't know for sure. A lot of games lack options because devs are usually pressed for time, have deadlines, etc. And again, even if they DID, I argue graphical preference of the player is more important than intention.
:Don't act like they SPECIFICALLY chose not to include it on purpose. We don't know for sure. A lot of games lack options because devs are usually pressed for time, have deadlines, etc. And again, even if they DID, I argue graphical preference of the player is more important than intention.


''"You can go seek opinions of the other admins/active users (Kolano, MaJoR, Lucario, etc), if the majority are in favour"''
''"You can go seek opinions of the other admins/active users (Kolano, MayImilae, Lucario, etc), if the majority are in favour"''


:What's the point? Wikis tend to be an admin circlejerk where other admins tend to agree with the opinions of others just 'cuz you're all "buddy buddy" with each other.
:What's the point? Wikis tend to be an admin circlejerk where other admins tend to agree with the opinions of others just 'cuz you're all "buddy buddy" with each other.


:But yes, I advocate the inclusion of deletterbox codes, film grain removal codes and blur removal codes. I'll send them a notice anyway. [[User:Devina|Devina]] ([[User talk:Devina|talk]]) 18:46, 4 February 2016 (CET)
:But yes, I advocate the inclusion of deletterbox codes, film grain removal codes and blur removal codes. I'll send them a notice anyway. [[User:Devina|Devina]] ([[User talk:Devina|talk]]) 18:46, 4 February 2016 (CET)
===MayImilae's Response===
Hi, I would like to ask you for your opinion on the inclusion of deletterbox codes, film grain removal codes and blur removal codes. I believe players should be able to tweak the graphical settings of their games as they wish, and believe Dolphin Wiki would be a great place to list such codes because they can be difficult to find elsewhere, and they are purely optional. The discussion for this is [https://wiki.dolphin-emu.org/index.php?title=Talk:The_Legend_of_Zelda:_Twilight_Princess_%28GC%29 here]. [[User:Devina|Devina]] ([[User talk:Devina|talk]]) 18:51, 4 February 2016 (CET)
:Sorry, but I am completely opposed. In the past we had a great deal of problems with users adding in *tons* of codes that were extremely difficult to track down and verify. Many of them didn't even work when users tried them! This wiki is not meant as a codes database, and was not able to handle the display or verification of tons of codes. As such, we talked about it, decided that only certain codes would be accepted, which those codes were, and even wrote it down in [[Project:Wiki Conventions]]. I'm sorry, but this is not accepted and we have very real reasons for rejecting it. There are many other places for users to get codes, sites that are able to handle them better than we would be able to, and they will work in Dolphin just fine! - [[User:MayImilae|MayImilae]] ([[User talk:MayImilae|talk]]) 09:47, 5 February 2016 (CET)
::By your logic, we should remove ALL the aspect ratio codes since all of them may not actually work, and no one has time to verify all these 16:9 codes. And it's possible the codes didn't work because they were of a different region. [[User:Devina|Devina]] ([[User talk:Devina|talk]]) 13:06, 5 February 2016 (CET)
:::Regions are noted, and many of them have been verified. Even if they haven't been verified it's much much easier to do so with a limited number! Regardless, we were faced with too many cheatcodes, but we didn't want to ban them all. So we debated where the line should be, and we established one. It's what wiki admins are for! - [[User:MayImilae|MayImilae]] ([[User talk:MayImilae|talk]]) 14:40, 5 February 2016 (CET)
:::About the Aspect Ratio codes, where did you get that they aren't tested? We may not cover all games but the few ones that have widescreen codes listed were indeed tested and confirmed working (the only exception being the codes added to the two Mario Party games recently which AFAIK weren't tested by anyone else besides the contributor). When [[User:Karasuhebi]] raised the question sometime ago we ended purging a lot of codes that didn't work. And BTW, an Aspect Ratio code is only added to a game page if Dolphin's built-in widescreen hack causes issues, otherwise it's not listed on the page, even if there's a code available for it. That restriction alone already shrinks the list of codes only to the games that reeealy needs them and makes the testing much simpler. - [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 19:22, 5 February 2016 (CET)
===Kolano's Response===
* Generally we try to provide guidance here to enable accurately emulating titles, things like film grain and blur removal codes go directly against that and will not be accepted here (unless they resolve some game breaking issue with a title). Arguably revised Aspect Ratio AR codes also goes against that sentiment, but we have allowed them due to a high demand seen for them, and that they specifically compliment the pre-existing Dolphin widescreen hack and problems it can cause.
* There are plenty of sites online that provide more comprehensive AR code listings. In general I'd prefer if we could work out some integration to one of them and push all AR code content to one of them instead of having it here on the wiki at all.
* And yes, we would almost prefer to "remove ALL the aspect ratio codes since all of them may not actually work", but have allowed them, again mainly to address issues with the Widescreen hack Dolphin enhancement. I wouldn't push this much, as it's already been an uphill fight to just allow the codes that we do.
[[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 17:40, 5 February 2016 (CET)
== Wolf Link scent trails disappearing issue ==
I have done a good bit of testing for the disappearing wolf link scent trail issue and can confirm the real cause of that issue.
It does not occur with only either of the custom texture packs enabled for any version of Dolphin from 4.0 to 5.0.
It does not occur for either custom texture pack enabled in conjunction with the AR code for widescreen for any version of Dolphin from 4.0 to 5.0.
It does occur with the Gecko widescreen codes with Dolphin 5.0. It occurs with only those codes or those codes in conjunction with texture packs.
The Gecko widescreen codes are the true source of the issue with disappearing wolf link scent trails. It has nothing to do with the custom texture packs as stated in the wiki.
Just wanted to drop by and clear this up for everyone.
== New Gecko widescreen code makes dig spots hard to see ==
I love the new widescreen Gecko code. It improves upon the existing hack, and the old AR code. Whoever made it, achieved the impressive feat of moving the UI to the corners of the screen, instead of staying in the "4:3 area", like a code that was here before. But it causes a small issue during the Twilight sections, and probably <SPOILER>after Link can transform into a wolf at will, and find other dig spots inaccessible before</SPOILER>. It becomes really hard to see the dig spots. Instead of a black patch with a little sparkle, only the sparkle can be seen now. The screen noise effect is slightly reduced as well, now only visible in the background. Both effects (dig spots and noise), can be seen for a split second after activating the "Senses", but they disappear afterward. Here's a small video of the issue. I apologize for the audio chops, it's due to using FRAPS on my ancient machine:
{{#ev:youtube|S0vduRtfIFo}}
My game dump's MD5 is: 41deff9b1fd2831f48fbfa2dd1054e4d , so it should be a clean dump.
There was a similar issue on the first Gecko codes that was here, but that made the NPC's disappear during the Twilight sections. I had reported that on the Issues Tracker, but it was said that it wasn't appropriate, since that's not for Wiki issues, so I'm using this discussion thread now. At least that issue was fixed, so I hope this small issue is fixed as well. It's not a big thing, actually, since it kinda turns the game into hard mode, because some dig spots are useful, and now they're hard to find XD.

Navigation menu