</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">I was looking at the wip status and I saw the timing is only 18% emulated, and I was asking myself: doesn't this cause some games not to work? why don't you try to emulate more of it?[/b][/quote]
Well, the 'timing' value that I've listed on the wip status section refers to the number of instructions that have accurate cycle count information programmed into them. The others just use an average value (8 cycles, if I remember correctly).
You are right that it will affect compatibility, but not at this stage - timing will affect the more complex raster effects, and more importantly sound accuracy (in some cases). But right now, compatibility is affected by straight bugs and ommisions in the CPU core.
The only thing that is affected by timing right now is that the screen refresh period does not exactly match that of the NGPC. But it seems close enough now, not to worry about!
</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">I saw there is also 57% emulated of flags, but I don't know what is it[/b][/quote]
Well this is a much more important measure of progress (I would say the most important). It refers to the number of instructions that correctly set the CPU flags after execution. (eg. if the result of a subtraction is zero then the 'z' flag is set)
This is the hardest part of the project to emulate correctly, and is also very time consuming. My main focus now, will be getting this accuracy higher, this will fix almost all of the current problems with the games that don't work very well, or at all. Other things like timing emulation will not affect as many games.
I hope this answers your questions!