[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Circle cut off at 60+fps, fixed by display.flip

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
From: Vincent Michel <vxgmichel@xxxxxxxxx>
Date: Thu, 12 Jun 2014 15:35:42 +0200
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Thu, 12 Jun 2014 09:35:45 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HOLyhlJOM10YA898+RMhMY96Uaoy/SbO37xlA079nL8=; b=TmDnpyj/wJlYrJE1+cVlaWbA45pPeqML1XaKutRTkhhXGJ1g37vpGl6aEPejwipf8H bSoG2Qa98CiDWQUqqM7RTkkyyq3IEFqELUyrfwgBItsPtZNY5OhjnfxSShzotz1ipkEE TbyYcEneUNjx/JTBN15qLfUzEcz9S70WEYXq9pr+xjMriK5DQIVFa2gieZLbNDR5OHqZ 9p/onYlmlKfFP4zc6Fnjpw0NGos75kUhQJn/+OyK3bYpDAK3sXcX60z9bRIgRhd3Rl2l mWjro1rXcF7Yvu0I0yJEWlYfvK42YWd72TeFPbkT4FJ4sPl7H1X+cNI1iftDmPQ46cPQ bu3A==
In-reply-to: <CAC5tdwOSukJqke88O8o670+=W2LkX3Xsz3QE+_iuCn6cCvvH1g@xxxxxxxxxxxxxx>
References: <b07c567c-348c-48c4-bd68-3b5af1d9efcd@xxxxxxxxxxxxxxxx> <53996D3F.1000605@xxxxxxxxxxxx> <CAGYJgdXy-O6pcBNw-VXH=tEE=8PS+1BMN3mNT+_Pm4LXKxXQ_Q@xxxxxxxxxxxxxx> <CAC5tdwNY-34WfvrPC7Zg6s34OzWzcrgkvRTBgO3Yf6HWocgodA@xxxxxxxxxxxxxx> <CAC5tdwOSukJqke88O8o670+=W2LkX3Xsz3QE+_iuCn6cCvvH1g@xxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx

I ran your code and clearly noticed the same problem.Â

Also displayed the dirty rectangles and there's nothing wrong here.

I tried with a Sprite/RenderUpdates approach so I can use the RenderUpdates.draw method and I observed the same result.

I also agree that pygame should handle this stuff internally. This behavior really surprises me.

I'll keep experimenting a bitÂ

2014-06-12 14:16 GMT+02:00 Abhas Bhattacharya <abhasbhattacharya2@xxxxxxxxx>:

Also, just to mention again, screen,flip magically solves the problem,
which made me think that it was a incorrect screen update issue. But
the code seems pretty simple and couldnt really find any screen update
bug.

References:
- [pygame] Circle cut off at 60+fps, fixed by display.flip
  - From: Abhas Bhattacharya
- Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
  - From: Radomir Dopieralski
- Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
  - From: Jesterea
- Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
  - From: Abhas Bhattacharya
- Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
  - From: Abhas Bhattacharya

Prev by Author: Re: [pygame] Potential Malware in Pygame 1.9.2a0.win32-py3.2
Next by Author: Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
Previous by thread: Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
Next by thread: Re: [pygame] Circle cut off at 60+fps, fixed by display.flip
Index(es):
- Author
- Thread