Good Afternoon,
My mistake, i3 is a window manager (I get them mixed up from time to time :) ); LightDM is the display manager. Here is (to my knowledge) the layout of the environments: [image: VGL_Env.png] - Cases 1, 2, 4, and 5 do not work well when used with an i3 desktop (but well for MATE, KDE, etc.). - Cases 1 and 2 with i3 requires XFree86 to be disabled - Cases 4 and 5 with i3 requires the VGL_USEXSHM=0 to be used - Cases 1, 2, and 3 requires the VGL_FORCEALPHA=1 to be used - Case 4 seemed to work better than Case 5 in performance (increasing the compression core count helped, but was still slower) - Case 6 works when running vglrun in a terminal, but not when launching the desktop environment with "vglrun +wm" (audio is lost) (Understandably, cases 3 and 6 are not supported like TurboVNC is, but I included them for completeness sake) In no case is the scope going wider than CAN (while there is potential for WAN, we are focusing currently on the LAN-CAN performance). In all, I am slowly, but surely understanding how Xorg, GLX and SSH all tie together. That being said, I appreciate your time helping us out with all of this. Thanks, 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/3174c035-7240-4a74-9b15-860f770f39f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
