Reviewers Don’t Notice Nintendo Switch Port Of Star Wars: Knights Of The Old Republic II Launches With Game-Breaking Bug

A number of reviewers praised the Nintendo Switch port of Star Wars: Knights of the Old Republic II despite releasing the game with a major bug.

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

RELATED: The official Star Wars Twitter account gives its thumbs up to a fan’s dog stack who responded to Pride Month coverage by asking for the franchise to remain apolitical: ‘There are more of us’

Shortly after the 2004 port of the title was released on June 8, players discovered that the game would crash during the “Basilisk Crash” cutscene. Worse, as this cutscene was played as part of the main story, this bug prevented players from beating the game.

This failure was acknowledged by Aspyr, the studio that ported the game, after a user tweeted them about the issue.

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

“Are you aware that there is no way to end this game?” demand @Moo_Resolutions. “I’ve been stuck on the onderon basilisk crash for a week now. What is the eta on a patch? »

“Hello, this is a known issue that will be fixed in the next patch,” Aspyr Explain. “Although we cannot provide an ETA at this time, we will certainly notify you when the patch is live. You can click the “Follow” button in this article to get the latest information in your inbox”.

Source: @Moo_Resolutions Twitter, @Aspyr Twitter

RELATED: 10 Coolest Star Wars Alternate Style Lightsabers

“Yes, I was one of the users who reported it before it was a known issue,” @Moo_Resolutions claimed in response. “Just to be clear, you know there’s no way to finish this game right now?”

In turn, Aspyr confessed, “Yes, we are aware and our development team is working to deliver the fix as soon as possible. We apologize for the inconvenience and appreciate your patience in the meantime!”

Source: @Moo_Resolutions Twitter, @Aspyr Twitter

At the time, Aspyr recommended users to cheat to get around the problem, explaining on the port’s official site support page“For now, our suggested workaround is to get past the point where the game crashes using the cheat menu.”

“To do this, triple click the left thumbstick, open the cheat menu and select Warp,” they continued. “We recommend that you warp to a random location on the party select screen before the cutscene, otherwise you’ll go solo after warping. Then follow the same steps above to switch to OND504. Make sure to do not head to the Merchants’ Quarter, as your game will crash.

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

RELATED: Obi-Wan Kenobi writer Joby Harold can’t even keep his story straight in an interview, let alone an episode of Obi-Wan Kenobi

While the fact that the Switch version of KOTOR II launched with such a devastating bug was surprising, what was even more surprising was the fact that game reviewers apparently failed to spot the problem.

Following the lifting of the game review embargo, check out the global website Metacritic reported that the port received an average early review score of around 79%, with all but four of fifteen reviewers scoring 80 or higher.

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

RELATED: ScreenRant’s Star Wars Article Sums Up Everything Wrong With Left’s Racial Perspectives

pocket tactics‘ Kayleigh Partleton gave KOTOR II a 9 out of 10, noting how “Aspyr has done a phenomenal job of bringing it to a Switch audience.”

“As a result, I have no comment on performance other than that the game runs well and I encountered minimal issues during my time with it,” Partleton wrote. “The only hiccup I can think of is that during the iconic opening credits, the words stretched out a bit, but beyond that moment everything flows beautifully.”

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

God is a GeekLyle Carr also scored a 9 out of 10, praising, “If you’ve ever played Knights of the Old Republic II, chances are you just want to know how well the game runs on Switch. Well, I can happily confirm that once again Aspyr has knocked it out of the park.

“Load times are low, framerate is stable, and the game even looks a little better than on the poor old Xbox,” Carr said. “Playing a full, sprawling Bioware game on a handheld always fills me with joy, and I absolutely wouldn’t want to play it anywhere else.”

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

RELATED: Rumored Star Wars: Reva to headline the second series after Obi-Wan Kenobi

On YouTube, SwitchUp’s Mark was one of the few reviewers who attempted to update their review after discovering the bug, albeit within the limits of the uploaded video format.

