Re: [pygame] pygame.display.flip slow

To: pygame-users@xxxxxxxx

Subject: Re: [pygame] pygame.display.flip slow

From: Nuno Maltez <nuno.lists@xxxxxxxxx>

Date: Mon, 24 Feb 2020 18:31:35 +0000

Delivered-to: archiver@xxxxxxxx

Delivered-to: pygame-users-outgoing@xxxxxxxx

Delivered-to: pygame-users@xxxxxxxx

Delivery-date: Mon, 24 Feb 2020 13:31:51 -0500

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=u/qEa0zUMbQrMWvk0mNFjPUoRtJ89vZLkb44rKSXeto=; b=E7fDnk3NwNA4sbSZNllGXg3FLE008yx6Nf8Jm0cCbYgbVJMYiQxgV6GP43ENQjr6Mc gS18njEGYftEoFH+uB0HLd5ZRxL+Kn79PapqluA/e1Nvb8GpYNxZSBhiUtaIuSEw63RC 9lA80yHYwjZ7+MiuHNurVIrb9W91SSELtBVFakFdvCyuydxOMZiJJV878DxPc5BkiqxZ m7cDrlGTLc9/pgf/2/pHkXJ0xUDY2HtzqL6HV2rbb1hBaKjHC1GfRNygZPvdGF6XKvXd mJiv/1LuVOyRkcPoEgOc/XhUPYO4U2IMAriHnL7PVCkyIa4JY3r+ELuGqQg6aVIdPasy a9hA==

In-reply-to: <236b720d-5f13-bcb2-27b9-928e2d560fc5@canterbury.ac.nz>

References: <CAGZq8YNakts6Xw6o0i7Gszn07mZ47fBXGCXndAuYdkdao6kJRg@mail.gmail.com> <CAG4NV=uSf-8yiiFUy7OhO9ojdQN-8bo3FUJK=jw9gxocnCzzbg@mail.gmail.com> <CAGZq8YNVKFY0HVjHTnU5MUK3egv19aP3u62=xuvVf9hBQJcbLQ@mail.gmail.com> <236b720d-5f13-bcb2-27b9-928e2d560fc5@canterbury.ac.nz>

Reply-to: pygame-users@xxxxxxxx

Sender: owner-pygame-users@xxxxxxxx

Hi,

Thanks again for the answers.

Both machines are running Fedora Linux. Both are using X11 and the nvidia drivers, but the drivers are different versions (older graphics card in machine B).

I'll look at the settings to see if I can figure out the difference.

I'll try to find out

On Thu, Feb 20, 2020 at 10:30 PM Greg Ewing <greg.ewing@xxxxxxxxxxxxxxxx> wrote:

On 20/02/20 8:57 am, Nuno Maltez wrote:
> when I run my test program, Machine B reports FPS > 200, and
> pygame.display.flip taking 0.002 per call,
> while machine A reports FPS < 60, and pygame.display.flip taking 0.016
> per call.

This looks to me like machine A is synchronising its flips
with the monitor's refresh rate, but machine B is not. Why
that would be when you're creating the surface with the same
flags I don't know. Maybe a difference in the display
driver?

--
Greg