Can't June 4th just come already?
Yeah. Need the data stream from ssd to be prioritzed then allocate audio ray tracing its data.
SWWS have their hands on PS5 io technology for 3 years now. Could be some crazy upcoming games.
At 1080p...
The problem isn't that it can't run. It probably can with worse results. But it's Windows Central and we know exactly what they're trying to do here.
4k textures are x4 smaller than 8K textures, not x2. And there is no reason to have lower-quality textures or models, they will just stream slower which means more pop-in but not the same pop-in we know today on consoles.
It's much more than just that, it's fully path traced. That's the most intensive RT demo I've ever seen until NVIDIA showed their marble demo which melted my face.
What Epic is using can't use the RT hardware because they don't use rays. They are using three GI methods in Lumen and none of them use rays (actually, UE4's SSGI might but even if it does, it casts very few rays), probably because they want to be hardware-agnostic.Well, so far, it's been using "software-based" global illumination on the PS5, which is the most critical type of Ray Tracing that's much more visible than reflections which need certain reflective surfaces. So with that lifted with HW RT later on when they implement it that demo should benefit from higher resolution/framerates. Plus, we're not sure if it was utilizing The Tempest 3D Audio engine or it was using only traditional, pre-baked audio behavior. Global illumination, shadows, reflections were all used in video in real time to some extent, not sure if ray-traced audio. All of those taxing types aren't utilizing the built-in HW RT.
You've just described my wet dream.
8K textures are actually 8192 X 8192, not 7680 X 4320 like TV resolution. When developers talk about texture sizes they are talking about 1:1 ratio and always in the 2^x. So 1K is 1024x1024, 4K is 4096x4096, and so on. But even if you are using 8K textures you are still paging them and using different MIPS so it's not like there are 24 8K textures in memory at the same time. Also, BCPack and Kraken will make them 30%-60% smaller to stream on average.
If it uses memory bandwidth, it goes through the memory.
No, you misunderstood my point, the comparison of an uncompressed 8K cinema texture to an 8k DXT lossy compressed texture is like comparing to a lower resolution texture in absolute PQ terms of signal to noise.
Oh, got it. I disagree because XSX doesn't use DXT, it uses BCn and BC7 looks wonderful even at ~70% compression, not to mention closer to 60% and whatever enhances BCPack has over BC7. When you add on top of that all sorts of filtering and post processing, I doubt even DF will be able to tell the difference. I mean, most users can't even tell when an image is reconstructed or if VRS is used.
June the 4th will come and go. Then some presentations will be suspicious and it’ll all starts again until the July event. Then comparisons between games that are not the same game. Console warring all the summer and then in November, finally, DF comparisons between the same game.
Don't forget the warring on PS5 Pro VS XSX-X and then, after they are out, speculation on PS6 VS next-box starts!
Yeah it really is a TRUE GENUINE NEXT-GENERATION LEAP!!
Guys, we are in for a treat for next-gen, if this is just a tech demo thrown around easily like that, you'll see games with crazier graphics, animations, destruction, AI, world simulations and so many stuff in the next 3 years.
Look at even Richard Leadbetter's opinion and what he said about it here in this picture below:
It's safe to say any headset, especially good ones, would give you great experience. Current PS Gold and Platinum already sport 50mm, and the Platinum supports 3D audio in some selected games (pre-baked 3D audio). So if you have already a good headset you'll enjoy it. If you don't have yet better wait to see a new PS headset or the next Sony 1000XM4 if you have the budget. Avoid bland headsets that lack punchy bass like Astro A40 that I own and it has an optical mixer.
You know I was out of the games stuff. In fact I have to catch a lot of this generation and that’s why I want a PS5: to play a lot of this generation with better graphics in my 4K. I couldn’t care less about HZD2. So I came back recently and then all of this next GeV drama happened and suddenly you can have an account in GAF easily.
Thanks for the size correction. But from the perspective of the UE5 demo, no MIPS are being used (for nanite and GI at least) as far as I'm aware, because you don't require usage of LOD for those.
As far as I know, they are all derivative formats from DXT, and no matter how nice they look - no one said they looked awful - they are not the same as the source texture, and can be downscaled and measured against the uncompressed 4K version in signal to noise, and lower orders. When you are doing UE5 graphics at infinite geometry and texture detail, the noise from lossy compression is going to be more problematic, than in a game like Gear5 using the classic rendering. Ultimately the XsX version has to choose a compromise.
As far as I'm aware, Nanite won't work if there is animation involved. The character in the demo is still rendered the traditional way.
PS5 goes brrrrrrrrrr
I actually don't remember anything regarding MIPS in Nanite, just geometry. I mean, MIPS are still required, they are just streamed in pages on GPU requirement from the SSD to memory, don't they?
Competition is good, especially if your PSU gets some TF!
DXT1 is BC1, DXT3 is BC2 and DXT5 is BC3. No one really calls them DXT and they aren't used much today anymore but I went along because you called them DXT
GI too, at least two out of three methods Lumen uses for GI require none-animated objects and the third is SSGI which IMO looks like shit
Cerny presenting the PS5 pro:
Actually there is point of reference for this(IMHO). RAM speeds have increased linearly over the last few decades, while processors have followed moore's law, so there has always been a shortfall in memory in consoles, and developers will exhaust however much they are given in each generation. So for the UE5 demo, if the PS5 has 16GBs of memory with 448GB/s bandwidth and an IO complex/SSD that can deliver between 4.8GB/s and 22GB/s storage into RAM - which is still an order of 20x -100x less than memory - and we already know that the data per frame being loaded is exhausting the system to the point of needing to use dynamic resolution - a resolution that is directly tied to memory bandwidth exhaustion -IMHO it doesn't sound plausible that the storage device that is still a bottleneck won't be pushed more than 50%.
Only people that use DirectX call them BC - because the underlying techniques they derive from weren't by Microsoft-and I'm pretty sure the BCpack compressor is even fed with a DXTn flag from a link I checked out about 900 pages ago in this threadDXT1 is BC1, DXT3 is BC2 and DXT5 is BC3. No one really calls them DXT and they aren't used much today anymore but I went along because you called them DXT
If you are still using DXT to describe them, you should check out BC7 for instance which gives extremely good quality on the compression rates MS talked about and BCPack should be an upgrade over BC7.
Regarding compromises, You don't have to compromise in quality, you can compromise in delivery time. If the PS5 can stream in extra detail for the asset in 33ms, what's stopping the XSX streaming the same in 67ms? Yes, it will give it a delay of 33ms, and extremly quick pop-in that morphs in, but will it be actually noticeable when it takes 33ms? I have no idea, I guess we will have to wait for DF analysis for that one.
