I <relatively> recently changed my emu core from scanline- to pixel-based and have noticed artifacting in RasterDemo.nes that was not there in the scanline-based implementation. I have convinced myself it is operand timing related, as I can mess around with cycle counts and change the artifacting.
Does anyone have the de-facto 2A03 opcode timing reference guide? I have found disagreements between the various ones that I have been using online. Some of the problems appear to be related to whatever OCR software was used to scan in the C=64 PRM that I was using at one point. 3's became 8's or vice-versa. I have attempted to put common sense into the figuring out of these types of things, but am sure there MUST be a "gold standard" reference somewhere?!
Does anyone have the de-facto 2A03 opcode timing reference guide? I have found disagreements between the various ones that I have been using online. Some of the problems appear to be related to whatever OCR software was used to scan in the C=64 PRM that I was using at one point. 3's became 8's or vice-versa. I have attempted to put common sense into the figuring out of these types of things, but am sure there MUST be a "gold standard" reference somewhere?!