GTE Lighting Input Latency

Measures how long NCT, NCCT and NCDT keep reading each input register after they start.

This is an old revision of this page, as edited by RemmyLee at 05:18, 23 October 2026. Edit this revision | Latest revision

Overview

A GTE command reads its input registers while it runs. The program starts a lighting command, waits N NOPs, then writes a different value to one input register with MTC2 or CTC2. N runs from 0 to 32, and every output of the command is compared against an unchanged baseline.¹

The smallest N at which the late write no longer changes the output is the number of instruction slots the command still needs that register. The scene uses identity light and colour matrices, three unit normals, a grey colour of 80h and zero back and far colours. Every input is reset before each probe.¹

Results

A command reads its inputs in a fixed order. The first vertex and the first rows of the light matrix are read at once, and the back colour, far colour and RGBC late. The number of NOPs after which a write to each register no longer reached the command is as follows:²

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.²

Runs

22 October 2026

gtelatency/GTELATENCY.txt

gtelatency/bench.txt

226143 bytes of TTY text in psx.log

gtelatency/when.txt

20261022T2233Z

References