nesdev.com

Skrybe, if you've got the time, could you check Armadillo in-game and look whether or not the status bar occasionally bumps vertically by 1 pixel? (try it on Nestopia or another accurate emulator to see what I mean)

pputime2 was tested on a CopyNES, that inits RAM before booting.. your emu is not broke, just a bit short on cash maybe =p

The numbers don't mean anything it's just an ordered list. Each next in the list is the result timed at 1 PPU cycle after the previous one.

cool
If you've got an earlier source of Schpune, the one before you added this, could you measure the speed improvement?

They flame you because they're ignorant, jealous, or just like to hurt people sometimes, don't let it influence you

It's ok, I made that thinking-error too once ;p. It would only work if you stored it into an 8 bit variable before the "if". Still though, it won't work that way, since if A=$FF, value=$FF, carry is set, result would be the same as A, but cause a carry anyway.

Some other things come to mind, like the timing of these accesses, and RMW instructions write testing (maybe use $2007 for that).

yeah, that test rom fails here (for now)
Thanks.

OK, Ironsword doesn't have the problem because the loop that clears APU registers reads the register first since it uses the STA $4000,x addressing mode. So that reads $4015 after the frame IRQ flag has been set. Ah, good find, didn't know that that was an "RMW"? instruction. Maybe you could improv...

Are you modifying it during rendering?

hmmmmm... *shameful yes*
none of your test roms cover it

$2002 power on with $00 instead of $A0: - Ironsword: locks up at titlescreen with "Ironswor" and no sword in his hands - Cobra Triangle: locks up when starting game btw1: I probably don't need to mention that a lot of homebrew stuff fails. btw2: $2007 read buffer.nes usually succeeds if I leave $200...

After implementing your recent findings, Tiger Heli (U), Kamen Rider Club (J), and maybe more, won't boot in my emu due to PPU register writes being ignored in the 1st frame. These do work by doing a reset afterwards though.

on Quietust's webspace
http://www.qmtpro.com/~nes/misc/nestest.nes
http://www.qmtpro.com/~nes/misc/nestest.txt

nmi_on_timing tests NMI timing near the end of vblank by writing with bit 7 ($80) set to $2000. if 5=N, it means your edge timing is 1 PPU cycle off.

Specifically, do problems show up during page boundary crossing, when there's no page crossing, or both? I suspect that since the store value is affected by the upper byte of the target address (the "fixed" version, with 1 added to it), it's possible that a page crossing would also cause an issue w...