Module report 

RunReport: what a shipped game says in its console on every run, when it turns the report on (Driver::with_report): how its start went, and then how fast it runs, so a tester’s log shows a slow start or a stutter without a bench build.

• The start: when the loading card and the game’s first frame were shown (milliseconds after init), how long the load took, the game stack’s deepest use after it, and the files the load read: how many, which the bundle lacks, and the slowest. A loader names a step that reads no file with mark, so its time is its own.
• Each minute (or RunReport::every_seconds): the top screen, the frames a second, the times of App::frame and of the draw, the stack, the music; and, with RunReport::phases, each phase of the draw.

Off, nothing is measured or logged. Times are whole microseconds from the SDK’s high-resolution timer, shown in milliseconds.

Structs

RunReport

What the report says, and where else it writes the start: off until a game makes one.

Timing

How long something took, time after time: the fewest, the most and the average microseconds.

Functions

mark

Names the step name of the game’s load, which reads no file: the time from here to the next read is its own, not the last file’s. Nothing happens unless the report is on and the game is loading.