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
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 --
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).
Jon TURNEY wrote:
Since [1], glxgears turns at a constant 70 degrees per second.
---
70 degress/s? How is that important?
glxSwapBuffers does not block when used with indirect rendering, which means
that lots of frames can be rendered almost instantly, with no apparent
rotation, since the
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
