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 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.
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.
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.
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.
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.
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.