public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-xfree@cygwin.com
Subject: Re: problem with opengl (glxgears) running on cygwin ....
Date: Thu, 27 Mar 2014 06:28:00 -0000	[thread overview]
Message-ID: <5333C52C.1040602@users.sourceforge.net> (raw)
In-Reply-To: <53318D38.5050409@dronecode.org.uk>

On 2014-03-25 09:05, Jon TURNEY wrote:
> On 20/03/2014 08:41, Linda Walsh wrote:
>> When I try to run glxgears locally, it displays the initial gears,
>> but now they are just frozen.  It doesn't work remotely, either,
>> which was what I tried initially.  It *used* to work -- remotely
>> at 20-30 frames/second (as measured by fraps).
>>
>> Interestingly enough, I get a glx window, -- fraps will display
>> 30 (the right number for my screen refresh rate), in the right corner
>> of the glxgears window... but the gears don't move.
>
> Thanks for pointing out this issue.
>
> I think that currently glxgears doesn't work very well with the combination of
> indirect rendering and vsync-limited buffer swapping, so you are getting 30
> fps, but they aren't useful frames.

This should be fixed in mesa-demos-8.1.0-2.


Yaakov
Cygwin/X


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  parent reply	other threads:[~2014-03-27  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20  8:41 Linda Walsh
2014-03-25 14:05 ` Jon TURNEY
2014-03-25 15:59   ` Linda Walsh
2014-03-27  6:28   ` Yaakov (Cygwin/X) [this message]
2014-03-27  7:33     ` remote desktop /session bus woes...(was Re: problem with opengl (glxgears) running on cygwin ....) Linda Walsh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5333C52C.1040602@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).