79,235
edits
 |
Progress Continues
We've already had 21687 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. |
User talk:Mbc07: Difference between revisions
Jump to navigation
Jump to search
→Formatting guidelines for processor speed under testing
| Line 117: | Line 117: | ||
:::::::::: I initially thought keeping to a single decimal place with no space on the Dolphin wiki would be a compromise, as well as keeping with how CPU speeds are commonly displayed on most pages elsewhere on the Internet. But, no compromises here. [[User:Flang|Flang]] ([[User talk:Flang|talk]]) 21:18, 3 May 2017 (CEST) | :::::::::: I initially thought keeping to a single decimal place with no space on the Dolphin wiki would be a compromise, as well as keeping with how CPU speeds are commonly displayed on most pages elsewhere on the Internet. But, no compromises here. [[User:Flang|Flang]] ([[User talk:Flang|talk]]) 21:18, 3 May 2017 (CEST) | ||
::::::::::: I can be supportive of adding a non-breaking space to align with the stylistic guidance from [http://www.bipm.org/en/about-us/ BIPM], but such is likely to also be a pain to maintain. I'm still not onboard with adding excess decimal zeros. However, I still generally feel a single speed value is unlikely to capture actual performance characteristics well. There is simply too much scaling that occurs /w modern processors based on things like temperature/load. And we aren't going to get people to populate values appropriately to capture those sorts of details, or be able to back-populate them in pre-existing entries. I persist in a strong preference to simply purge the indicated speeds, which simplifies all this and likely has only minor impact on reported results (i.e. I still don't feel most overclocks effect things significantly enough to matter, even if a >10% improvement was seen). [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 22:12, 3 May 2017 (CEST) | |||
::::::: * You keep referring to our own guidelines as if we're not consistent with it, even though we are. Perhaps we should rephrase that CPU speed section to better reflect how these speeds got handled during all those years since the way it's written currently leads you to that kind of "loose" interpretation? | ::::::: * You keep referring to our own guidelines as if we're not consistent with it, even though we are. Perhaps we should rephrase that CPU speed section to better reflect how these speeds got handled during all those years since the way it's written currently leads you to that kind of "loose" interpretation? | ||
| Line 126: | Line 128: | ||
:::::::::: Today I have overclocked my own CPU. It would be sad to see my test entries changed to include false information, but that appears to be how determined you are not to give any ground. [[User:Flang|Flang]] ([[User talk:Flang|talk]]) 21:18, 3 May 2017 (CEST) | :::::::::: Today I have overclocked my own CPU. It would be sad to see my test entries changed to include false information, but that appears to be how determined you are not to give any ground. [[User:Flang|Flang]] ([[User talk:Flang|talk]]) 21:18, 3 May 2017 (CEST) | ||
::::::::::: Again, why we'll never actually have consistent handling unless we generally purge the speed details. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 22:12, 3 May 2017 (CEST) | |||