6,576
edits
 |
Progress Continues
We've already had 21717 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: February, March, and April 2024 Dolphin Progress Report. |
 |
The Dolphin Emulator Wiki needs your help! Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin. |
Project talk:Wiki Conventions: Difference between revisions
Jump to navigation
Jump to search
m
Geez wiz!
No edit summary |
m (Geez wiz!) |
||
| Line 59: | Line 59: | ||
:: I hadn't thought about this before and indeed it makes a lot of sense putting the section below problems. Also, changing to Enhancements seems fine too, after all, HD texture packs, 60FPS or Widescreen codes makes little sense being tagged as Patches. In future, if we start to tag 3D compatibility or required settings it would fit very well in that new section. Regarding codes for other ARs, I tried integrating somehow (after all the address is exactly the same, the only thing that change is the value) but I failed miserably, all approaches I tried became messy and cluttered. Because of that I still think we should stick with 16:9 only. I see this as another confusion source in future, let's say someone puts a code for an awkward AR, like, let's say, 39:12, then another guy come and put another strange AR as well, in little time the pages would be a mess again. And in relation to other "standard" ARs, like 16:10, using crop feature would suffice, I mean, you'll lose a very small part of the frame which is veeeery unlikely to have important data since the game is already running in a wider resolution than the intended. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) | :: I hadn't thought about this before and indeed it makes a lot of sense putting the section below problems. Also, changing to Enhancements seems fine too, after all, HD texture packs, 60FPS or Widescreen codes makes little sense being tagged as Patches. In future, if we start to tag 3D compatibility or required settings it would fit very well in that new section. Regarding codes for other ARs, I tried integrating somehow (after all the address is exactly the same, the only thing that change is the value) but I failed miserably, all approaches I tried became messy and cluttered. Because of that I still think we should stick with 16:9 only. I see this as another confusion source in future, let's say someone puts a code for an awkward AR, like, let's say, 39:12, then another guy come and put another strange AR as well, in little time the pages would be a mess again. And in relation to other "standard" ARs, like 16:10, using crop feature would suffice, I mean, you'll lose a very small part of the frame which is veeeery unlikely to have important data since the game is already running in a wider resolution than the intended. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) | ||
I kind of want to clean up and remove all credits that included after the code names after seeing that Jhonn has converted the widescreen code for PM:TTYD then removed the credit, as seen here: [ | I kind of want to clean up and remove all credits that included after the code names after seeing that Jhonn has converted the widescreen code for PM:TTYD then removed the credit, as seen here: [https://wiki.dolphin-emu.org/index.php?title=Paper_Mario%3A_The_Thousand-Year_Door&type=revision&diff=105640&oldid=105541 Difference between revisions of "Paper Mario: The Thousand-Year Door"] | ||
I don't believe anyone can deserve a credit if the code is only made up of one or a few lines, so I'm in support of removing them. Anyone else? [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 08:38, 23 August 2015 (CEST) | I don't believe anyone can deserve a credit if the code is only made up of one or a few lines, so I'm in support of removing them. Anyone else? [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 08:38, 23 August 2015 (CEST) | ||