-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
ATI R300 specs revealed!
Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
first of all can you say, LOAD OF CRAP? Inquirer is full of it. they do this before EVERY product launch, and end up being at least partly wrong.
where did this '107 million transistors' number come from in the first place?? I heard it first mentioned on the Beyond3D boards just a couple of days ago, and no-one could verify the source or anything.
0.15 micron process? well if it has 107 million transistors, then nope, that's not correct.
512 bit? ok you can think what you want.. there's absolutely no point in saying the architecture is 512 bit, becuase it ISN'T ALL MADE OF 512 bit FPU's NOW IS IT?? FRAME BUFFER? 512 bit?? Z-BUFFER? 512 BIT?? I think not. show me one unit on that chip that actually is 512 bit, and THEN you are not a total bulshitter to me..
ok 8 rendering pipelines + 2 texture units each? I doubt it.. fillrate isn't nearly as much of a concern any more.. why add pipes?? the only thing increasing the fillrate is number of textures on a polygon, so you'd think keeping 2 texture units per pipe makes sense, but even John Carmack disagrees with this move.
I don't know about the 16 textures per pass requirement, I don't know much about DX9.
Quad Vertex shader? sure lets take what we have, and double it.. that makes sense.
Vertex shader 2.0 yep.. with 107 rumored transistors you'd better hope that's included..
Pixel shader 2.0? hmm, well perhaps they can do that with 107 million transistors..
displacement mapping support? well as with the P10, it's not mentioned as a spec, becuase it doesn't have a specific unit dedicated towards this operation, it would have to be done with the vertex shaders. I think the R300 is either too far along to support this in 'hardware' so to speak (ie, not wasting FPU units when you could have a dedicated unit doing these calculations), or they were part of the DX9 developement and had to support it. either way, it CAN do Displacement mapping, it's just a question of how it does it.
64 bit colour? 64 bit Z-Buffer? not likely, but we'll see.
FP rendering.. well lets see, considering you already have Vertex shader 2.0 support, you'd assume that..
256 bit DDR SDRAM? been rumored quite a bit, and is even included in the Parhelia (and I think the P10), so it's not totally impossible to think that R300 would be able to do this.
as for the RV250.. I won't comment. it's a long enough post already.
where did this '107 million transistors' number come from in the first place?? I heard it first mentioned on the Beyond3D boards just a couple of days ago, and no-one could verify the source or anything.
0.15 micron process? well if it has 107 million transistors, then nope, that's not correct.
512 bit? ok you can think what you want.. there's absolutely no point in saying the architecture is 512 bit, becuase it ISN'T ALL MADE OF 512 bit FPU's NOW IS IT?? FRAME BUFFER? 512 bit?? Z-BUFFER? 512 BIT?? I think not. show me one unit on that chip that actually is 512 bit, and THEN you are not a total bulshitter to me..
ok 8 rendering pipelines + 2 texture units each? I doubt it.. fillrate isn't nearly as much of a concern any more.. why add pipes?? the only thing increasing the fillrate is number of textures on a polygon, so you'd think keeping 2 texture units per pipe makes sense, but even John Carmack disagrees with this move.
I don't know about the 16 textures per pass requirement, I don't know much about DX9.
Quad Vertex shader? sure lets take what we have, and double it.. that makes sense.
Vertex shader 2.0 yep.. with 107 rumored transistors you'd better hope that's included..
Pixel shader 2.0? hmm, well perhaps they can do that with 107 million transistors..
displacement mapping support? well as with the P10, it's not mentioned as a spec, becuase it doesn't have a specific unit dedicated towards this operation, it would have to be done with the vertex shaders. I think the R300 is either too far along to support this in 'hardware' so to speak (ie, not wasting FPU units when you could have a dedicated unit doing these calculations), or they were part of the DX9 developement and had to support it. either way, it CAN do Displacement mapping, it's just a question of how it does it.
64 bit colour? 64 bit Z-Buffer? not likely, but we'll see.
FP rendering.. well lets see, considering you already have Vertex shader 2.0 support, you'd assume that..
256 bit DDR SDRAM? been rumored quite a bit, and is even included in the Parhelia (and I think the P10), so it's not totally impossible to think that R300 would be able to do this.
as for the RV250.. I won't comment. it's a long enough post already.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
