r420 may beat nv40 in doom3 with anti-aliasing

Discussion in 'Architecture and Products' started by LokeshRay, May 10, 2004.

  1. digitalwanderer

    digitalwanderer Dangerously Mirthful
    Legend

    Joined:
    Feb 19, 2002
    Messages:
    18,987
    Likes Received:
    3,529
    Location:
    Winfield, IN USA
    See Baron? THAT'S why they don't ban him. ;)
     
  2. Tim Murray

    Tim Murray the Windom Earle of mobile SOCs
    Veteran

    Joined:
    May 25, 2003
    Messages:
    3,278
    Likes Received:
    66
    Location:
    Mountain View, CA
    sigh, so true...

    Beyond3D Drinking Game: Every time Radar says something stupid, take a shot. If you can get through a single thread without your liver exploding, you win.
     
  3. TheAlSpark

    TheAlSpark Moderator
    Moderator Legend

    Joined:
    Feb 29, 2004
    Messages:
    22,146
    Likes Received:
    8,533
    Location:
    ಠ_ಠ
  4. radar1200gs

    Regular

    Joined:
    Nov 30, 2002
    Messages:
    900
    Likes Received:
    0
    R3xx/R4xx do not do everything at FP24 precision or else they would have no need of mini-ALU's that aren't FP24 capable.
     
  5. nelg

    Veteran

    Joined:
    Jan 26, 2003
    Messages:
    1,557
    Likes Received:
    42
    Location:
    Toronto
    Seriously, are you just making this stuff up to keep the conversation going?
     
  6. FUDie

    Regular

    Joined:
    Sep 25, 2002
    Messages:
    581
    Likes Received:
    34
    The mini-ALUs are FP24 capable. You must be thinking of NVIDIA's parts.

    -FUDie
     
  7. Ostsol

    Veteran

    Joined:
    Nov 19, 2002
    Messages:
    1,765
    Likes Received:
    0
    Location:
    Edmonton, Alberta, Canada
    "Mini" refers the the instruction set that those ALUs support.
     
  8. digitalwanderer

    digitalwanderer Dangerously Mirthful
    Legend

    Joined:
    Feb 19, 2002
    Messages:
    18,987
    Likes Received:
    3,529
    Location:
    Winfield, IN USA
    :shock:












    :shock:








    [​IMG]

    You've got to be just putting us on now, right? [​IMG]
     
  9. KimB

    Legend

    Joined:
    May 28, 2002
    Messages:
    12,928
    Likes Received:
    230
    Location:
    Seattle, WA
    Basically the only thing that's done at FP32 in the R3xx's pixel shader is fixed-function texture addressing.
     
  10. Deathlike2

    Regular

    Joined:
    Aug 17, 2003
    Messages:
    542
    Likes Received:
    5
    Last I recall, ATI has stated in interviews that all precision in the pixel shader is handled internally at FP32.. the output that results from it is FP24.

    I presume it is a difference between the storage and the internal calculations.
     
  11. Deathlike2

    Regular

    Joined:
    Aug 17, 2003
    Messages:
    542
    Likes Received:
    5
    Last I checked, NVidia ENDORSES the use of FP16 AND PS 1.4.

    I also recall, ATI processes _PP too... which still runs better than NVidia's hardware (in the case of R3XX vs NV3X).

    Of course, there's absolutely no correleration with this statement:

    Who wanted _PP? NVidia
    Which IHV with DX9 hardware doesn't support _PP? noone that anyone knows of
    Whose hardware runs terrible w/o _PP? NVidia (at least with the NV3X hardware)
    Which company's DX9 app (NOT BENCHMARK) hasn't used _PP? none that I know of

    Flawed arguments with erroneus statements don't make what one says true.
     
  12. KimB

    Legend

    Joined:
    May 28, 2002
    Messages:
    12,928
    Likes Received:
    230
    Location:
    Seattle, WA
    You've got it backwards. The input/output formats supported in the R3xx go up to FP32. The internal pixel shader math is all done at FP24. Even if the actual units had more precision than that, they're still storing at FP24 in the registers after each operation, which would destroy the point of having higher precision math in the first place.
     
  13. radar1200gs

    Regular

    Joined:
    Nov 30, 2002
    Messages:
    900
    Likes Received:
    0
    Okay, I got the FP24 bit wrong for the mini-ALU's. For that I apologise.

    What I'd like to know is are the Mini-ALU's more suited to working PS1.x instructions or SM2.0 instructions?

    Once again I'll point out that nVidia also did this with NV30, NV31, NV34 but when DX9 changed to full/partial precision from multi-precision they altered their mini-ALU's to reflect that. Unfortunately the change happened late enough that the above gpu's couldn't be modified in time (production chain already in motion) and first appeared in NV35. This more than anything else probably explains why NV30 was aborted from an architectural standpoint (not to say there weren't other reasons also, not related to architecture).
     
  14. Dave Baumann

    Dave Baumann Gamerscore Wh...
    Moderator Legend

    Joined:
    Jan 29, 2002
    Messages:
    14,090
    Likes Received:
    694
    Location:
    O Canada!
    The best I can get from ATI is that they contain more than just PS1.4 modifiers. If they do contain other instructions then these can be scheduled to assist the full ALU for any other operation that requires those instructions.

    DX9 was always floating point precision - there was no change. It is an implemantation detail how they support legacy integer shaders - IHV's had the option to support integer shaders with separate units or float units with conversion. NVIDIA gambled with NV30 that DX8 would still be the main requirement and so they kept a similar structure to NV25 with NV30 for the integer processing but extending the texture address processor (which is already float in NV2x) to support DX9 float operations. Id's say their issues stemmed from NV30's lateness and some blindsiding of ATI's architecture whereby ATI decided to make everything float which offered comparable, or better, DX8 performance and very good DX9 performance.
     
  15. KimB

    Legend

    Joined:
    May 28, 2002
    Messages:
    12,928
    Likes Received:
    230
    Location:
    Seattle, WA
    From what I've read about the NV40, perhaps the largest problem with the NV3x is that the compiler is the last thing they developed. This basically allowed the hardware team to make a lot of decisions that made life extremely hard on the compiler writers. This is why nVidia's drivers are tailor-made to specific shaders in games, and why the general compiler has been so slow to improve with the NV3x.

    Of course, there's also the fact that there just wasn't much floating point performance to be had in the NV30-34 to begin with. This really should be the most surprising thing, if you think about it. Why would nVidia want to shoot themselves in the foot by automatically halving (or more) PS 2.x performance over PS 1.x performance? I can only conclude that early in development, nVidia planned on integer precision being allowed in PS 2.x.
     
  16. Albuquerque

    Albuquerque Red-headed step child
    Veteran

    Joined:
    Jun 17, 2004
    Messages:
    4,309
    Likes Received:
    1,103
    Location:
    35.1415,-90.056
    I'm just happy that the NV40 parts are back "up to par" with the competition. Yeah, there's a bigger feature set without argument, but the performance in current situations is what's very nice.

    For the past 18-24 months, the only NV hardware I've been able to wholeheartedly recommend were the NV25 series for great budget cards and the 5900NU series for good performance at a cheap price. Every other price/performance point was better covered by ATI, which was quite sad because it made the whole market lopsided.

    This round is very obviously different in my eye; enough so that I am strongly considering ditching my X800XTPE and looking for a 6800U (although the prices are still a little insane on the NV40 right now).
     
  17. cthellis42

    cthellis42 Hoopy Frood
    Legend

    Joined:
    Jun 15, 2003
    Messages:
    5,890
    Likes Received:
    33
    Location:
    Out of my gourd
    I don't drink and I think my liver STILL exploded! :shock: Is that a bad sign?
     
  18. KimB

    Legend

    Joined:
    May 28, 2002
    Messages:
    12,928
    Likes Received:
    230
    Location:
    Seattle, WA
    Exploding liver is always a bad sign.
     
  19. SirkoZ

    Newcomer

    Joined:
    Jun 20, 2004
    Messages:
    29
    Likes Received:
    0
    By integer precision you mean FX12 (48-bit)? Because that's what John Carmack was requesting for Doom 3. And NVIDIA usually listenes to him as they have the best OpenGL impementation in gaming cards. If I remember correctly the request for 48-bit color came as soon as in GF256/GF2 days... I think NVIDIA thought if FX12 is good enough for Carmack, it would be for Microsoft too, but time went on, they had a fight over XBox grf. chip pricing, Doom3 was nowhere to be found and NV3x was the one, that ended up Doomed... :(
     
  20. FUDie

    Regular

    Joined:
    Sep 25, 2002
    Messages:
    581
    Likes Received:
    34
    I don't think your argument makes sense. For one, Carmack wanted higher precision backbuffers and FX12 only applies to the shaders. Second, I believe he was talking about 64-bit (FX16 per component) surfaces. NVIDIA's FX12 shaders were a byproduct of carrying over legacy shader stuff from the GF4.

    -FUDie
     
Loading...

Share This Page

  • About Us

    Beyond3D has been around for over a decade and prides itself on being the best place on the web for in-depth, technically-driven discussion and analysis of 3D graphics hardware. If you love pixels and transistors, you've come to the right place!

    Beyond3D is proudly published by GPU Tools Ltd.
Loading...