Hi Sean,
On Mon, Jul 23, 2012 at 11:29 AM, Sean Delaney sdela...@cp.dias.ie wrote:
Dear Nikhil,
Success! I believe I have the configuration right. Now I just need to add
a wand.
Awesome. Let me know if you run into trouble.
By the way, I may have found a bug / feature. It seems like I
Hi Sean,
By the way, I may have found a bug / feature. It seems like I have to
specify the eye separation value in mm, even though I have transformed my
tracker units to metres in the state file. Perhaps this is another mistake
in my configuration though. Please let me know if that's the
Hi Aashish,
Thanks for your comments. To my knowledge, there is no reason why the eye
separation must be specified in the same units as the raw tracking data.
Paraview never uses my tracking data in its raw state. The tracking data is
transformed to my chosen world coordinates before it is used
Hi Sean,
On Tue, Jul 24, 2012 at 10:39 AM, Sean Delaney sdela...@cp.dias.ie wrote:
Hi Aashish,
Thanks for your comments. To my knowledge, there is no reason why the eye
separation must be specified in the same units as the raw tracking data.
Lets suppose they are not in the same units, in
Hi Aashish,
In my case, my tracker data is in mm but my chosen world coordinates are in
meters, so I transformed the tracking data to meters and I expect the eye
separation to be defined in meters too.
It is. If you transform your tracker data, then you would have to
adjust your eye
On Tue, Jul 24, 2012 at 12:03 PM, Sean Delaney sdela...@cp.dias.ie wrote:
Hi Aashish,
In my case, my tracker data is in mm but my chosen world coordinates are
in meters, so I transformed the tracking data to meters and I expect the
eye separation to be defined in meters too.
It is. If you
Thanks Aashish, it would be good to know if I have made an error with my
configuration. It's certainly not a major issue, the workaround is trivial
to implement.
Thanks a lot for your help,
Seán
On Tue, Jul 24, 2012 at 6:50 PM, Aashish Chaudhary
aashish.chaudh...@kitware.com wrote:
On Tue,
Dear Nikhil,
Success! I believe I have the configuration right. Now I just need to add a
wand.
By the way, I may have found a bug / feature. It seems like I have to
specify the eye separation value in mm, even though I have transformed my
tracker units to metres in the state file. Perhaps this
Hi Nikhil,
I have made the appropriate transformation to my tracking data, as you
suggested. The display is now responding to the motion of the tracking
targets. However, it is not responding to the rotation of the targets. I
believe this might be happening because the tracking server is showing
Hi Sean,
If you are using the same config file that you sent me then
VRConnectionManager
VRPNConnection name=iotracker address=iotracker@192.168.20.9
Tracker id=1 name=head/
/VRPNConnection
/VRConnectionManager
VRInteractorStyles
Style class=vtkVRStyleTracking
Hi Nikhil,
I have fixed the networking issues. There was an error in my state file and
I had also made an embarrassing mistake with the build. It works now and
the display moves when I move the tracking target. I recalibrated the
tracking system and measured the coordinates of the screen corners
HI Sean,
On Wed, Jul 11, 2012 at 9:55 AM, Sean Delaney sdela...@cp.dias.ie wrote:
Hi Nikhil,
I have fixed the networking issues. There was an error in my state file
and I had also made an embarrassing mistake with the build. It works now
and the display moves when I move the tracking
Thanks Nikhil. I guess I'll troubleshoot the connection first and then
worry about the number of sensors. It's possible that Paraview is just
dropping the connection due to an incorrect number of sensors though, or
some other issue with the data received. I'll report back with any findings.
Hi,
I'm trying to use paraview's VRPN functionality for head tracking. I've
compiled Paraview 3.14.1 on linux (64) and I have one stereo screen. I'm
using a Windows tracking server with IOTracker hardware / software.
What works:
Stereoscopic rendering (I use the cube source as a test).
Hello Seán,
1. When you use PV under Windows with head tracking, you should use always
VRPN.
2. Head tracking only works with a pvserver environment. Therefore you have
to define a Server configuration file with proper display parameters (read
more
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
Sean,
On Mon, Jul 9, 2012 at 9:04 AM, Sean Delaney sdela...@cp.dias.ie 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
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
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 sdela...@cp.dias.ie wrote:
Thanks Nikhil.
I should have mentioned that I have set the VRplugin to load automatically
both for the server and client (and checked
19 matches
Mail list logo
