I tried to get this run to sync in BizHawk and it made it all the way up to the glitch itself. But after that it crashed.
It crashed at a kill instruction ($72).
Execution here depends critically on values in PPU registers/memory and undocumented opcodes.
FCEUX seems to be having some serious trouble here. Here are the last few instructions where things depart seriously from NESHawk:
c64248952 A:7E X:FF Y:62 S:FC P:nvUBdizc $3C78:A8 TAY
c64248954 A:7E X:FF Y:62 S:FC P:nvUBdizc $3C7A:10 00 BPL $3C7C
c64248957 A:7E X:FF Y:62 S:FC P:nvUBdizc $3C8C:87 UNDEFINED
c64248960 A:7E X:FF Y:62 S:FC P:nvUBdizc $3C9E:23 UNDEFINED
c64248963 A:7E X:FF Y:62 S:FC P:nvUBdizc $3CA0:A8 TAY
c64248970 A:7E X:FF Y:62 S:F9 P:nvUBdIzc $0029:48 PHA
There are 2 TAY's here that aren't moving A to Y, a jump to $0029 that I can't tell where it's coming from, and execution jumping from 3C8C to 3C9E on the 87 instruciton (which is just supposed to AND X and A.)
I read in the original publication of this branch by MUGG that the glitch itself is console verified, but on a different level. Is the glitch console verified on this level?