![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
One standard that works for everyone, including older graphic cards. Not hard to understand.
It's not like Nvidia has only one DLSS standard. DLSS 3 only works on RTX 40 series, which complicates things more. You also have to look at it from the technical support side of things.
Ah, yea that won't do anything here. You're not going to stream textures from the SSD when you have ram, which might be the reason why people find this game better on 32GB of ram. Or just have more VRAM and avoid that problem all together. We're also assuming that Jedi Survivor runs well with max graphic settings on the PS5, which I really doubt it does.
But it's more cinematic!
My understanding is that there are 3 options:
I stopped reading when you said dial down fps to 30.
That's fine I don't care about anyone else at this point. All the pissing and moaning before the game even released is pathetic. People didn't even know what the game was like and were moaning about low fps. You will probably get better FPS on the 4090 if it runs at 30-45 FPS than my 7900XTX, and that is entirely playable. It's sad and utterly hilarious to see all the tears on here.
See, that is exactly as I had suspected it would be. All the tears and whining here have been overly dramatic and ridiculous.
Clearly runs on a 4090, Niner21 above just commented that it "ran great"
I haven't read through this thread much so I can't comment on anyone complaining, but I just wanted to chime in on my personal experience with the game and my hardware.
Much appreciated. There are 2 threads here on the [H] and both had a ton of people complaining about the game before they even had their hands on it.
Yes I just commented in the game thread. Games should be waited to be reviewed at full release only and not these early versions that come out that give a game and the consumer a false reading. Just my .02.
Correct games change right up till release date.
People do this with Intel and just about everything else in the world unfortunately. Don't agree with their opinion then the gloves are off.
Not sure what you think it is hard to understand, what does this statement has to do with your original statement or the question you are answering too.
Which is purely an possible issue if you decide to add DLSS 3 support and has it seem nothing to do about adding DLSS 2 or not outside a pure positive (future option of adding DLSS 3 if you want easier than before)
But you do not have much ram-vram on a console, you have an extremelly limited about a third to an half your medium end PC that will tend to have about 40-48, which I imagine was the nice saving cost strategy, if you mean does not need to on an expensive PC probably true. There must be a way for already uncompressed texture in actual ram must still be faster, let us have good performance when we have 64gb of ram like some pc UE5 title can take advantage of. (And I could imagine that yes that why those new game we see them use 18gb of ram or more now, they can put stuff in much faster ram that would have stayed on the much slower drive, that is with good decompression like DDR3 fast which is extremelly impressive for harddrive, but nothing special vs ram)
Epic now owns Blink who owns the Kraken stuff so they are probably going to roll it into their Lumen/Nanite stuff.
Yes Sony paid for Oodle and built a hardware Kraken implementation and Microsoft made its own BCPack algorithm that was from the ground up only for game texture and an hardware accelerator, who say BCpack does not touch Kraken ?
A DDR-4 ram stick at 3200 peak transfer rate is 25 Gb/s, in dual channel mode goes around 50gb/s, obviously you go more at 4x something in real life than full max theorical bandwith.
Yes, they do have inline decompression, but that is not necessarily unique to the PS5, as part of the NVME standards there is an optional part of the spec that allows for "game-optimized" IO which allows for various protocols to be loaded to the firmware to accelerate game related storage tasks. To my knowledge, Phison is the only company that makes a controller compatible with that part of the standard, they introduced it in the E18 for use with premium NVME devices, but it looks like it became available to any device that uses the E26.
You have to do the compression (but for a yet to be shipped game..) should really not be that big of a deal to change your texture compression from one to another.
That really different, the PS5-Xbox hardware decompression is capable like 4 zen2 core at decompression or something of the sort, Phison I/0, is a capacity to sustain long work on big size IO, for hours, like a openGAMe world with continous stream would do, but I do not think they know what a compressed texture is, it is just that it would be good at something the SmartAccess-Direcstorage workload could typically look like.
On a game you usually use Kraken from the Oodle texture compression choice, Kraken is a Texture compression algo in the Oodle Data compression family (i.e. to make it simple you can use Oodle texture compression or Oodle Kraken texture compression almost in the same way for what we talk):