I found that in game development, most people set a timer which triggered every 16ms and do the render things. As an Android programmer, I'm familiar with the Choreographer. You set a callback which will do the drawing staff, and each time vsync happens, the callback is called.

I know the origin use of vsync is to prevent modifying the buffer when the front buffer and the back buffer is switching. But don't you think making the drawing/render code has the same period with the actual screen refresh rate (in an ideal situation) is better?

So is there any reason why people don't prefer the vsync callback or vsync event based design?

Edit: One reason I can come up with is that if a monitor is 75Hz, it will be too frequency to do the render, right?

I found that in game development, most people set a timer that gets triggered every 16ms to do the rendering. 

As an Android programmer, I'm familiar with the Choreographer. You set a callback that will do the drawing stuff, and each time vsync happens, the callback is called.

I know the original use of vsync is to prevent modifying the buffer when the front buffer and the back buffer are being switched. But don't you think making the drawing/render code have the same period as the actual screen refresh rate (in an ideal situation) is better?

So is there any reason why people don't prefer the vsync callback or vsync event based design?

One reason I can come up with is that if a monitor is 75Hz, it will be too high-frequency to do the rendering, right?

I found that in game development, most people set a timer which triggered every 16ms and do the render things. As an Android programmer, I'm familiar with the Choreographer. You set a callback which will do the drawing staff, and each time vsync happens, the callback is called.

I know the origin use of vsync is to prevent modifying the buffer when the front buffer and the back buffer is switching. But don't you think making the drawing/render code has the same period with the actual screen refresh rate (in an ideal situation) is better?

So is there any reason why people don't prefer the vsync callback or vsync event based design?

I found that in game development, most people set a timer which triggered every 16ms and do the render things. As an Android programmer, I'm familiar with the Choreographer. You set a callback which will do the drawing staff, and each time vsync happens, the callback is called.

I know the origin use of vsync is to prevent modifying the buffer when the front buffer and the back buffer is switching. But don't you think making the drawing/render code has the same period with the actual screen refresh rate (in an ideal situation) is better?

So is there any reason why people don't prefer the vsync callback or vsync event based design?

Edit: One reason I can come up with is that if a monitor is 75Hz, it will be too frequency to do the render, right?