The game utilized the Frostbite 2.0 engine (the same engine powering Battlefield 3 at the time). While this allowed for stunning visual fidelity—dynamic lighting, motion blur, and detailed car models—it was heavily taxing on hardware. However, the issues players faced weren't just about high-end graphics cards struggling; they were about poor optimization.
Players reported severe stuttering, input lag, and fluctuating frame rates that made the twitch-based driving mechanics nearly impossible to master. The game would freeze during critical "quick-time events" (QTEs), leading to instant failures. For many, the game was unplayable in its vanilla state. The frustration was palpable on forums, with many PC gamers feeling they had been handed a shoddy console port. Need For Speed The Run Patch 1.1
Patch 1.1 introduced better handling of variable frame rates. It allowed the game to run smoother on high-end systems, pushing towards 60 FPS and beyond (provided the hardware could handle it). This smoothed out the camera pans during races and made the handling of vehicles feel significantly more responsive. The "micro-stutter" was the bane of The Run players. It would happen during texture streaming—when the game loaded high-res assets on the fly. The patch optimized the streaming engine, reducing the frequency and severity of these hitches. While it didn't eliminate all loading pauses, it made the gameplay loop consistent enough to be enjoyable. 3. Input Lag Fixes A major complaint in the vanilla version was the delay between moving the steering wheel (or analog stick) and the car reacting on screen. Patch 1.1 tightened the input polling, ensuring that the connection between driver and vehicle felt direct and instantaneous—a necessity when you are dodging traffic at 200 mph. 4. Graphical Tweaks The patch also resolved issues with specific graphical effects. Some players experienced flickering shadows or textures that popped The game utilized the Frostbite 2
