public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: cygwin-xfree@cygwin.com, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: remote desktop /session bus woes...(was Re: problem with opengl (glxgears) running on cygwin ....)
Date: Thu, 27 Mar 2014 07:33:00 -0000	[thread overview]
Message-ID: <5333D453.2060409@tlinx.org> (raw)
In-Reply-To: <5333C52C.1040602@users.sourceforge.net>

Yaakov (Cygwin/X) wrote:
> 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.
----
FWIW, I tried another X server...VcXsrv?...
Same with that program.

I tried several, got some that worked, most didn't.

Of the few that worked 'well' remotely, they were variations
on the glgears... got about 400-500 FPS -- and about low 300's MB/s
in bandwidth consumed... that sounds about right... but I think
there are other problem in trying to get a remote desktop to work
now... everything wants to connect to the session bus -- and many progs
won't start if they can't.  So if I can't figure out a way to
get that to work, remote usage is left at a fairly primitive level
despite the high frame rates on a 3"x4" window... ;-)


One of the demo progs said it required opengl 2.1 .. my card has V4.something.
well above 2.1, so that seems like another latent problem.

Will look for the fixed version ...

thanks for the news...

--
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/


      reply	other threads:[~2014-03-27  7:33 UTC|newest]

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

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=5333D453.2060409@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin-xfree@cygwin.com \
    --cc=cygwin@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).