Project check list

[GoogleCodeExporter]

This is really for myself to help me keep the project on track (and myself
busy of course) as well as to let everyone working on the project or
interested in becoming involved with the project to know what most pressing
things need to be done. Listed here are everything from trivial programming
tasks to potentially major core changes.

1)Getting 3D working well
Right now, 3D renders some things but textures are for the most part
transparent. This is what I am personally working very hard on resolving.
It seems on the outside that we need to allocate more memory for the 3D
functions to use. However, it also seems that there is something going
wrong causing some textures not to show. I think it involves the palette
color conversions but I'm really not too sure at the moment. If you
couldn't tell, this is what I'm personally focusing my working around.

2)Getting homebrew and commercial ROMs to work properly
It seems we can only get homebrew ROMs to work correctly when we hardcode
in the GPU display mode as 2. But we can only get commercial ROMs to work
when we do not. At the very least, we need to setup an if() that hardocdes
the gpu display mode if "Homebrew" is detected as the ROM ID.

3)Visibly marking stylus position
We've got X and Y coordinates tracking the stylus. Now let's use GX to
render a small aquare or something to show where the stylus is positioned
at. At the moment, as you cant see where the stylus is at, it's almost
impossible to use it or tell if it even works at all.

4)Getting more ROMs to boot
It's no longer an issue of ROMs just crash the emulator because we can't
get 3D to work. While compatibility has been greatly improved, there are
many ROMs like the Castlevanias and Mario Kart that just freeze and don't
do anything. This is presumably something in the loader code. My guess
would be that there's a register we need to give memory that we stole back to.

5)Optimization
I'm noticing in the rasterizer and  3D effects that we could probably
directly use GX to get some things done more efficiently and quickly. There
are most certainly other places in the emulator where similar things can be
done to shorten code or make it more Wii friendly.

6)Removing unneeded code
We need every extra bit of memory we can get! We do not need things in
DeSmuME like code to record a video of gameplay. Or to interface with a
linux filesystem. We can also probably start getting rid of OGLRender files
now. Please, if you see code we can get rid of: Get rid of it. We need the
extra memory.

7)Using 32-Bit Variables
ekeeke suggested using 32 bit variables in lieu of smaller ones
(specifically 32 bit ints instead of the 8 bit ones we were using) in order
to speed up the emulator. I would love to look into this and see how
helpful this may be.

8)Adding frame skipping
We've got some code in main.cpp to monitor the fps rate. It shouldn't be
too hard to use it to give the user control over frame skipping to
artificially speed up emulation for themselves.

Original issue reported on code.google.com by castleva...@yahoo.com on 2 Apr 2010 at 2:20

[GoogleCodeExporter]

Pretty much everything here has been met so imma get rid of this issue now and 
cleanup.

Original comment by castleva...@yahoo.com on 22 Apr 2010 at 12:02

• Changed state: Done

[GoogleCodeExporter]

castlevania7689@yahoo.com
I created Wiki page about #8. It won't give you any speedup.

Original comment by AndreyLegchilin on 22 Apr 2010 at 9:26

[GoogleCodeExporter]

You mean #7? - http://code.google.com/p/desmumewii/wiki/ppc32_Types

Original comment by iamsca...@gmail.com on 22 Apr 2010 at 10:03

[GoogleCodeExporter]

scanff@yahoo.com
Right...

Original comment by AndreyLegchilin on 22 Apr 2010 at 10:11

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by castleva...@yahoo.com on 23 Apr 2010 at 12:31

• Added labels: Restrict-AddIssueComment-Commit