Results 1 to 25 of 161

Thread: AMD's Radeon HD 6870 benchmarked? (updated more screens)

Hybrid View

  1. #1
    Xtreme Addict
    Join Date
    Apr 2007
    Posts
    2,128
    Quote Originally Posted by Xoulz View Post


    Are you saying the resolution doesn't matter, when dealing with tessilation..?
    At least I am. Resolution (UNLESS IT CHANGES FIELD OF VIEW!) doesn't have ANYTHING to do with tesselation. The units which handle tesselation do not handle per-pixel operations, as far as I know, so there is no extra work for those units. The work remains the same regardless of the resolution.

    However, obviously even with tesselation, the resolution has impact on the framerate, because there is a limit how many operations the ROPs can do, and how many operations the TMUs can do. With bigger resolution they need to do more. And they also need a bigger share of the memory bandwidth, too.

  2. #2
    Xtreme Addict
    Join Date
    May 2009
    Location
    Switzerland
    Posts
    1,972
    Quote Originally Posted by Calmatory View Post
    At least I am. Resolution (UNLESS IT CHANGES FIELD OF VIEW!) doesn't have ANYTHING to do with tesselation. The units which handle tesselation do not handle per-pixel operations, as far as I know, so there is no extra work for those units. The work remains the same regardless of the resolution.

    However, obviously even with tesselation, the resolution has impact on the framerate, because there is a limit how many operations the ROPs can do, and how many operations the TMUs can do. With bigger resolution they need to do more. And they also need a bigger share of the memory bandwidth, too.
    offcourse it will, tesselation impact on the anti-aliasing and anistrope filtering....... indirect lightning, and reflect............... It was not the case when ATI have release the API cause driver was optimised for it, but as Microsoft have choose a diferent path in DX11............. it's impact it a lot.......... For make it simple, tesselation don't kill the framerate, but the addtion of the filters uppon the surface tesselated do it.......
    Last edited by Lanek; 08-29-2010 at 09:41 AM.
    CPU: - I7 4930K (EK Supremacy )
    GPU: - 2x AMD HD7970 flashed GHZ bios ( EK Acetal Nickel Waterblock H2o)
    Motherboard: Asus x79 Deluxe
    RAM: G-skill Ares C9 2133mhz 16GB
    Main Storage: Samsung 840EVO 500GB / 2x Crucial RealSSD C300 Raid0

  3. #3
    Banned
    Join Date
    Jun 2008
    Location
    Mi
    Posts
    1,063
    Quote Originally Posted by Calmatory View Post
    At least I am. Resolution (UNLESS IT CHANGES FIELD OF VIEW!) doesn't have ANYTHING to do with tesselation. The units which handle tesselation do not handle per-pixel operations, as far as I know, so there is no extra work for those units. The work remains the same regardless of the resolution.

    However, obviously even with tesselation, the resolution has impact on the framerate, because there is a limit how many operations the ROPs can do, and how many operations the TMUs can do. With bigger resolution they need to do more. And they also need a bigger share of the memory bandwidth, too.
    Per-pixel..? Bro, resolution is ratio. More is more... 1920 x 1200 is more than 1920 x 1080. Any benchmark will change it's fov to render @ said resolution, otherwise it would just stretch scenes & be dysfunctional as a benchmark.

    More to tessellate, more work to be done. Aren't you dismissing the obvious?

  4. #4
    Xtreme Cruncher
    Join Date
    May 2009
    Location
    Bloomfield
    Posts
    1,968
    Quote Originally Posted by Calmatory View Post
    At least I am. Resolution (UNLESS IT CHANGES FIELD OF VIEW!) doesn't have ANYTHING to do with tesselation. The units which handle tesselation do not handle per-pixel operations, as far as I know, so there is no extra work for those units. The work remains the same regardless of the resolution.
    are you familiar with a z-buffer? triangles directly affect rasterization and z-buffer performance. because of the way z-buffer algorithms are optimized(hierarchy, with quadtrees, coarse grained culling) tiny triangles hurt efficiency which tessellation creates.

    i am saying that the # of triangles and their properties are directly related to rendering speed.

  5. #5
    Xtreme X.I.P.
    Join Date
    Nov 2002
    Location
    Shipai
    Posts
    31,147
    Quote Originally Posted by Chumbucket843 View Post
    are you familiar with a z-buffer? triangles directly affect rasterization and z-buffer performance. because of the way z-buffer algorithms are optimized(hierarchy, with quadtrees, coarse grained culling) tiny triangles hurt efficiency which tessellation creates.

    i am saying that the # of triangles and their properties are directly related to rendering speed.
    why do you guys continue to discuss semantics though?
    the original point was that one score was 1920x1080 and the other 1920x1200 and that they were not comparable... to which i and others said, the difference in unigine between those two resolutions should be tiny and the scores would be somewhat comparable...

    and they are... somebody compared 1080 vs 1200 and the performance is almost the same...

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •