GTE Lighting Input Latency: Difference between revisions
| Revision as of 05:26, 23 October 2026 RemmyLee (Hardware tests: cross-link the two CD-ROM no-disc pages and the two GTE input timing pages, with the measured step sizes) | Revision as of 05:27, 23 October 2026 RemmyLee (GTE Lighting Input Latency: split the cross-link sentence) | ||
| Line 43: | Line 43: | ||
| | BFC | | | 12 | | | BFC | | | 12 | | ||
| − | An empty cell is a register the command does not use. NCDT needs the far colour longest: a write to GFC up to 13 NOPs after NCDT still changed its result.[^run] [GTE Input Timing and I/O Load Pairs](/tests/gte-input-timing/) sweeps the inputs of every GTE command in steps of up to 8 NOPs, cold from RAM and then cached. In that program a write to VXY2 four NOPs after NCT still reached the command in one of the two runs.[^cpu4] | + | An empty cell is a register the command does not use. NCDT needs the far colour longest: a write to GFC up to 13 NOPs after NCDT still changed its result.[^run] [GTE Input Timing and I/O Load Pairs](/tests/gte-input-timing/) runs each GTE command cold from RAM and then cached, and it sweeps the inputs in steps of up to 8 NOPs. There a write to VXY2 four NOPs after NCT still reached the command in one of the two runs.[^cpu4] |
| ## Runs | ## Runs | ||