4 ms·
Surely if they are both doing 60fps then by definition the performance will be the same? I guess the time spent doing the actual rendering vs waiting to do the
by jiggy2011 14y ago
Surely if they are both doing 60fps then by definition the performance will be the same? I guess the time spent doing the actual rendering vs waiting to do the next frame might be different, not sure if there is a reason that the characteristics would be different at 300FPS and 60FPS though since surely the only difference is how often the render code is called?
Bare in mind that Valve is running this test on a much higher end PC than most consumers are likely to have. People will want to be able to run these games on their $500 laptops , so the difference between 270 and 315 FPS might translate into a difference between 50FPS and 60FPS which would be noticeable.
- lmm 14y agoIf the code is "rendering" 300 FPS but only displaying 60, it could be doing anywhere from 1x to 5x as much work as if it were rendering at 60, depending on arbitrary driver internals. So it would be much more convincing if Valve had an example of "on this hardware, at these settings, it can sustain smooth 60fps under opengl and not under directx".
- geon 14y ago> the difference between 270 and 315 FPS might translate into a difference between 50FPS and 60FPS ...or it might not. Which is the problem. You can't just interpolate like that. Or can you? I have only heresay to go on.