TODO List: Difference between revisions

Jump to navigation Jump to search
(→‎Tasks: Migrate completed tasks to bottom)
Line 3: Line 3:
This page is kind of a TODO list for the Dolphin project: project members add interesting ideas they don't have time to implement here. If you are a developer looking to contribute to Dolphin, picking one of these ideas might be a good way to start! Join us on IRC to ask for more informations if needed: #dolphin-dev @ freenode.
This page is kind of a TODO list for the Dolphin project: project members add interesting ideas they don't have time to implement here. If you are a developer looking to contribute to Dolphin, picking one of these ideas might be a good way to start! Join us on IRC to ask for more informations if needed: #dolphin-dev @ freenode.


=== Add curl support ===
=== Add CURL Support ===
* Proposed by: Parlane
* Proposed by: Parlane
* Difficulty: average
* Difficulty: average
Line 10: Line 10:
Curl is needed for the WC24 side of things and would also be beneficial to the "Check for updates" task below. We need to make sure we can have curl work with PolarSSL.
Curl is needed for the WC24 side of things and would also be beneficial to the "Check for updates" task below. We need to make sure we can have curl work with PolarSSL.


=== Hardware errors detection ===
=== Hardware Errors Detection ===
* Proposed by: delroth
* Proposed by: delroth
* Difficulty: average
* Difficulty: average
Line 16: Line 16:
A lot of people overclock their CPU and/or memory to run Dolphin at full speed. This could potentially cause stability issues misdiagnosed as bugs in Dolphin. I'm not sure if there is an easy way to check for this kind of issues because they are very random (compared to issues due to bad memory), but having this kind of feature might be a good way to avoid invalid issues.
A lot of people overclock their CPU and/or memory to run Dolphin at full speed. This could potentially cause stability issues misdiagnosed as bugs in Dolphin. I'm not sure if there is an easy way to check for this kind of issues because they are very random (compared to issues due to bad memory), but having this kind of feature might be a good way to avoid invalid issues.


=== Generate crash informations on JIT segfault ===
=== Generate Crash Information on JIT Segfault ===
* Proposed by: delroth
* Proposed by: delroth
* Difficulty: easy/average
* Difficulty: easy/average


When JIT-ed PPC code crashes because of an invalid memory access, the curent behavior is to display a cryptic message box to the user ("BackPatch - no support for operand size 1", or "Unhandled disasm case in write handler") and/or kill the whole program. This makes it hard to debug these issues after the crash happened because no debug informations has been left behind.
When JIT-ed PPC code crashes because of an invalid memory access, the curent behavior is to display a cryptic message box to the user ("BackPatch - no support for operand size 1", or "Unhandled disasm case in write handler") and/or kill the whole program. This makes it hard to debug these issues after the crash happened because no debug information has been left behind.


Writing a crash dump file with the PPC backtrace, state of all the PPC registers, code of the JIT block that caused the crash + exact instruction causing the crash, and maybe informations about the user hardware would be very nice.
Writing a crash dump file with the PPC backtrace, state of all the PPC registers, code of the JIT block that caused the crash + exact instruction causing the crash, and maybe information about the user hardware would be very nice.


=== Implement Post-Processing shaders in D3D11 ===
=== Implement Post-Processing Shaders in D3D11 ===
* Proposed by: Sonicadvance1
* Proposed by: Sonicadvance1
* Difficulty: average
* Difficulty: average


The OpenGL backend already supports post-processing shaders while the D3D11 backend doesn't. Implementing this feature should allow persons to use the same shaders for both the D3D and OGL backend by abstracting portions of the shaders out.
The OpenGL back-end already supports post-processing shaders while the D3D11 back-end doesn't. Implementing this feature should allow persons to use the same shaders for both the D3D and OGL back-end by abstracting portions of the shaders out.


=== Implement more fastmem methods ===
=== Implement More Fastmem Methods ===
* Proposed by: Sonicadvance1
* Proposed by: Sonicadvance1
* Difficulty: average/hard
* Difficulty: average/hard
Line 47: Line 47:
* Fix the [https://bugs.dolphin-emu.org/projects/emulator/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=cf_7&op%5Bcf_7%5D=%3D&v%5Bcf_7%5D%5B%5D=1&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&group_by= easy issues] or any of the other issues on our tracker.
* Fix the [https://bugs.dolphin-emu.org/projects/emulator/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=cf_7&op%5Bcf_7%5D=%3D&v%5Bcf_7%5D%5B%5D=1&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&group_by= easy issues] or any of the other issues on our tracker.


=== <s>"Check for updates" feature</s> ===
=== <s>"Check for updates" Feature</s> ===
* Proposed by: Parlane
* Proposed by: Parlane
* Difficulty: easy
* Difficulty: easy