Other places stable fast FPS in even busy clubs, where earlier versions of Firestorm crawled down to annoying extreme low FPS.
#Life framer full#
While we're here though.hey isn't this a great problem to have? 😄ĭoes it default to 60 FPS, if VSynch rate of monitor not recognized? My 2K 165 Hz monitor works correct regarding VSynch with other programs, but Firestorm craps it to 60 FPS, if I use Preferences->Rendering->Limit Framerate to 120 FPS.Īs you, I have two monitors connected, the other one older full HD 120 Hz, which add to the complexity of bug hunt.Įlse thanks to you and all the people working on the Firestorm update, it fast, reliable, responsive compared to earlier versions and without the above Limit Framerate, I get crazy wild high FPS at home with high/ultra graphics, ALM on. My advice, at least until someone slaps me sensible with clear proof that I am wrong, is to turn off VSync, if you want to limit the fps then use the old fashioned fps limiter and let the viewer have micro sleeps it is (at this stage) more predictable.īTW, This whole set of scenaros is further muddied by adaptive sync technologies such as NVidia's G-Sync and AMD's Free-Sync the sleep on one fram allowing a faster frame next time, leading to all kinds of weird stutter potential. The chances are that it would not be quite so black and white either.
#Life framer driver#
This means I have 20ms per frame.Ĭase 1: higher FPS - If I draw my screen in 15ms (~67 fps) then what happens is that the card waits for 5ms for the frame to start over and then swaps the buffers, forcing the 20ms frame time and giving me the 50FPS updates.Ĭase 2: lower FPS - If I draw my screen in 25ms (40fps) then what happens? Based on the OpenGL documentation, the GPU will ask the driver to wait until the next vsync event (known as a vblank) This means that you are now waiting two whole frames, giving you 25fps! The questions I have about this are as follows and are based on my understanding of the openGL documentation :-ġ) If I have two monitors, one running at 144Hz and one running at 60Hz does it correctly detect the one that I am running on? What if I am (presumably because I just like being awkward) straddling the two monitors?Ģ) What happens when I am slower than the cap? Let's assume (for the sake of my brain near midnight) that my monitor is running at 50Hz.
The underlying implementation uses an opengl extension "wglSwapIntervalEXT" which is set to 1 for "vsync on" and 0 for "vsync off", in the properties it is exposed as a simple toggle.
The main problem I have with it is a lack of clarity over what it achieves. It's a default that we inherited (having VSync enabled) and I am not entirely sure I agree with it.
0 kommentar(er)
