Skip to the notes

Does a heavier Cronus Zen script add input lag?

How to distinguish script processing load from end-to-end input latency without assuming a fixed penalty.

Dana RehnTechnical editor

Filed Revised Nov 14, 20261 min read

Quick answer. More script work can change processing behavior, but a load percentage does not tell you how many milliseconds reach the screen. This page does not assign a universal latency penalty to commercial scripts.

Compare like with like

A useful experiment compares an empty slot, a pass-through fixture and controlled increments of additional work. Keep the controller, firmware, console, display and test scene the same. Test whether connecting monitoring equipment changes the measurement.

A synthetic arithmetic loop can isolate one kind of workload. It does not represent every commercial script, which may spend time on menus, stored settings, input sequences or different execution paths.

Two different measurements

Measurement Interpretation
A tool's load reading What that tool reports about execution load
Press-to-screen time The response of the entire tested chain

Neither can be substituted for the other. Read a tool's documentation before treating a percentage as a hardware utilization limit or a measured delay.

Reporting a result

Name the exact fixture or script build, its settings and the sample count. Compare distributions across conditions and report the measurement resolution. A claimed sub-millisecond difference requires an instrument and analysis that can support it.

The previous original load table and unverified compile statistics have been removed. No commercial script is ranked by latency here. The latency breakdown explains why the entire chain matters.

A figure looks wrong? Report an error

Further notes