# OpenP2P GTA V action timing

Exactly 100 recorded-input candidates, each 15 seconds at 20 FPS. The source is the Open Pixel2Play GTA V subset. Selection excludes menu/system keys, requires all 300 user input and mouse-delta states, and requires nonzero mouse movement. This is not a claim of 100 visually accepted events.

Gemini 3.8 Flash examines full-clip context at about 8 FPS, then receives 20 FPS images around candidate boundaries. Output includes onset/completion brackets referring to actual submitted frames, descriptions, and UI/menu intervals. Original responses and prompts are preserved locally. The page provides all labels, boundary evidence and original per-frame mouse/keyboard states.

Cases flagged by an independent visual spot check or boundary brackets wider than one native frame receive an additional API review of all 300 frames. The visual spot check addresses car-door completion and the distinction between landing on a boat bow and landing on the beach. Both the earlier responses and the final API outputs remain in the local audit trail. The page identifies the extra review pass; this spot check does not certify all 100 cases.

Mouse deltas are pixel input increments, not camera pose or rotation angles. A 0.05-second bracket describes temporal sampling resolution, not human-certified semantic accuracy.

After this timing page is published, complete eligible events are placed in five-second clips with 81 sampled frames. Frame zero is followed by five 16-frame chunks. Crop placement preserves complete actions and seeks the fewest action chunks with symmetric context. Missing boundaries and long events remain in the ledger.