This is not really answering the question, but I sometimes set vsync on, and set the update to 1/61 instead of 1/60. This works smoothly for the most part, since it's always capped by the vsync.
On Thursday, October 27, 2016 at 4:19:47 AM UTC+9, Baitshop wrote: > > I was wondering if a fixed timestep is possible with pyglet's current > event loop? When using schedule_interval for 1/60.0 it's not always > consistent since it is using a variable time step. > > How is one supposed to separate the rendering from the updates considering > adjusting the position of the sprite will move it next time it is drawn. I > am also having trouble understanding how interpolation would be configured > using the pyglet app system as the on_draw does not get passed any dt. I > have tried an older implementation that I found, but it seems like it fires > the scheduled function faster than the dt actually is. Would anyone happen > to have a proper example of how a fixed time step would work using a sprite > and pyglet? > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
