"The V=T still happens at 304 of the prerender scanline if rendering is enabled".
Just wondering if such info is still valid.
It happens continuously from x=280 to x=304.
I read in the ntsc diagram that v=t "208 trough 304 each tick" does it mean that each clock makes v=t??
Yes. If the program turns rendering on, turns rendering off after x=280 and before x=304, and turns rendering back on after x=304, then the v := t step has already occurred. The "but why would anyone do that?" nature of this edge case explains why the old hypothesis of triggering this behavior only on x=304 was enough to satisfy commercial games.