Star Wars Jedi: Survivor is being patched up good and proper

Star Wars Jedi: Survivor lightsaber fight

Star Wars Jedi: Survivor has numerous issues pre-launch, reviewers have reported, at least some of which are being addressed with patches.


Ahead of the launch of Star Wars Jedi: Survivor, journalists have reported a catalogue of performance issues with the game, including a frame rate that often struggles to hit 60 fps. A pre-release patch was dropped on 25 April, which Patrick Klepek at Waypoint addressed in his review. He said that the game’s “gnarly performance issues” on PS5 have “largely disappeared” as a result of the patch, which dropped a day ahead of the game’s review embargo.

The game is also set to receive a launch-day patch today, which EA has said will fix bugs, address performance issues and add more accessibility features. However, it’s still too early to say whether the pre-release and launch-day patches have addressed all of the performance issues seen in the game so far. The same tweet from EA promised more patches in the weeks ahead.

Star Wars Jedi: Survivor has already been delayed by six weeks in order to address bugs and “enhance performance, stability, polish, and most importantly, the player experience”, according to a statement from developer Respawn back in January. It appears the studio is working feverishly right up until the last minute to fix the performance issues with the game.

PC Gamer reported that the PC version of Jedi: Survivor suffered from frame rates in the region of 25-30 fps ahead of the pre-release patch, which increased them to around 40-50 fps. It’s currently unclear what kind of improvements will be made with the launch-day patch.

We do know that Jedi: Survivor will require a hefty download. The PC version comes in at around 155 GB, in addition to the two patches, while the physical PS5 and Xbox versions require a mandatory download of tens of gigabytes, because the game is seemingly too big to fit on one Blu-Ray disc.

Leave a Reply

Your email address will not be published. Required fields are marked *

More like this