How is that happening? There's no way it should be possible to throw off the beam timing. beam advances 1/256th of a scanline per rendered dot (that is, dots that are not h-blank). All that changes is that 512 pixel modes output twice per dot. The counters still move just like 256-pixel mode, and beam timing should respect that...
