It wasn't just the crashes that were hampering Usher's progress. Now he was forced to start over with a gigantic time deficit, racing to clock in under the run's 80-minute estimate.Īt 44 minutes into the run, the game crashed again. The technical issues with The Sands of Time are well-known, but Usher wasn't expecting a crash so early in the run. At one point in the game, Usher skipped a cutscene where the Prince tears off one of his sleeves - as a result, later in the run, his body texture just straight-up doesn't load: The game is known to do a lot of weird stuff on PC, particularly when its player is playing it in such an unintended manner. It's a tall order, and last night's run was made even taller by a series of unfortunate technical difficulties. It's an impressive maneuver, and speedrunning Prince of Persia: The Sands of Time requires that you pull it off dozens of times. ![]() The video above shows Usher demonstrating what the zips look like during his Summer Games Done Quick 2015 attempt. Using those zips, a runner can break the sequence of the game, skipping battles, cutscenes and entire levels in the process.Įleven minutes into the run, the game crashed. Upon using the game's time-rewinding dagger, those steps transfer their total momentum to the action that preceded them, allowing the Prince to "zip" forward through walls or upward through ceilings. The exploit works like this: The player executes an action (usually a jump or lunging attack), and then a series of canceled steps. That's because of a new exploit discovered in February, which has allowed runners to shave about one hour off of the game's former world record time - a colossal improvement that the game's runners have been practicing since its discovery. Though Prince of Persia: The Sands of Time has been around for nearly 12 years, there's been a lot of activity in the game's speedrunning community for the past few months. At midnight last night, a speedrunner by the name of Joe "Henneko_" Usher kicked off a run of Prince of Persia: The Sands of Time that was expected to last a breezy 80 minutes.īy 12:11, the run had gone straight to Hell.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |