Ampere K. Hardraade wrote:
The GLXUnsupportedPrivateRequest error was caught. I have raised the issue a few times over the past six months, but there aren't much response.
Yes that is true, but typically in open-source projects, when you see non-action or non-response from the developers it means that no one knows the answer or no one is in a position to be able to fix the problem. It doesn't mean no one cares.
I'm sitting here and FlightGear works fine on all the machines I have access to (windows and linux.) We aren't like a major corporation where someplace we have a large set of various development machines and hardware at our disposal for developers to use for testing. We *depend* on distributed bug catching and fixing. Our test platforms are spread around the world in user's homes and work places. In this case we seem to have found a bug that so far has only affected non-developers. That stinks, but what are you going to do. I've long ago given up on trying to understand the entire body of FlightGear code, so there are many chunks of it that are way beyond me ... including the rendertexture, 3d clouds, and shadow stuff ... and that seems to be where this problem is. Hopefully one of the other developers that knows something about this area of code can work with you.
I still remember when the problem started occuring: after Harald made an update to his initial 3D Clouds code. I never saw 3D Clouds under XFree after that, and running FlightGear under 24bit depth in Xorg would get me the GLXUnsupportedPrivateRequest error.
Let's continue to push for a solution to this. Perhaps you can keep bugging Harald and Erik or whoever else it is that knows something about this code and if we can find a solution soon, I am happy to roll out a v0.9.10 or v0.9.9a that addresses this issue.
I'm not happy that we have a bug that crashes FG for some people on some hardware, but understand that this is a really tough one if none of our 'coding' developers are seeing it on their own hardware. We need as much support and encouragment and system information from you 'end users' as possible. I realize that isn't a great answer and I'm sure this is more frustrating for you than me. But let's stay patient, keep this positive, and spend our energy working together towards a solution. (And realize that not every developer can spend time on FG every night ...)
Curt. -- Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
