Good Afternoon,
I ran a few more tests to apply these principles. To start (and only as
a test), I ran SSH using the '-Y' option so see if there was any
appreciable performance difference; it was marginal, but noticeable. The
issue of disabling XFree86 applies to the cases where I was testing a few
WINE applications. As before, I believe that several of these errors was a
matter of the client Window Manager being i3, where it was missing some
packages or other functionality necessary for rendering an application from
the X-Forwarded SSH session. With cases 1, 2, 4 and 5: we are not directly
running a window manager; we are only running individual applications. Only
in cases 3 and 6 is there a window manager being started. In those cases,
we have had issues propagating the vglrun functionality to the commands run
within the session (i.e. using "vglrun mate-session" or the like in FastX
to use VirtualGL for the window manager and all programs running within
it). This could just be a case of mixing 2D and 3D X servers and/or
misusing the command, given that it is all running on the same server. The
good news is, I gave the jpeg-compression method another shot and received
better results (perhaps a good day for the server?). It runs very well, and
with the addition of the -fps <num> option, I can stabilize the rendering
so that it is more in sync with the X inputs (mice, keyboards, etc.). And
always, thanks for the clarifications.
Best Regards,
Jason
--
You received this message because you are subscribed to the Google Groups
"VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/virtualgl-users/cc4ca35c-71d1-4f86-ae99-8093beb153d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
