[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[pygame] flip() and opengl
- To: pygame-users@xxxxxxxx
- Subject: [pygame] flip() and opengl
- From: David <dvkeeney@xxxxxxxxx>
- Date: Mon, 4 Sep 2006 21:23:19 -0400
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Mon, 04 Sep 2006 21:23:28 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=J8D9bD9J9yg2foR07k8PIloYJhym17KjSkMQqO8TPKX1f9WOV2S6HrFVmo138sXQBRoPwmjX+g+Cg50J/rNU/Jos418nXfoNf4PhKkizTSjYmAUYbndtBbSQe/MqcTgBIgJ8qOrO5i1uKcQwNVnERP8GPhpYH9quzLduogL2Ec8=
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
What does the flip() function do exactly, in OpenGL mode?
I have been doing some profiling of variations on a simple script, and the time taken by flip can vary from 0 (too small to measure) to 35 ms per call.
flip() must do more than just change a hardware register indicating which buffer to display. I assume there are finalizing operations to be done before toggling the buffers. Is there documentation somewhere on what exactly is being done?
Knowing what is taking the 35 ms would help in optimizing.
Thanks
David