Announcement

Collapse
No announcement yet.

Parhelia - any bandwidth-saving features?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Parhelia - any bandwidth-saving features?

    once and for all can someone tell me that?

    any so-called occlusion - culling, deferred rendering, crossbar crap kind of techniques?

    i know fast z-clears, hardware displacement mapping and those tesselation, advanced depth whatever stuff are supported in hardware, but are these categorised under "bandwidth-saving"?

    thank you very much.
    The future's no use today.
    <a href="http://autarkic.org/geek.html">RIG*</a>

  • #2
    once and for all can someone tell me that?
    No, they can't tell you yet.
    Gigabyte P35-DS3L with a Q6600, 2GB Kingston HyperX (after *3* bad pairs of Crucial Ballistix 1066), Galaxy 8800GT 512MB, SB X-Fi, some drives, and a Dell 2005fpw. Running WinXP.

    Comment


    • #3
      It's all in your point of view.
      The features you listed are concidered by many to be bandwidth saving techniques.
      nVidiots and fanATIcs would disagree (untill it's available in their cards)
      Last edited by Kruzin; 19 June 2002, 23:04.
      Core2 Duo E7500 2.93, Asus P5Q Pro Turbo, 4gig 1066 DDR2, 1gig Asus ENGTS250, SB X-Fi Gamer ,WD Caviar Black 1tb, Plextor PX-880SA, Dual Samsung 2494s

      Comment


      • #4
        Isn´t 16xfaa a "kind" of deferred antialiasing algorithm, that saves alot of bandwith?
        I think that is the next-coolest bandwith saving tech i have heard of, tilebased rendering is still the coolest, but 16xfaa is a close second.
        This sig is a shameless atempt to make my post look bigger.

        Comment


        • #5
          The future's no use today.
          <a href="http://autarkic.org/geek.html">RIG*</a>

          Comment


          • #6
            I can tell you.

            "Once and for all"

            There, happy?
            Meet Jasmine.
            flickr.com/photos/pace3000

            Comment


            • #7
              funny thing is that i think it was anandtech that found that of the bandwidth saving features on the Radeon 8500, Fast Z-Clears was the one that made the largest difference, and the others were pretty minimal.

              the "crossbar" memory architecture that NVidia is always talking about is nothing new... the G400 had a similar memory controller iirc.

              the other thing is that it looks more like Matrox's core is designed to work more intelligently than others, eliminating extra work when possible. that in and of itself could be a bandwidth saving feature, of sorts...

              why is everyone so worried about having bandwidth saving features when it has like twice the bandwidth of a GF4 anyways...
              "And yet, after spending 20+ years trying to evolve the user interface into something better, what's the most powerful improvement Apple was able to make? They finally put a god damned shell back in." -jwz

              Comment


              • #8
                I think the reason is obvious: having twice the bandwidth may have diminishing returns *if* there isn't any sort of logic in place to try and preserve/save BW.

                In other words, one might ask the question: Is it better to save transistors and go with a wider bus architecture, or better to spend a considerable amount of R&D on the memory interface/architecture and use a less-wide bus? In the end, do things, more or less, cancel themselves out?

                I think we will finally see for ourselves tomorrow...Personally, I think the wider bus is more attractive, but it also has the side-effect of being a more expensive option as well...

                Comment


                • #9
                  Originally posted by Pace
                  I can tell you.

                  "Once and for all"

                  There, happy?
                  thanks for proving yourself. have a nice day.
                  The future's no use today.
                  <a href="http://autarkic.org/geek.html">RIG*</a>

                  Comment

                  Working...
                  X