Hello! I recently started making a little game using Pyglet. I noticed that when I'm using a scheduled update interval of 1/60.0, everything feels slightly choppy even though the frame rate stays at maximum all the time (60 fps). When I use schedule() instead of schedule_interval (), however, everything is really smooth even though the frame rate appears to be the same.
My thinking is this: the frame rate is ultimately limited by the refresh rate my monitor is set at (at least as long as vsync is on). When I schedule updates at a rate close to the refresh rate, I seem to somehow "miss" possible screen updates. What's worse, this happens at an uneven rate so it makes the movement look choppy. But the frame rate counter shows no indication of this. Is my theory correct? For now I solved the problem by setting the update interval slightly higher than my refresh rate. But I'm still not quite sure that I'm on the right track. Especially as some of the examples I saw (eg. Astraea) use an update interval of 60hz, which also happens to be the most commonly refresh rate nowadays. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
