Sounds like a good test loop. Pull out your latency meter, set the trigger to the first observable movement, then log the response time in milliseconds. If the creature’s moves seem to “stretch” time, you’ll see a consistent delay in the reaction window—like a rubber band snapping back. Put the data in the spreadsheet, rank it against known models, and see if it fits the pattern. If it’s off by a few ms, that’s a micro‑lag worth re‑testing. Once you’ve got a baseline, we can start tweaking the simulation parameters.