Initially they criticized KOTOR II’s performance for sometimes not reaching 60 FPS (drops to around 30FPS in the same places it did when running on PC), textures turning black when playing too long , and said they experienced crashes, and recommended frequent manual saves.

“It wasn’t a break, and in 20 hours three crashes doesn’t sound like the worst thing ever, but it’s probably about three or four hours of lost progress,” Mark warned.

The title of the video was later updated to add “SEE TOP COMMENT!”, which was directed by SwitchUp themselves and was updated to let viewers know, “A few things have come to light, firstly it seems like a bug on the last island literally stops completion.”

“Second, when the DLC comes out, it will kill your current saves,” SwitchUp explained. “You will literally have to start over…ughhhh. Not great.”

Source: YouTube SwitchUp

RELATED: Social justice activist Sam Maggs has announced that she has quit the Knights Of The Old Republic remake

Only the lowest rated review on Metacritic for KOTOR II, that of Joshua Duckworth as written for Rant gameseemed to mention bugs, though they bury the lede somewhat, starting by noting how the game had “a host of smaller bugs that players can arguably ignore” such as dipping audio, invisible walls intrusive, with the AI ​​not acting or causing allies and enemies to jump.

“It’s par for the course in most games,” Duckworth said, before claiming, “However, during our time with the game, it crashed constantly – at least once every hour.

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

“The game seems to be aware of this even, as its seemingly most common loading screen trick is ‘save often and in more than one location,'” he said. “A game has to work, and functionally that takes a lot of players.”

Along with mentioning the Basilisk Crash bug, Duckworth detailed a similar one that could show up when players board the Ebon Hawk.

Despite his admission that he couldn’t complete the game, the KOTOR II game reviewer received 2.5 out of 5, concluding that it was “great when it works, but the frustrating problem is getting it to work” .

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

Kira C made no mention of any game-breaking bugs in his review for Pure Nintendobut pointed out how, “from what I’ve reviewed, there are bugs that weren’t in the original game or other ports.”

These included graphics becoming “mudtier” over time, only resetting when a player reloaded their save, poor cinematic audio quality, and crashing before a cutscene loaded.

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

Warning that it was “not the best port on the Nintendo Switch”, Kira admitted that they “can’t recommend it as much as its predecessor unless you want a portable copy of KOTOR II”.

“Of course, updates could be made to fix the various bugs,” they concluded, ultimately giving the game a score of 6.5 out of 10, “but if you want to try this version, be aware of the issues and save frequently so you don’t lose anything if it crashes!

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

Conversely, a number of YouTube outlets mentioned the game-breaking bugs in their respective reviews.

One such channel was GameXplain, which in its June 8 review of the game recalled that “the game crashed me a few times. Fourteen times to be exact.

“And that doesn’t include the game-breaking bug that crashed my game easily ten more times when I tried to get around it, which I couldn’t,” they said. “I can deal with random crashes, but a game-breaking bug is unacceptable. You may not experience it yourself, but I cannot recommend the game at this time, in case you encounter it yourself .

Finally, on June 30, Asyper released a fix for these issues.

As noted in its patch notes, this patch addresses “a crash that would occur after certain cutscenes (i.e. the Basilisk scene on Onderon)”, “an issue where the game would crash on certain mid saves. /endgame.(Dantooine, Korriban)”, “Fixed an issue where players could get stuck in a loading screen loop when Sith Troopers boarded the Ebon Hawk on Peragus”.

Source: Star Wars Knights of the Old Republic II: The Sith Lords (2004), LucasArts

What do you think? Let us know on social media and in the comments below!

NEXT: Star Wars: Obi-Wan’s Final Episode Ends the Franchise

About Jason Zeitler

Check Also

Little League World Series Baseball 2022 will launch on Nintendo Switch next week

Little League Baseball World Series regional tournaments, including the United States Championship, are in progress …