Airbus Jr
Banned
Yo why this guy is banned?Thread aged like a fine milk.
Hes correct ( in the recent Control series s vs ps5 size comparison)
Last edited:
Yo why this guy is banned?Thread aged like a fine milk.
Yeah and above all that they'll probably stop making Xbox games altogether....... And I don't know what I'm talking about just like all the other fanboys complete nonsense.Above all of that Sony has already licensed Oodle Kraken and Oodle Texture for all PS5/PS4 devs so they can use them for free. Now with Epic Games having RAD Tools under their sleeves it'll make it the obvious choice across the board. It's pretty likely to throw BCPack and ZLIB out of the window for all 3rd party devs.
Yo why this guy is banned?
Hes correct ( in the recent control size comparison)
Yeah and above all that they'll probably stop making Xbox games altogether....... And I don't know what I'm talking about just like all the other fanboys complete nonsense.
You know what I think you're being conservative, I think they can push it even further to a 100% it's only 3% more! I've heard a rumour so don't quote me on this but I've heard..... The compression in the PS5 is so good that Cerny compressed himself! He can now work from the inside to push things even further.I think he was being sarcastic. He's mostly a Sony guy, also I suspect he read all the OP to post a proper answer. Also speaking of milk, this is a long life milk.
Actually 29% Kraken advantage over ZLIB is just for general data losslessly, Oodle Texture has just amplified that to 42% as Oodle Texture can compress up to 50% yet it's extremely hard to distinguish from raw texture. You can push further up to 97% with very impressive results and minor detail loss if you go check out the official website example.
You know what I think you're being conservative, I think they can push it even further to a 100% it's only 3% more! I've heard a rumour so don't quote me on this but I've heard..... The compression in the PS5 is so good that Cerny compressed himself! He can now work from the inside to push things even further.
This topic is really pushing your buttons eh ?You know what I think you're being conservative, I think they can push it even further to a 100% it's only 3% more! I've heard a rumour so don't quote me on this but I've heard..... The compression in the PS5 is so good that Cerny compressed himself! He can now work from the inside to push things even further.
You guys are hilarious.This topic is really pushing your buttons eh ?
You guys are hilarious.
Sure buddy, sure .You guys are hilarious.
In Control they most probably don't use Kraken compression because otherwise the loading times would be much lower than that. They all seem limited by the CPU here with virtually the same loading times.ZLIB is free, open source. PS4 and all XSX have ZLIB decompressors. Oodle Kraken needs to be licensed, and Sony licensed that for PS5 and PS4 so devs use it for free, but PS4 is using HDD so it needs more duplicates sitting at 39GB vs 42GB on XSX|S. If you don't understand what's going on here take a deep breath and start reading.
In Control they most probably don't use Kraken compression because otherwise the loading times would be much lower than that. They all seem limited by the CPU here with virtually the same loading times.
I think the size difference is related to the use of oodle textures on PS5 (because it's free to use there).
With Kraken compression, the loadings will be much faster on PS5. Look at Nioh2 loading times.I think the game is still a 2019 game, so even with Kraken it won't be as instant as PS first party games that are built around PS5. But that can still be true.
With Kraken compression, the loadings will be much faster on PS5. Look at Nioh2 loading times.
PS4 (CPU + HDD): 13s
PS5 BC & multiplats legacy (CPU + SSD): 8s
PS5 native (Kraken + SSD): 2s
Most multiplats on PS5 (like Control) are in the second category (CPU + SSD).
Yo why this guy is banned?
Hes correct ( in the recent Control series s vs ps5 size comparison)
He wasn’t banned for that. Scroll to the bottom of any page on GAF and click on BansYo why this guy is banned?
Hes correct ( in the recent Control series s vs ps5 size comparison)
He is banned because he can't control himselfYo why this guy is banned?
Hes correct ( in the recent Control series s vs ps5 size comparison)
With Kraken compression, the loadings will be much faster on PS5. Look at Nioh2 loading times.
PS4 (CPU + HDD): 13s
PS5 BC & multiplats legacy (CPU + SSD): 8s
PS5 native (Kraken + SSD): 2s
Most multiplats on PS5 (like Control) are in the second category (CPU + SSD).
With Kraken compression, the loadings will be much faster on PS5. Look at Nioh2 loading times.
PS4 (CPU + HDD): 13s
PS5 BC & multiplats legacy (CPU + SSD): 8s
PS5 native (Kraken + SSD): 2s
Most multiplats on PS5 (like Control) are in the second category (CPU + SSD).
Awesome post, Op.p, really interesting. Thanks for putting it all together!
Speed up settings here
8 GB smaller patch size on PS5 vs XSX, very interesting.Another example of superior compression? Thanks to Rea for sharing.
74.7% smaller update on PS5 vs Xbox Series S|X.
Another example of superior compression? Thanks to Rea for sharing.
74.7% smaller update on PS5 vs Xbox Series S|X.
8 GB smaller patch size on PS5 vs XSX, very interesting.
Like what I'm seeing. Control, this and maybe others to come. If this continues then the PS5 will have more internal storage than the X. Now Sony need to start with the expandable SSD compatibility hopefully soon.
74.7% smaller would mean the PS5 patch is 5 GB. Your math is off.Another example of superior compression? Thanks to Rea for sharing.
74.7% smaller update on PS5 vs Xbox Series S|X.
Another example of superior compression? Thanks to Rea for sharing.
74.7% smaller update on PS5 vs Xbox Series S|X.
Another example of superior compression? Thanks to Rea for sharing.
74.7% smaller update on PS5 vs Xbox Series S|X.
Stupid question, maybe, but why would compression influence patch sizes? I assume the XSX can decompress the same files as the PS5. The PS5 is just faster at it.
Stupid question, maybe, but why would compression influence patch sizes? I assume the XSX can decompress the same files as the PS5. The PS5 is just faster at it.
74.7% smaller would mean the PS5 patch is 5 GB. Your math is off.
Cerny was really thinking beyond once again. PS5 is not the best of an old tech, but bring new ones to the table.
quick math lecture: it's ((1953-1118)/1953)*100 = 42.7%Yes, checked again and maybe I used the PS4 version by mistake, it's 65.5%:
42.75% smaller ^
Different compression methods give different results. Like ZIP vs RAR and stuff.
quick math lecture: it's ((1953-1118)/1953)*100 = 42.7%
Your math was kinda correct but the wrong way around, it's Xbox is 74.7% larger, PS5 is 42.75% smaller.Textures are compressed differently and using different methods. Using Kraken + Oodle Texture on PS5/PS4 while using ZLIB + BCPack on XSX|S. It's already licensed for PS4/5 devs, so to use Kraken + Oodle Textures on xbox devs must buy a license or MS provides it to them like Sony did. Compressing the same files like PS5 might not decompress properly/fast enough and could result in into bad LOD lag or worse pop-ins. Also CPU has some work on XSX|S vs totally independent decompressor on PS5 so it can hurt framerates on XSX|S.
Yes, checked again and maybe I used the PS4 version by mistake, it's 65.5%:
Indeed, he really made a great design along with the Sony design team.
Yeah I know, but what's stopping the devs from compressing with the same method in the patch and then decompressing to a format the XSX can support in games?
Unless, of course, the XSX simply can't decompress said files.
quick math lecture: it's ((1953-1118)/1953)*100 = 42.7%
Depends on the compression used you need to do it in software on the CPU or GPU making load times worse or potentially wasting shader cycles on decompression.Yeah I know, but what's stopping the devs from compressing with the same method in the patch and then decompressing to a format the XSX can support in games?
Unless, of course, the XSX simply can't decompress said files.
Indeed. Some people have issues with percentages. The XSX version is 65.5% bigger, while the PS5 version is 42.7% smaller. Give or take.
It's 11.18GB, the first number you did was correct, 74.7%.Yes, the update is 42.7% smaller on PS5, and 65.5% bigger on XSX.
It's 11.18GB, the first number you did was correct, 74.7%.
that's such a huge difference.
Slowly but surely we're starting to see devs start to trickle in the benefits of that I/O.... whether that be game install sizes, patch sizes, instant loading etc...
We can only go up.
If this trend continues that means that 605GB left will have the same/better overall breathing room as the XSX 802GB, but the XSS will be the worst deal with only 364GB left.
Because of krackers and noodles?That's why I picked the ps5 as my console of choice.