Hi Ricardo, On Mon, Nov 7, 2011 at 11:43 AM, Ricardo Reis <[email protected]> wrote:
> On Mon, 7 Nov 2011, Nikhil Shetty wrote: > > Hi Ricardo, >> >> Which version of paraview are you using? >> > > 3.12.0 RC3-50 > > You may want to revert to an older version (3.10) to be able to use the space-navigator. > taken from git > > I have also the spacenav open-source driver and daemon in my system. > > I have tried both ways, ie, > > - with spacenav daemon running and starting the vrpn server > > - with spacenav daemon off and starting the vrpn server > > To make spacenav work with vrpn you need to uncoment the following line in vrpn.cfg (comes with VRPN src) vrpn_3DConnexion_Navigator device0 then start the server # vrpn_server -f /path/to/vrpn.cfg to test if the device is working run the following command provided by vrpn # vrpn_print_device device0@localhost This should print out values from VRPN device. none works. The spacenav source brings a simple example program that works. > It's just a openGL cube that you manipulate with the SpaceNavigator. Maybe > the plugin should work with this instead of vrpn? Just suggesting. > The reason we went with VRPN is because we were building a general VR framework and needed the capability to support different devices (wiimotes, gamepads, kinects etc). Developing a VRPN client plugin seemed like the quickest way to do that and also our clients use VRPN so it was sort of our way forward. But what you say makes a lot of sense but we are sorted of limited by funding and the clients immediate requirements to be able to support that. As a matter of fact the SpaceNavigator support in PV was a community contributed patch to the original VRPN plugin. You are more than welcomed to contribute native drivers support if you so wish to. I would be glad to provide assistance in this endeavor if you choose to take it up. > > Anyway I will be grateful for any input, this device was bought with > paraview in mind. > > As a side note, there have been quiet a lot of changes to the VRPN plugin (its now called VRPlugin). We have a better framework to support multiple VR devices (even tracked) from various VRPN/VRUI server sources and better configuration mechanism to deal with these devices. However we haven't yet ported and tested the space-navigator into this new framework. Its work in progress and I will be sending out an email once we are ready with a few more things (like documentation) in place. Regards Nikhil > best > > > > Ricardo Reis > > 'Non Serviam' > > PhD candidate @ Lasef > Computational Fluid Dynamics, High Performance Computing, Turbulence > http://www.lasef.ist.utl.pt > > Cultural Instigator @ Rádio Zero > http://www.radiozero.pt > > http://www.flickr.com/photos/**rreis/<http://www.flickr.com/photos/rreis/> > > contacts: gtalk: [email protected] skype: kyriusan >
_______________________________________________ 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
