Schedules still result in inconsistency.
On Sep 9, 10:32 am, "Drew Smathers" <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 9, 2008 at 1:27 AM, 3TATUK <[EMAIL PROTECTED]> wrote:
> > ...
> > At this point it's kind of pre-mature optimization because pyglet has
> > serious FPS issues as it is.
> > ( seehttp://code.google.com/p/pyglet/issues/detail?id=341)
>
> Pyglet does not have serious FPS issues. set_fps_limit() is
> deprecated. If you want an almost constant FPS, write your own event
> loop with blocking clock ticks. Otherwise, schedule your animations
> and be happy.
>
> -Drew
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
