At the moment, I was wanting to launch compiz in "the normal way"; i.e., on ubuntu, I right-clicked on the desktop, enabled the fancy stuff, then went into the comiz control panel and checked / configured the features I wanted.
In playing around some more with this, I found some interesting problems. Apparently my thin clients, which have the Intel 945 graphics onboard, are capable of some 3d rendering. If I have the nvidia binary drivers installed on my server, and configure my account so that on the server's console, all works well, then log into the client, everything is reversed and upside down. Disabling compiz, I log in and see that glxinfo actually works and claims nvidia acceleration, etc. According to the people from #compiz on freenode, the inverted issue I saw is a consequence of rendering on intel while using the nvidia GLX module (as opposed to the standard X one). I've also found that in order to enable compiz as above, I must have the nvidia binary drivers installed. I'm not sure how VirtualGL will interplay with all this...In theory, everything is being rendered on the host. As to the launching methodologies...I was really wanting something more transparent than trying to teach all my users that they need to use vglrun in front of any app that uses 3d...Although we probably don't use that many 3d apps, so if I can catch compiz in whatever magic script that is starting it, that might catch 90% of the 3d stuff. I don't know if there's other apps that "can benefit from 3d" but don't ordinarily use it... I'm also not yet sure that VirtualGL + compiz is a useful/usable/worthwhile combination (i.e., how much network load and complexity does it add for its features; does it work well enough to make it worth the trouble, etc). At this point, I guess I'm going through a proof of concept test and evaluation. Thanks! --Jim On Thu, Nov 12, 2009 at 2:29 PM, DRC <[email protected]> wrote: > Jim Kusznir wrote: >> Users on thin clients will log in and have a full 3d-capable desktop >> including compiz. I intended to use vgl transport to the x server >> running on the thin client. >> >> My attempts so far seem to be very confusing, as I was originally >> under the impression that VirtualGL can just be "set up", and then >> everything runs through it. After digging in deeper, it appears that >> vgrun needs to be used for running all applications...Is that >> accurate? Is there a way to set it up so its transparent to people; >> that it "just works"? > > vglrun is the preferred method, yes. VirtualGL only intercepts the > functions it needs and passes everything else unimpeded to the OpenGL > library. Otherwise, we'd have to maintain our own OpenGL library (like > Chromium does) and stay on top of every OpenGL extension, etc. Doing so > would be a compatibility minefield. > > You could try explicitly setting LD_PRELOAD=librrfaker.so to cause > VirtualGL to be preloaded into all applications. I don't guarantee the > stability of this configuration, though. > > Can you provide more details about how you're trying to launch compiz? > Maybe I can offer an alternative suggestion if I get a better > understanding of the problem. > > >> As a second, more minor use case, I'd like to make it "just work" for >> users logging in via nomachine's NX. I'm not sure how well it will >> perform, though, as the proxy probably isn't really set up for that >> kind of frame rate and such. >> (I did try to use vgrun on glxgears through NX, but did not see any >> performance improvement over no 3d). > > Use /opt/VirtualGL/bin/glxspheres as a benchmark, and run it with no > frame spoiling (vglrun -sp /opt/VirtualGL/bin/glxspheres). GLXgears is > a very poor benchmark for remote 3D. The geometry and image size are so > small that the frame rate has no correlation to the performance of a > real-world app. > > You are correct that NX isn't set up for the kind of frame rate that > VirtualGL can deliver. The most I've been able to get out of it is > about 9-10 Megapixels/sec, on a LAN under ideal conditions. That's > about 1/3 the performance of the VGL Transport or TurboVNC. > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > VirtualGL-Users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtualgl-users > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ VirtualGL-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/virtualgl-users
