Hi ,
I have a problem trying to run Animator4 with vglrun.
It seems it doesn't work even I use vglrun.
When I run vglrun a4 it just like I use a4.
error messages:
=
QGLContext::makeCurrent(): Cannot make invalid context current.
With the help of nVidia, I was able to get to the bottom of what's going
on with WINE 1.3.11+. In fact, it has nothing to do with WINE. Any
application that attempts to call glXSwapIntervalSGI() with a Pbuffer
current will cause nVidia GLX to trip a BadWindow error. This has been
the case at
Hi Darrell,
This is the 2nd fairly recent issue I notice you tracked down to drivers
being very unhappy with specific modes set. I'm curious, how did you go
about figuring out which call was killing the driver? Is it
trial-and-error or you have a GL-driver-writer's mind and can make
It seems to be an issue with the ATI drivers. You can reproduce it
simply by running glxinfo without even getting VirtualGL involved. I've
reproduced it using the latest (v8.773) Catalyst drivers on RHEL 4 and
with several different types of remote X server and X proxy
configurations. It seems
On 3/24/11 3:45 PM, Nathan Kidd wrote:
From those messages it seems that a4 does some internal checks and
doesn't like it when VGL redirects and/or modifies certain GLX state.
You can run with +tr (VGL_TRACE) option to see if you can find out what
VGL was doing when a4 became unhappy. To
No, I'm not that smart. :) These have all been cases of someone
specifically leaving a particular mode set, experiencing readback
problems, and reporting it to me. This specific bug report is here:
http://sourceforge.net/tracker/?func=detailaid=3234376group_id=117509atid=678327
On 3/24/11
