Alright, I've sort of had my mind blown. While its a simple concept, this article definately takes a look at framerate in a new way: Instead of FPS (framerate is life), it looks at the number of ms to render each frame. 16.7 ms = 60 fps... pretty safe ground. Until you see some frames needed 500 ms to be rendered.
This article also addresses the "micro-stutter" that is seen with multi-gpu configurations (SLI/Crossfire). Beware, however, it is quite long (thorough) but there are pretty graphs that really extrapolate it.
Suspicion active, was sprinting around no scoping everyone prior to demo then just ran around with pistol after I started, seems to be tracing through walls.
# 464 "Gannicus" [U:1:1847068838] 30:29 105 0 active
gannicus.dem
Hello Belcher, Hello Cannon,
thanks for your reply and I appreciate the effort. Strangely some weeks ago I could join the server and played on it but some days after access been blocked again, of course not using any vpn or other stuff. Really no idea what really happened.
My steam ID is 76561198037997651
Thanks for your reply, I appreciate you looked into it!
Kind regards Chris / Crucco
Question
Dillon 1st MRB
Alright, I've sort of had my mind blown. While its a simple concept, this article definately takes a look at framerate in a new way: Instead of FPS (framerate is life), it looks at the number of ms to render each frame. 16.7 ms = 60 fps... pretty safe ground. Until you see some frames needed 500 ms to be rendered.
This article also addresses the "micro-stutter" that is seen with multi-gpu configurations (SLI/Crossfire). Beware, however, it is quite long (thorough) but there are pretty graphs that really extrapolate it.
http://techreport.com/articles.x/21516
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.