Any fan of the Star Wars franchise will know that the Star Wars: Knights of the Old Republic and its sequel Star Wars: Knights of the Old Republic II—The Sith Lords are some of the best games to have ever been made around the Star Wars universe. So good in fact that they’re still being ported onto newer systems these days, with the latest being Star Wars: KOTOR II that launched onto the Nintendo Switch earlier this month.
However, if you’ve recently got yourself Star Wars: KOTOR II on the Switch, you might want to play it just a little slower than you normally would. It seems as though that—mild spoilers ahead—when you land on Onderon and enter the Basilisk Crash cutscene, there’s a high chance that the game will end up crashing. Plenty of gamers have since reported the issue, with some even finding loopholes to skip the cutscene using a cheat menu.
Aspyr, the game studio that carried out the work to port the game to the Nintendo Switch has since confirmed the issue. They had first replied to a user complaining about it by stating that it’s a known issue. The Aspyr team also confirms that this basically means that the game can’t actually be completed properly right now. There’s also now a support page highlighting the issue on the Aspyr website.
Aspyr did however mention that they’re currently working on it, and that the fix will come in the next patch for Star Wars: KOTOR II on Switch. That being said, they were unable to provide an ETA for when the patch will be available. Needless to say though, many gamers aren’t happy that Aspyr released the game in a state that quite literally wouldn’t allow anyone to finish the game. If you’re planning to buy the game for yourself, it’s safe to say that you probably shouldn’t until Aspyr issues a fix for it.
“We’ve received player reports of a game crash occurring after the Basilisk Crash cutscene when landing on Onderon.
This is a known issue and will be addressed in the next patch. We are currently investigating workarounds for this issue and will update this article with any new information and patch dates as we get them,” – Aspyr
Funnily enough, this mistake from Aspyr almost has a feeling of deva ju to it, as back when Star Wars: KOTOR II first debuted in 2005, a couple of reviewers had also highlighted the game being in an ‘incomplete’ state. There were plenty of bugs and glitches in the shipped product that was eventually blamed on the developers rushing it to meet deadlines.