In order to quickly address many issues with the game, EA and Respawn Entertainment this morning have revealed patch notes for the update that went out today for the PC version and what they have scheduled for tomorrow for the PS5 and Xbox Series X. We’re pretty sure this won’t remedy all of the complaints from players, but it hopefully seems that they are on the right track to do so.
Check out the details below.
Today, we?ll be deploying a patch for the PC version of Star Wars Jedi: Survivor, and tomorrow (5/2) we?ll also be deploying one for both PlayStation 5 and Xbox Series X|S.
The PC version of the game has already received the fixes coming to console on 5/2.
Please find the patch notes for both below.
5/1 – PC Patch
- Performance improvements for non-raytraced rendering.
5/2 – PlayStation 5 & Xbox Series X|S
- Multiple crashes fixed across PlayStation and Xbox Series X|S and various areas of the game.
- Fixed crashes that were tied to skipping cinematics.
- Performance improvements across PlayStation 5 and Xbox Series X|S.
- Fixed an issue with dynamic cloth inside the Mantis.
- Fixed various rendering issues.
- Fixed an issue with registered Nekko colors not saving.
- Fixed an issue with registered Nekko disappearing from the stable.
- Fixed issues with cinematic dialogue overlapping.
- Fixed various collision issues.
- Fixed an issue with enemy AI remaining in T Pose during photo mode.
- Fixed a freeze that occasionally occurred while talking to Doma.
- Fixed a bug where the BD-oil VFX did not properly render.
- Fixed an issue where players were getting stuck inside the Chamber of Duality if you didn?t save after leaving the chamber and die.
Give whoever came up with that term “Photo-Appa” a raise…like now!
An encore of Iron Man Mark 85 is great an all, but when is the…
You would think a game like BrownDust 2 would do a cake collaboration given how…
If the past is any indicator, we’re gonna be in for a rough time before…
Atsu’s bloody tale of revenge is worth revisiting a year later, especially with its new…
If I had written the headline LRG @ PRG, I’m sure someone would’ve had a…
This website uses cookies.