But another official pulled back the hype claiming that it may cost your wallet. EA suck.Just before dropping the final gameplay trailer for Star Wars Jedi: Survivor, game Director, Stig Asmussen revealed that players can access Coruscant as a playable ground during the course of the campaign, though the big city from the Galaxy far far away may not be a full explorable-open-world. I think I should stop playing it but I really don’t want to which is a testament to how good the actual game is otherwise. It’s just infuriatingly inconsistent and it is seriously spoiling my enjoyment of the game. This is on the Epic preset the game defaulted to at 1440p with RT enabled and FSR2 set to Quality.

They should have delayed the game but as with many publishers these days they seem to be okay with letting their customers beta test the games for them…

I’ve even had the game dips into the teens after a cutscene for 2 or 3 seconds before it returned to 45-55 fps. The game’s opening cutscene was promising as it ran at 90-165 fps (yes, really) on my system with some bad hitches at certain points then when I took control of Cal for the extended walk it was around 70-90 fps with some stutters, I think asset-streaming related, then when you actually got full control and could play it the framerate and cutscenes ran between 28 (yes, below 30 fps) and 65 fps until the last section of Coruscant as described above. The game is simply an absolute mess in my humble view, no matter how much you try and sugar-coat it. To those claiming they are getting 100 fps on the second planet (Koboh) after sub-60 fps performance on Coruscant: have you reached the village area yet because I was getting 70-110 fps on the last section of Coruscant and at the start of the Koboh level but then I reached the village and now performance is again in the 35-65 fps territory with the low framerates, usually in cutscenes but gameplay seldom exceeds 60 fps, leading to a very sluggish and chugging feel to the game.

Star wars jedi: survivor coruscant