From: Christopher D. Johnson (cubicwts++at++excite.com)
Date: 10/06/2005 09:56:14
Jason-
I took out the calls to capture the x-events on the lower screen (those actually caused the app to crash) and my initialization actually proceeds until I try to create my scene. Once I have my terrain loaded there is a call
"pfdCombineLayers((pfNode *)pTerrain);"
that I make and then the program craps out on me again with the error:
"X Error of failed request: GLXBadDrawable
Major opcode of failed request: 145 (GLX)
Minor opcode of failed request: 11 (X_GLXSwapBuffers)
Serial number of failed request: 41
Current serial number in output stream: 162"
Seems I'm still getting bit by some GLX anomolies.
Christopher D. Johnson
AV-8B Harrier II Simulators
ISEO Support Team
Cherry Point, NC
252-466-4542
252-466-4538
--- On Thu 10/06, Jason Daly < jdaly++at++ist.ucf.edu > wrote:
From: Jason Daly [mailto: jdaly++at++ist.ucf.edu]
To: jdaly++at++ist.ucf.edu
Cc: cubicwts++at++excite.com, info-performer++at++sgi.com
Date: Thu, 06 Oct 2005 12:08:07 -0400
Subject: Re: [info-performer] Multipipe Initialization
Jason Daly wrote:<br><br>> Christopher D. Johnson wrote:<br>><br>>> here are the results I get running glxinfo:<br>>> <br>>><br>><br>> Hmm, I'm a little confused now. According to the NVIDIA driver <br>> documentation, the second screen in a two-screen setup from one card <br>> is not supposed to support GLX, yet clearly glxinfo says that you have <br>> full support on both screens.<br><br><br>OK, I'm less confused now. Turns out that I misread the README. You <br>can in fact have hardware OpenGL on both screens. It just can't span <br>both screens as it can in TwinView.<br><br><br>-- <br><br>--"J"<br><br>"I'm a castaway stranded in a desolate land,<br> I can see the footprints in the virtual sand."<br> --Neil Peart<br><br>
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
This archive was generated by hypermail 2b29 : Thu Oct 06 2005 - 09:56:29 PDT