Search papers, labs, and topics across Lattice.
To evaluate whether Video-LLMs possess genuine physical motion perception required for world models, the authors introduce MotionBlind, a contrastive benchmark isolating speed, magnitude, and direction across paired, near-identical video clips. The evaluation reveals that open models perform near the 6.25% chance baseline regardless of model scale, temporal sampling strategy, or frame density. Even frontier systems like Gemini 3.1 Pro fail to discern relative action speeds, indicating that current temporal visual representations remain fundamentally insensitive to motion dynamics.
Video-LLMs can perfectly label every object in a scene yet collapse to near-random chance when simply asked which of two identical actions moved faster.
Video large language models (Video-LLMs) are increasingly used as the perceptual front end of world models, a role that assumes they can read motion: how fast something moves, which way it travels, how hard it is pushed. We show they cannot. A Video-LLM can watch two clips of the same person in the same room, name every object in both, and still fail to say which clip moves faster. We introduce MotionBlind, a contrastive benchmark of self-recorded video for physically grounded motion(speed, magnitude, and direction), the variables a world model must predict. Each instance is a pair of near-identical clips that differ only in motion. Each clip carries two complementary yes/no questions, giving four items per instance, and a model earns credit only if all four are correct. We report Instance Accuracy(IAcc), which has a 6.25% chance floor. Single-frame, appearance, and language-only shortcuts all collapse to it. MotionBlind complements the recent TimeBlind benchmark. We run a controlled study of six open and two frontier Video-LLMs, varying whether the video is present, whether frames are shown in the correct temporal order, and how frames are sampled (1 to 24 frames, four selection strategies). Open models sit near the 6.25% floor, and scale does not help. Removing the video drops every model to zero IAcc, and shuffling frames collapses IAcc to chance, so the task genuinely needs video in order. Neither more frames nor smarter frame selection closes the gap, because these change which frames are seen, not whether motion is read. Only Gemini3.1 Pro clears the benchmark overall, and even it fails on speed. A frontend that cannot tell two speeds of the same action apart is not yet a trustworthy source of supervision, reward, or evaluation for a world model.
