[rich_sasha]

Why 2k FPS? I'm not being facetious; human eye sees, apparently, at around 25fps, which is why this is what TVs and cinemas used to use. At that rate, and 144kph, say, the car moves 1.4m between frames.

Fine, so maybe you think this is too much. But 10x this still gives you 14cm between frames, at what is already speeding in most jurisdictions I know of.

2000 FPS seems to my untrained eye like a problem, not a feature.

[dns_snek]

> human eye sees, apparently, at around 25fps

What do you mean by "sees"? I'll bet you that you can't walk around wearing a VR headset running at 25 FPS for more than 30 seconds without violently emptying your stomach. Trying to watch a movie on a display that doesn't exhibit motion blur also makes me motion sick.

Human brain doesn't see in terms of frames at all. There's a limit where an increase in FPS likely becomes imperceptible to most people but that limit is at least 10 times higher (from personal experience), likely more.

[Vilian]

Humans don't see around 25fps, it depends but the maximum for a trained person or competitive player is 300hz

[storus]

Because you are processing a sequence of a fixed length in deep learning models and the more frames you have, the more accurate your FSD output is. Driving 1.4m between the frames with single-frame accuracy of 80% is quite risky and input correction quite discrete; 14cm is still risky for a proper trajectory planning. Now make it in millimeters and suddenly your trajectory is nearly perfect with only little noise.