Hi Sean, Can you send me your config and state files. I'll take a look.
-Nikhil On Mon, Jul 9, 2012 at 11:19 AM, Sean Delaney <[email protected]> wrote: > Thanks Nikhil. > > I should have mentioned that I have set the VRplugin to load automatically > both for the server and client (and checked that it is marked as "loaded" > in the manager). My apologies for not mentioning that in the last message. > > The figures I used in the pvx file describing the corners of the screen > (in the coordinates / units of the tracking system) are not correct, I just > used them for testing. I was still expecting to see some change on the > display when I move the tracking target (even if it's not the "correct" > change). I can recalibrate the system to rule this out, but I suspect that > this will not solve the problem. > > Perhaps I can use a network monitoring tool to see if Paraview is actually > connecting to the tracking server. > > Seán > > > > > On Mon, Jul 9, 2012 at 3:14 PM, Nikhil Shetty > <[email protected]>wrote: > >> Sean, >> >> On Mon, Jul 9, 2012 at 9:04 AM, Sean Delaney <[email protected]> wrote: >> >>> Hi Nikhil and Stephan, >>> >>> Outstanding response time, thanks! As you say, my first mistake is not >>> using a CAVE client-server setup. >>> >>> I have set up a CAVE display with the short pvx file below, (borrowed >>> from the CAVE example). I run the server with >>> pvserver /path/to/config.pvx >>> I don't use MPI because I only have 1 screen and hence 1 process. I >>> launch the client (by ssh from another machine) with >>> paraview --stereo --stereo-type="Crystal Eyes" --server="hubble1" >>> --state=/path/to/1.pvsm >>> where "hubble1" is the local hostname, and also the PVserver name. >>> >>> Result: A "cave" type window is launched in fullscreen mode on the main >>> display showing a stereo image. The standard Paraview client is available >>> on the remote machine (via X forwarding). I can manipulate the session with >>> the mouse on the remote machine. Moving the tracking targets has no effect >>> on the main display. >>> >>> Perhaps I should save the state from the CAVE session and append the >>> VRPN settings to that one instead? >>> >>> Make sure that the VRPlugin is loaded at startup. The appended VRPN >> setting in *.pvsm are read by the plugin. When the plugin is not loaded >> then the configuration is simply ignored. >> >> Thanks, >>> >>> Seán >>> >>> >>> ------------------------------ config.pvx ------------------------ >>> <?xml version="1.0" ?> >>> <pvx> >>> <Process Type="client" /> >>> <Process Type="server"> >>> <EyeSeparation Value="0.065"/> >>> <Machine name="hubble1" >>> Environment="DISPLAY=:0" >>> LowerLeft="-1.0 -1.0 -1.0" >>> LowerRight="1.0 -1.0 -1.0" >>> UpperRight="1.0 1.0 -1.0"> >>> </Machine> >>> </Process> >>> </pvx> >>> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/mailman/listinfo/paraview >> >> >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
