I can't reproduce the failure with WINE 1.3.13. Can you give more
specific information-- what graphics hardware you are using, the
specific driver version, what O/S, etc.?
After looking at the WINE source, the only scenario I can come up with
is that it's trying to use glXBindTexImageATI(), which WINE seems to
want to use when emulating wglBindTexImageARB(). However, that code has
been in there forever, not just since 1.3.11.
Can you provide a simple Windows 3D app that demonstrates the issue?
Maybe it only occurs when using D3D, not OpenGL?
On 2/24/11 9:32 AM, calvin.morrow@... wrote:
> Hello List,
> I'm finding that VirtualGL has been working well with most graphics
> applications I've tried under Linux, and even with pretty decent
> I have been running several Windows applications using wine and
> VirtualGL (Games and other graphic applications) with decent success
> (usually the same as running on a native workstation). However, all
> versions of Wine newer than 1.3.10 (which includes 1.3.11 - 1.3.14) have
> started crashing with the following error:
> X Error of failed request: BadWindow (invalid Window parameter)
> Major opcode of failed request: 136 (GLX)
> Minor opcode of failed request: 16 (X_GLXVendorPrivate)
> Resource id in failed request: 0x1c00007
> Serial number of failed request: 0
> Current serial number in output stream: 99
> Obviously some new code in Wine introduced during the 1.3.11 cycle isn't
> playing well with VirtualGL. Any ideas?