| Progress Continues
We've already had 11819 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: December 2019 and January 2020 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.
Remember the Dolphin Manual? Well, I've thought about it a lot since that project failed, and really the dolphin manual was only two things.
1. A list of instructions for set up and doing various things. The wiki already has most of that in Help:Contents via our tutorials.
2. A list of functions in the emulator and what they do and where they are.
We already have #1. However, it occurred to me that we already have #2 as well... right here. Template:Config. It lists all of the options in the emulator, shows where they are (general location via categories anyway) and describes them. The problem is that it is very user unfriendly. It's designed to display stuff in wiki pages, and it does that job very well but it's not very friendly for other purposes. So, here's my question to you guys - how hard would it be to make a page that automatically displayed every Template:Config entry? That way, any time Template:Config is updated, the big user-friendly list would be updated as well. With a little tweaking to make it more presentable, we take what we already have and maintain and suddenly it's a one-stop shop for Dolphin help, fulfilling everything the Dolphin Manual set out to achieve! But uh, I don't know how to do that. You know, artist and all. What do you guys think? - MaJoR (talk) 15:23, 13 July 2014 (CEST)
- It'll need some refactoring to automatically add new option to a list and the template's code is messy at the moment. A temporary solution is creating a page and include Config template with every possible entry and then update accordingly whenever we add new options. It's a quick way to archive #2 until we refactor the template's code. Jhonn (talk)
EFB to RAM/Texture
EFB to Ram and EFB to Texture have changed. It is now a single option: "Store EFB Copies to Texture Only". Checked is EFB to Texture, unchecked is EFB to RAM. And of course EFB Copies Disabled is gone. So um, how should we handle this? We'll need an ideal way of handling it as well as a way to migrate everything over. - MaJoR (talk) 05:26, 5 March 2015 (CET)