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 performance.
I have been running several Windows applications using wine and VirtualGL
(Games and other graphic applications) with decent success
On 11-02-24 10:32 AM, calvin.mor...@comcast.net 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
performance.
I have been running several Windows applications using wine and
VirtualGL
On 11-02-24 12:15 PM, calvin.mor...@comcast.net wrote:
xscope 1.3 reports to have beginning support for GLX, so I've attempted
to use that. This is my first time using xscope, so hopefully it is correct.
I've attached both the VGL Trace output as well as the xscope output in
GZip format.
On 11-02-24 01:24 PM, Nathan Kidd wrote:
VGL doesn't hook
any vendor private calls, so ...
Correction: VGL doesn't appear to hook this vendor private function.
--
Free Software Download: Index, Search Analyze Logs
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(),
I ran xscope on the rendering server using xscope -i13 -o0 -d:0.0 and then
connected from my PC to the server (using vglconnect) and then ran the app
using vglrun -c rgb -d :13.0 wine program
If it would be helpful for me to do this differently let me know. I wasn't sure
where to place xscope
