In an unexpected twist of fate, a two-decade-old classic, Grand Theft Auto: San Andreas, has become the center of attention due to a peculiar interaction with the latest Windows 11 24H2 update. Initially, it appeared that the update had caused the Skimmer plane in the game to vanish entirely, leading many to speculate about potential faults within Microsoft’s software. However, a thorough investigation revealed that the issue stemmed from a coding error within the game itself, rather than any misstep by Microsoft.
Neowin reported on this curious incident, which was meticulously detailed by developer Silent, known for his work on SilentPatch—a project aimed at enhancing older PC games, including various titles in the GTA series. The investigation uncovered that when players attempted to spawn the Skimmer, it would inexplicably launch into the sky, seemingly defying the laws of physics.
The root of the problem was traced back to the vehicle’s ‘bounding box,’ an invisible structure that defines the model’s boundaries. An incorrect calculation for the Z axis, which determines height, had been present in the configuration file. Prior to the 24H2 update, this error had gone unnoticed, as the game managed to read the positioning values from the previous vehicle, a van, albeit imperfectly. However, the update altered the way the game processed these values, leading to the plane receiving an astronomical Z value, effectively propelling it into the cosmos.
Analysis: Too quick to pin the blame
This incident serves as a captivating reminder of how minor bugs can linger unnoticed for years, only to be exposed by seemingly unrelated changes in software. The 24H2 update, built on a new platform named Germanium, introduced a series of intricate modifications that inadvertently affected the game’s code. This foundational shift was essential for the launch of Arm-based (Snapdragon) CPUs, which powered the first Copilot+ PCs, thus necessitating the update.
The unexpected behavior and peculiar bugs associated with the 24H2 update may be attributed to the extensive under-the-hood changes that were implemented. This complexity can lead to unintended side effects, as seen in the case of the Skimmer. Furthermore, this episode highlights that not all issues can be laid at Microsoft’s doorstep. Initially, many, including myself, were quick to assume that this glitch was yet another consequence of the 24H2 update. However, it became clear that the fault lay with the coding practices of Rockstar Games.
While there is certainly justified criticism directed at Microsoft regarding the overall bugginess of the 24H2 update, it is essential to recognize that the intricacies of software development can sometimes lead to unexpected outcomes. The hurried rollout of this update, possibly to meet the launch timeline for Copilot+ PCs in summer 2024, may have contributed to the perception of a rushed product. Yet, as this incident illustrates, the interplay of software updates and legacy code can produce surprises that are both fascinating and perplexing.
