EA has announced that Star Wars Jed: Survivor, Respawn's sequel to the action-adventure Star Wars game featuring Cal Kestis, finally has a release date. It'll be out September 17.
Sales on current-gen consoles must’ve not been great
I played it on my RTX 3070 shortly after launch, and while there were certainly some stutters here and there and the very occasional crash, for the most part it actually ran fine. I think the poor quality of the PC port has been seriously overblown. Granted I don’t care much about sustaining insanely high frame rates, but the game itself was amazing on its own, and even better having played and enjoyed the first one. Well worth any remaining technical glitches.
I’ve got a 1660Ti, and it’s not perfect but smooth enough to play med settings on 1080p. The biggest thing holding me back was VRAM, so I’m interested how they address that on the older consoles, with an eye toward better performance for me.
Sounds like you just didn’t notice/remember the problems in that case. There was/is performance issues that will show up regardless of your hardware setup. “Runs fine on my pc” is simply not true, unless your pc runs on magic.
I mean if you want to invalidate my lived experience, sure. Played on release on a 5600X, RTX3070 and 32GB of RAM, 1080p, almost everything maxed out. Open areas on Koboh saw a drop to mid-40 fps, but other than that, I had one hard crash and no bugs I noticed.
I had the same experience with pretty much the same hardware. I played right after launch and had one or two crashes and a few stutters here and there, but otherwise I found it to be a surprisingly stable game, especially considering the wildly negative press it was getting at the time.
Nothing wrong with not noticing stutters, on the contrary you’re probably lucky to not notice that kind of stuff. However when the problems are documented to be hardware independent and shows up on far more powerful hardware than your own, it’s not a case of “works fine on my computer”.
Something like shader compilation stutter will still cause issues for the top end CPU in 10 years time for old poorly designed UE5 games.
I suppose I’m somewhat fortunate to have been a poor bastard for most of my life. 25fps with moldy potato settings was just fine, as long as the game didn’t crash or deep fry the CPU, so I’m not as sensitive to the occasional drop below 60fps and don’t feel slighted when I have to turn some settings down. Though I can understand being incensed when you’ve poured thousands into a bleeding-edge gaming rig that’s supposed to handle anything at 4k, maxed out and a stable 120fps and it’s the game itself dragging your experience down.
But the stutters weren’t the only problem people reported early on. There were cries of the game being unplayable, on account of endless bugs, visual glitches and repeated hard crashes. Worst I got was the normal mapping on Cal’s face getting real weird in certain lighting conditions. That’s hardly game-breaking.
I’m somewhat insensitive to it myself but shader compilation stutter is something that is measurable and reproducible so there aren’t any room for arguments around it.
Other problems, yeah they may be system dependent although something like animation rubber banding I suspect would be the same across systems, though hard to identify if you aren’t experienced.
People don’t like being confronted and told they’re objectively wrong. It’s not a new phenomenon that people report not experiencing problems that we know all systems, regardless of computing power, encounter when playing a given problematic game. And people get defensive when told they just didn’t notice it.
Some stranger’s 5600x doesn’t randomly have the hardware to compile shaders at 10x the speed of top of the line CPUs. A game that suffers from shader compilation stutters will do so on all systems. To say it didn’t stutter for you means either that:
The game never compiled the shaders
You already had the shaders pre-compiled, which isn’t a thing on normals PCs
You never noticed
You’re lying
It’s impossible to avoid for games that suffer from it.
Is it finally stable and playable on PC?
Without checking I’m going to go out on a limb and say no.
as is tradition with pc games now
I played it on my RTX 3070 shortly after launch, and while there were certainly some stutters here and there and the very occasional crash, for the most part it actually ran fine. I think the poor quality of the PC port has been seriously overblown. Granted I don’t care much about sustaining insanely high frame rates, but the game itself was amazing on its own, and even better having played and enjoyed the first one. Well worth any remaining technical glitches.
yeah it worked fine on my 3080 too.
Ok, now someone do a mere mortal take.
It plays much better than it did on launch.
I’ve got a 1660Ti, and it’s not perfect but smooth enough to play med settings on 1080p. The biggest thing holding me back was VRAM, so I’m interested how they address that on the older consoles, with an eye toward better performance for me.
I played it with no issues on my PC at release, so … yes?
Sounds like you just didn’t notice/remember the problems in that case. There was/is performance issues that will show up regardless of your hardware setup. “Runs fine on my pc” is simply not true, unless your pc runs on magic.
I mean if you want to invalidate my lived experience, sure. Played on release on a 5600X, RTX3070 and 32GB of RAM, 1080p, almost everything maxed out. Open areas on Koboh saw a drop to mid-40 fps, but other than that, I had one hard crash and no bugs I noticed.
I had the same experience with pretty much the same hardware. I played right after launch and had one or two crashes and a few stutters here and there, but otherwise I found it to be a surprisingly stable game, especially considering the wildly negative press it was getting at the time.
Nothing wrong with not noticing stutters, on the contrary you’re probably lucky to not notice that kind of stuff. However when the problems are documented to be hardware independent and shows up on far more powerful hardware than your own, it’s not a case of “works fine on my computer”.
Something like shader compilation stutter will still cause issues for the top end CPU in 10 years time for old poorly designed UE5 games.
I suppose I’m somewhat fortunate to have been a poor bastard for most of my life. 25fps with moldy potato settings was just fine, as long as the game didn’t crash or deep fry the CPU, so I’m not as sensitive to the occasional drop below 60fps and don’t feel slighted when I have to turn some settings down. Though I can understand being incensed when you’ve poured thousands into a bleeding-edge gaming rig that’s supposed to handle anything at 4k, maxed out and a stable 120fps and it’s the game itself dragging your experience down.
But the stutters weren’t the only problem people reported early on. There were cries of the game being unplayable, on account of endless bugs, visual glitches and repeated hard crashes. Worst I got was the normal mapping on Cal’s face getting real weird in certain lighting conditions. That’s hardly game-breaking.
I’m somewhat insensitive to it myself but shader compilation stutter is something that is measurable and reproducible so there aren’t any room for arguments around it.
Other problems, yeah they may be system dependent although something like animation rubber banding I suspect would be the same across systems, though hard to identify if you aren’t experienced.
Not sure why you’re being downvoted. I honestly wish I couldn’t detect stutters.
People don’t like being confronted and told they’re objectively wrong. It’s not a new phenomenon that people report not experiencing problems that we know all systems, regardless of computing power, encounter when playing a given problematic game. And people get defensive when told they just didn’t notice it.
No, it’s because you’re being a petulant turd when people inform you that you are objectively wrong.
Some stranger’s 5600x doesn’t randomly have the hardware to compile shaders at 10x the speed of top of the line CPUs. A game that suffers from shader compilation stutters will do so on all systems. To say it didn’t stutter for you means either that:
It’s impossible to avoid for games that suffer from it.
All computers run on enchanted runes in graven rocks, so yeah, it runs on magic.
A course in computer architecture would dispel that mystery real quick
I have a degree in computer engineering and have been designing and implementing embedded systems professionally for decades
It’s magic, and I am a wizard.
Sure
Don’t make me
hackcurse you with aprogramspellI tried about 2 months ago, it was not.