# Not fixed at 60fps for glfw apps

**URL:** <https://discourse.glfw.org/t/not-fixed-at-60fps-for-glfw-apps/237>\
**Category:** support\
**Created:** [April 16, 2012, 8:11am UTC](https://discourse.glfw.org/t/not-fixed-at-60fps-for-glfw-apps/237 "2012-04-16T08:11:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [April 16, 2012, 8:11am UTC](https://discourse.glfw.org/t/not-fixed-at-60fps-for-glfw-apps/237/1 "2012-04-16T08:11:34Z")

</div>

**anonymous** wrote on [Monday, April 16, 2012](https://sourceforge.net/p/glfw/discussion/247562/thread/8bab3b88/#5a6e):

I would like not to fix my game integrating with glfw to 60 fps or any values  
automatically set in glfw.

How can I do that ?

and

What’s the default time interval (in ms or secs) for swap buffer to be  
processed (or content drew on screen)?

To be more elaborate on this, please see my situation below.  
In glut, I implemented my own timing system which hooks up call to  
update/render function if the time is right, so I can restrict fps for my game  
say 30fps, or non-fixed at all. In addition, I’ve experimented with glfw and  
found that glfw already restricted or targeted fps at 60 automatically (but  
not sure whether it’s always at 60 fps or not) so I have to set my timing  
system to non-fixed timestep to allow glfw to cap it outside of my system. If  
I set my timing system to be fixed timestep then the app will be double slow  
in time because it’s capped by glfw and my own timing system.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [April 16, 2012, 9:24am UTC](https://discourse.glfw.org/t/not-fixed-at-60fps-for-glfw-apps/237/2 "2012-04-16T09:24:45Z")

</div>

**anonymous** wrote on [Monday, April 16, 2012](https://sourceforge.net/p/glfw/discussion/247562/thread/8bab3b88/#e729):

(may not relavant here)  
In addition, I have tested with glfwSwapInterval(0) and enabled fixed-mode  
in my timing system. Things go as expect, I can restrict it to says 30 fps or  
60 fps. But the smooth is only on window mode. When I go into fullscreen mode,  
I saw tear of polygon and non-sync, and jittering. I guess it’s because I set  
glfwSwapInterval(0) so no v-sync.

So additional question (sorry for popping up a new question inside my own  
again, but I think it relates and should be in continuing) -\> **How can I  
prevent those tear / unsync / jittering but allowing the software or hardware  
to as fast as possible render its content with glfwSwapInterval(0) ?**

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [April 16, 2012, 12:01pm UTC](https://discourse.glfw.org/t/not-fixed-at-60fps-for-glfw-apps/237/3 "2012-04-16T12:01:35Z")

</div>

**[elmindreda](https://sourceforge.net/u/elmindreda/)** wrote on [Monday, April 16, 2012](https://sourceforge.net/p/glfw/discussion/247562/thread/8bab3b88/#b003):

You cannot both disable vsync and avoid tearing. Synchronising to the  
display’s refresh rate is what allows tear-free output.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [April 16, 2012, 1:04pm UTC](https://discourse.glfw.org/t/not-fixed-at-60fps-for-glfw-apps/237/4 "2012-04-16T13:04:19Z")

</div>

**anonymous** wrote on [Monday, April 16, 2012](https://sourceforge.net/p/glfw/discussion/247562/thread/8bab3b88/#4720):

@elmindreda, thanks for your reply. I finally found out that the (too much)  
tearing / unsynced / jittering are affected from my own timing system. After  
fixed it, result is nice both in window and full screen. It works as expected  
now. GLFW just works fine.

Thanks !