Complete Details on Xenos from E3 private showing!
- Thread starter dukmahsik
- Start date
Yes, its confirmed. I just had the CC with the architects. I now have about an hour of audio to go through and get into something coherant.
I've asked, but NVIDIA can't talk about it to any great extent yet, and when you do hear about it I still get the impression that the G70 reviews will reflect more accuracy for the actual architecture.
It'll take some time.
I don't see the relevance in talking about the bandwidth between EE and GS. Sony could claim 48GB/s bandwidth for GS's eDRAM because the bus from GS's graphics core and eDRAM was 48GB/s. The bus between 360's graphics core and eDRAM is 32GB/s. Certain parts of 360's rendering pipeline have a 256GB/s bus to eDRAM (z and stencil buffer) but not the whole thing. So I agree with Mordecaii and Shifty, its misleading to claim 256GB/s bandwidth to eDRAM and not mention that the actual main graphics core uses a 32GB/s bus. Not that its a big deal though with all the other exaggeration and PR crap that goes on in this industry
Deadly Towers
Newcomer
Teasy said:
how is that different from GS?
Megadrive1988
Veteran
looking forward to listening to the CC with ATI architects
Fafalada said:Read what archie wrote - GS has internal component running at a much higher bandwith in a similar manner (though the asociated logic in pagebuffers is pretty dumb
By all means, Sony should have claimed the 150+GB/s number then.
So instead of Smart Memory, it's Dumb Memory?
Jawed said:
Not in reality, because 4xAA will take up more edram, so you have to draw more tiles.
Folks, I don't know how many times I have to say this - 720p + 2xAA DOES NOT FIT INTO 10mb of edram. Period. End of story. The scene has to be tiled , ie - executed multiple times. This is required, as the Xbox360 minimum requirement is 720p + 2xAA. Going to 4xAA may require even more tiles.
AA is 'free' at the cost of having to render scene multiple times due to low amounts of edram. We'll see how it plays out on beta hardware.
Triangles splitting along tile edges will not be required, guardband scissoring (it should be free..) will be enough.Laa-Yosh said:
If the application doesn't cope with tiling itself the driver will probably force geometry to be resent/retransformed (this will take some ALUs time )or cached and reused (this will take some extra memory)
aaronspink
Veteran
fresh said:
Most likely, you are wrong. 720P at 4xAA will most likely fit within 10mb. In the rare cases where a given pixel needs more space for samples than is provided within the edram.
There are lots of alternatives. Even in the tiling case, the scene does not need to be executed multiple times.
Aaron Spink
speaking for myself inc.
EDRAM stores all the samples uncompressed.
It depends.
If you let the driver handle tiling for you it will cost more, cause it would have to cache transformed geometry or it would have to read N times the same dispay list and transform geometry N times per frame.
If one has some spare bandwith and some free mem (not much..) the first option should be almost painless.
More advanced titles would probably handle tiling themselves, rendering N tiles and sending to each tile only geometry that belongs to the current tile (no transformed vertices caching or N read and transform of the same full frame display list), this would not be different from what a lot of multiplayers+split screen titles do now.
a 640x360x4AAxFP16+Z buffer takes 10.54 MB, so if it fits in R500 edram (I don't know the exact amount of edram!) 4 tiles would be enough to render a fulll 720p 64bit 4x AA frame!
This way tiles would be so big that a non managed solution would suffer an absolutely negligible hit, a managed solution would take more overhead.
With a 32bit render target a 3 tiles (1280x240 per tile) solution would nicely fit in R500 edram too.
More I think about R500, more I like it
