From: Paul N. <Pau...@Su...> - 2006-10-25 21:15:04
|
Thanks Brian for your response. We put together a DMX config today and used the render_to_app_window as part of the dmx.conf, which solved point 1. However, we now have an issue where the app hangs for about 5 seconds and then works fine for about another 5 seconds, then hangs again, etc. It could be to do with using GbE, as we are waiting for Infiniband switches, etc. However, what doesn't seem to add up is that when running VMD over DMX (app on master, rendered on slave) and not Chromium, we get good performance, however, once you put Chromium into the mix, the performance issues outlined above occur. Any pointers as to how to best debug what is going on would be much appreciated. Kind regards, Paul. Brian Paul wrote: > Paul Needle wrote: >> Hi, >> When I try to run applications (VMD/OpenSceneGraph) through Chromium, >> I have a few issues I can't work through: >> 1. Chromium splits the mouse control of the application into a >> separate window, with the actual display window being shown full >> screen separately. > > The 'render_to_app_window' option can be used to tell Chromium to > render back into the original application window. > > >> 2. Even though I am using the 'fullscreen' option from the render spu >> and even though the actual display window is full screen, the actual >> images only show up on a quarter of the screen. > > The render SPU is just using whatever viewport parameters the > application gives it. So, the viewport size in the render SPU window > is probably equal to the app window's size. > > With the tilesort SPU you can scale up rendering to match the render > SPU's window size. > > >> 3. Chromium can't interpose on scripts as easily as binaries, you >> need to mess around with the LD_LIBRARY_PATH variable within the >> application script (this one is not so much of a problem, as we have >> found a workaround more or less for this). > > Yeah, the only alternative to hacking the shell script is to put all > the Chromium libs in a standard location (like /usr/local/lib/) and/or > setting up various symlinks. > > -Brian |