Results 1 to 25 of 236

Thread: HD5970 Microstuttering tests

Threaded View

  1. #11
    Xtreme Addict
    Join Date
    Aug 2005
    Location
    Germany
    Posts
    2,247
    Quote Originally Posted by rge View Post
    So basically what you are saying is if something is traveling at 500 miles per hour, but has yet to go one mile it is not really traveling at 500 miles per hour, and hence we should not talk about it in mph terms...think about it for a minute, you might get the analogy.

    1 second = 1000 microseconds. 30 fps = 1 frame every 33 microseconds.

    THERE is no difference in stating fps versus microseconds of frames, unless you actually think until you have reached one second you cant know the speed of that frame in fps.

    For example let me translate your numbers, 8 8 8 40 8 would be 125 fps, 125 fps, 125 fps, 25fps, 125 fps.

    You are confusing fps with some bizarre notion that unless you have waited full second you cant measure transient frames per second. For example you can measure over .25 seconds then multiply x 4.

    So if I get pulled over for a ticket for driveing 45 miles per hour in a 35, can I tell the police officer I havent driven a full mile yet, hence I was going to drive 10 miles under 35 for next 1/2 mile, therefore I was doing exactly 35?

    Or was this a joke?
    ehm, i don't get what you're trying to say with this post. in my opinion you basically said exactly the same thing as prava. the only thing i don't understand are the numbers for the said example: 125fps, 125fps, 125fps, 25fps, 125fps (the bolded part in the quote). this is wrong.

    to sum it up:
    fps stands for frames per second, but we're in in a dimension between fps.
    the example 8-8-8-40-8 stands for the time in ms between each rendered frame. in other words: 1st frame is displayed after 8ms, 2nd after 8ms, 3rd after 8ms, 4th after 40ms, 5th after 8ms. in total this means 5 frames per 72ms. we're still far away from frames per second at this point. but what's important about microstuttering is, that the total amount of frames isn't the crucial measurement, instead the time between each frame is important.

    or did i miss smth about this little discussion?

    btw: sry for my ninja editing. i always tend to hit the "post reply" button too quick
    Last edited by RaZz!; 01-21-2010 at 04:41 AM.
    1. Asus P5Q-E / Intel Core 2 Quad Q9550 @~3612 MHz (8,5x425) / 2x2GB OCZ Platinum XTC (PC2-8000U, CL5) / EVGA GeForce GTX 570 / Crucial M4 128GB, WD Caviar Blue 640GB, WD Caviar SE16 320GB, WD Caviar SE 160GB / be quiet! Dark Power Pro P7 550W / Thermaltake Tsunami VA3000BWA / LG L227WT / Teufel Concept E Magnum 5.1 // SysProfile


    2. Asus A8N-SLI / AMD Athlon 64 4000+ @~2640 MHz (12x220) / 1024 MB Corsair CMX TwinX 3200C2, 2.5-3-3-6 1T / Club3D GeForce 7800GT @463/1120 MHz / Crucial M4 64GB, Hitachi Deskstar 40GB / be quiet! Blackline P5 470W

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
  •