Vuzix Forums / VR920 / Tracking

VR920 AND FLIGHT SIMULATOR

rigardie — Tue, 22 Dec 2009 12:11:53 GMT

i want to buy a VR290 to use it with Flight simulators 2004 and FSX as a tracking and 3d Device is that possible
thanks

Vuzix and FSX "set zero"

lightpanther — Sun, 17 Jan 2010 02:12:17 GMT

Ok, after copious experimentation I have finally managed to get this apparatus to function, sort of, on a laptop of mine and I can get the head tracking in FSX. Two significant problems remain

1) No matter where I "set zero" (which doesn't seem to me to make any difference, actually) whenever the cockpit view opens in FSX I am facing directly the back of the cockpit when I am facing my computer straight on. In other words, it is totally 180 degrees reversed. Any idea why? I can get a forward view by rotating my chair 180 degrees, but then for cable reasons and the fact that the keyboard is behind me, that isn't much use. Again, I did all the callibration with temples open and facing the computer screen, moving through all axes. The result is consistent...it ALWAYS shows up exactly 180 reversed when the cockpit view appears ???

*As an important aside, let me say that this 180 degree reversal problem is *NOT* solved by simply turning the Vuzix 180 degrees and doing the calibration like that. Also sometimes it's not 180, but it always seems to be facing somewhere between straight out the right cockpit window round to the very back wall of the cockpit.

2) The viewing frame "freezes" often and holds for two or three second before going back into motion again.

Much more accurate mouselooking script (Two of Carl's combined with an important added in part

Feilen — Thu, 17 Dec 2009 19:14:56 GMT

One problem I've noticed with the improved mouselook and general mouselook scripts Carl gave out is that general gaming lacks one thing: recentering. If your pitch goes out of line, the GlovePIE can't recognize it since it doesn't get feedback from the game. This is a major problem. Whenever you respawn, look around too fast, something moves, something moves you, or something moves where you're looking, your yaw goes out of line, a MAJOR problem that makes it much less realistic. The TRACKIR emulation part of the script allowed for recentering at user level, but anything else requires the mouse to change anything, with varying results.

However, I've found one excellent feedback mechanism: No game lets you look down more than, well, DOWN. Same for looking up.This script moves the mouse as far as it can down and up when the VR920's actual pitch is down or up.

[b]Use is simple: Calibrate VR920 accelerometer (for crouch detection, no jump), run script, and look all the way up or all the way down. This will line up your pitch, do this every time you respawn, pitch gets misaligned, etc etc[/b]

Okay, also, finding that the magnorth thing doesn't really work.

I did add something new that's useful though. Previously trying to find out sensitivity values was just guess and check, but I found a way to do it.
To use the new feature, face a definate object(something like the edge of a pole, something vertically the same and definate), align your crosshair to that part, and press Ctrl+Shift+[.

Next, turn the VR920 clockwise until your crosshair again lines up with the exact same spot (if your sensitivity at that time is off, it won't be the same direction). Press Ctrl+Shift+].

The last value of the debug (bar on top) will be something like 948 per degree. That's a rounded to a whole number value for that game at whatever ingame settings you have. To add this make a new entrie in the sensitivity list with the window title as whatever the game is and the sensitivity as that value. Have fun!
[hr]
[i]pie.FrameRate = 60Hz

var.crouch = true //if you want crouching

if window.Handle <> var.OldHandle then
var.OldHandle = window.Handle
var.sensitivity = 900
var.s = window.title
var.smoothing = 2
if var.s = "kk" then
var.sensitivity = 450
Say "K Krieger"
else if var.s = "DOOM 3" then
var.sensitivity = 4600
Say "Doom 3, lowest sensitivity"
else if var.s = "Harry Potter and the Chamber of Secrets" then
var.sensitivity = 1500
Say "Harry Potter 2"
else if var.s="Tomb Raider: Anniversary Demo" or var.s="Tomb Raider: Anniversary" then
var.sensitivity = 1270
Say "Tomb Raider Anniversary, sensitivity 10"
else if var.s="Second Life" then
var.sensitivity = 900
Say "Second Life"
else if var.s="F.E.A.R." or var.s="F.E.A.R. Perseus Mandate Demo" then
var.sensitivity = 300
Say "Fear, default sensitivity"
else if var.s="RoboBlitz" then
var.sensitivity = 600
Say "Robo Blitz, default sensitivity"
else if var.s="Left 4 Dead"
var.sensitivity = 1200
Say "Left For Dead"
else if var.s="Portal"
var.sensitivity = 1200
Say "Portal"
else if var.s="Unreal Tournament 3"
var.sensitivity = 600
Say "Yoo Tee Three"
else if var.s="Synergy"
var.sensitivity = 1225
var.smoothing = 4
Say "Half Life Too, Sinergie Mod"
else if var.s="Reminder" then
var.OldHandle = 0 // RoboBlitz demo changes window title
else
//debugprint(var.s)
endif
end if

if (not mouse.CursorVisible) and (not FakeTrackIR.active) then
var.yaw = RemoveUnits(Smooth((VR920.ContinuousYaw), 2))/90*var.Sensitivity
var.pitch = RemoveUnits(VR920.Pitch)/90*var.Sensitivity
var.mx+=delta(var.yaw)
var.my-=delta(var.pitch)
if vr920.pitch <= -83 then fakemouse.directinputY = -2*var.sensitivity
if vr920.pitch >= 83 then fakemouse.directinputY = 2*var.sensitivity
fakemouse.DirectInputX = var.mx
fakemouse.DirectInputY = var.my
if var.crouch = true then
//begin crouchcode
//Make sure the VR920 accelerometer is calibrated.
//Stand up quickly or it will be detected wrong.
var.gs = |[vr920.gx,vr920.gy,vr920.gz]|
var.moving = smooth(abs(var.gs-1),2)>0.04
var.MoveUp = false
var.MoveDown = false
var.Crouching = false
var.Standing = false
var.Jumping = false
if (abs(smooth(vr920.RelAccY,16))>2.3) and var.moving but not var.samemove then
var.updown = true
if var.dir = 0 then
var.dir = sign(smooth(vr920.relaccy))
end if
end if
if released(var.moving) then
var.deltapitch = vr920.StrictPitch-var.oldpitch
if var.updown then
if abs(var.deltapitch) < 15 degrees then
if var.dir = 1 then
var.MoveUp = true
end if
if var.dir = -1 then
var.MoveDown = true
end if
var.samemove = true
end if
end if
var.updown = false
var.dir = 0
end if

if (not var.moving) and (var.samemove) then
wait 800ms
var.samemove=false
end if

if not var.moving then
var.oldpitch = vr920.strictpitch
end if
if var.MoveDown then
if not var.Crouched then var.Crouching = true
var.Crouched = true
end if
if var.MoveUp then
var.Standing = true
var.Crouched = false
end if
end if

if var.crouched = true
key.ctrl = true;
else if var.Standing = true
key.ctrl = false;
endif
else if FakeTrackIR.active then
var.Yaw = vr920.yaw - var.offset
if var.yaw <-180 then var.yaw+=360
if var.yaw >180 then var.yaw-=360
var.Yaw = smooth(var.Yaw,5)

var.LeanHeight = 1
var.NeckHeight = 0.3
var.EyeDist = 0.1
FakeTrackIR.x = sin(vr920.roll)*var.LeanHeight+sin(vr920.yaw)*var.EyeDist
FakeTrackIR.y = (cos(vr920.roll)-1)*var.LeanHeight/2+(cos(vr920.pitch)-1)*var.NeckHeight
FakeTrackIR.z = -sin(vr920.pitch)*var.NeckHeight+(cos(vr920.yaw)-1)*var.EyeDist

var.YawScale = 1
var.PitchScale = 1
var.RollScale = 1
var.PitchOffset = 0
if FakeTrackIR.ProfileID=332DH then
var.PitchOffset = 20 degrees
else if FakeTrackIR.ProfileID=3A35H or FakeTrackIR.ProfileID=3A38H or FakeTrackIR.ProfileID=3A39H then
// Arvoch Conflict, Evochron Alliance, and Evochron Renegade
var.YawScale = 2
var.PitchScale = 2
var.RollScale = 10
FakeTrackIR.z += -EnsureMapRange(vr920.pitch,-30 degrees,-10 degrees,-1m,0)
FakeTrackIR.y += EnsureMapRange(vr920.pitch,-30 degrees,-10 degrees,-1m,0)
FakeTrackIR.x += FakeTrackIR.z*EnsureMapRange(sin(var.yaw),-sin(20 degrees),sin(20 degrees),-1m,1m)
end if

FakeTrackIR.yaw = var.Yaw*var.YawScale
FakeTrackIR.pitch = vr920.Pitch*var.PitchScale +var.PitchOffset
FakeTrackIR.roll = -vr920.Roll*var.RollScale

// Uncomment the next line to enable voice command:
//if said('recenter') or Ctrl+R then var.offset = vr920.yaw

// status display
end if[/i]
[hr]

Also, an added bonus, a L4D Wiimote script designed to work very well with this.

Press Home and +/- to switch mode, button 2 to voicechat, and swing up to jump.
While Survivor swing wiimote sideways to punch back infected.
While hunter hold A and punch forward to pounce.
While boomer press B to boom.
While smoker fire to grapple.
While tank press B to throw rocks, punch forward with Wiimote to punch.

[hr]
[i]pie.Framerate = 60Hz

//General
WASD = Wiimote.Dpad //Movement
if Wiimote.RelAccY > 20 then Key.Space = true else key.space = false //Jump
Key.C = Wiimote.Two //Voice chat
var.controlsetmax = 4

//Control switcher. Click Home to press flashlight, Press and press +/- to switch modes
if Wiimote.Home then
if (not Wiimote.Plus) and (not Wiimote.Minus) then
Key.F = true
Key.F = false
wait 250 ms //press F
else if var.controlset <=var.controlsetmax and Wiimote.Plus = true then
var.controlset++
var.say = true
wait 250 ms
else if var.controlset > var.controlsetmax and Wiimote.Plus = true then
var.controlset = 0 //loop to start
else if var.controlset >=0 and Wiimote.Minus = true then
var.controlset--
var.say = true
wait 250 ms
else if var.controlset < 0 and Wiimote.Minus = true then
var.controlset = var.controlsetmax //loop to end
endif
endif

//Control sets start

/*--------Human---------*/
if var.controlset = 0 then
Wiimote.led1 = true
Wiimote.led2 = true
Wiimote.led3 = true
Wiimote.led4 = true
if var.say = true then say("Survivor")
var.say = false

if Wiimote.RelAccX > 15 then RMB = true else RMB = false //push back infected
LMB = Wiimote.B //Fire
Key.E = Wiimote.A //Use
Key.R = Wiimote.one //Reload
if (not Wiimote.Home) and Wiimote.Plus then Mouse.Wheelup = true //up one weapon
if (not Wiimote.Home) and Wiimote.Minus then Mouse.Wheeldown = true //down one weapon
//Rumble effects
if Wiimote.B = true or Wiimote.RelAccX > 15 then
wiimote.Rumble = true
wait 100 ms
wiimote.rumble = false
endif

/*------------Hunter-------------*/
else if var.controlset = 1 then
Wiimote.Led1 = true
Wiimote.Led2 = false
Wiimote.Led3 = false
Wiimote.Led4 = false //set LEDs
if var.say = true then say("Hunter")
var.say = false

if Wiimote.RelAccZ > 15 and Wiimote.A = true then LMB = true else LMB = false
RMB = Wiimote.B

//rumble
if (Wiimote.RelAccZ > 15 and Wiimote.A = true)
Wiimote.Rumble = true
wait 250 ms
Wiimote.Rumble = false
else if Wiimote.B = true then
Wiimote.Rumble = true
wait 250 ms
Wiimote.Rumble = false
wait 500 ms
endif

/*------------Boomer------------*/
else if var.controlset = 2 then
Wiimote.Led1 = false
Wiimote.Led2 = true
Wiimote.Led3 = false
Wiimote.Led4 = false
if var.say = true then say("Boomer")
var.say = false

if Wiimote.RelAccX > 15 then RMB = true else RMB = false
LMB = Wiimote.B
//rumble
if Wiimote.B then
Wiimote.Rumble = true
wait 2000 ms
Wiimote.Rumble = false
else if Wiimote.RelAccX > 15
Wiimote.Rumble = true
wait 250 ms
Wiimote.Rumble = false
endif

/*--------------Smoker-------------*/
else if var.controlset = 3 then
Wiimote.Led1 = false
Wiimote.Led2 = false
Wiimote.Led3 = true
Wiimote.Led4 = false
if var.say = true then say("Smoker")
var.say = false

LMB = Wiimote.B
if Wiimote.RelAccX > 15 then RMB = true else RMB = false
if Wiimote.B = true then
Wiimote.Rumble = true
wait 500 ms
Wiimote.Rumble = false
else if Wiimote.RelAccX > 15 then
Wiimote.Rumble = true
wait 250 ms
Wiimote.Rumble = false
endif

/*------------Tank------------*/
else if var.controlset = 4 then
Wiimote.Led1 = false
Wiimote.Led2 = false
Wiimote.Led3 = false
Wiimote.Led4 = true
if var.say = true then say("Tank")
var.say = false

if wiimote.RelAccZ > 20 then LMB = true else LMB = false
RMB = Wiimote.B
if wiimote.RelAccZ > 20 then
Wiimote.Rumble = true
wait 300 ms
Wiimote.Rumble = false
else if Wiimote.B = true then
Wiimote.Rumble = true
wait 80 ms
Wiimote.Rumble = false
endif

endif

debug = "X: " + Wiimote.RelAccX + " Y: " + Wiimote.RelAccY + " Z: " + Wiimote.RelAccZ[/i]
[hr]

[b][center]-----------------------------------------------Problems with glovepie?-----------------------------------------------[/center][/b]

[url=http://forums.vr920.com/Topic4663-8-1.aspx]Better calibration method[/url]
[url=http://forums.vr920.com/Topic983-8-2.aspx]GlovePIE 0.3 not working? Fix here[/url]
[url=http://flightpad.net/files/GlovePIE030.zip]Download GlovePIE 0.30[/url]
[url=http://www.iz3d.com/driver]3d game drivers, if you need them- 30 day trial[/url]

JUST LEAVING THIS HERE

Feilen — Sun, 20 Dec 2009 22:39:02 GMT

The yaw drifts when you look up for one simple reason. The earth is round. Magnetic north is not directly north of you, it's north and DOWN.
For a long time I've been trying to figure out something to accomodate this, and I MAY have something that can do it. Not promising anything, but if you want this in your things just to mess with it, go ahead...

[hr]
[i]
//DO NOT ZERO OUT THE VR920!!!
//The VR defaults to perfect calibration relative to the earth for yaw, and directly away from magnetic north for pitch.

var.angle = -26.5 /*Angle between you and the magnetic pole. This is if you were facing that direction exactly, looking forward, how far down it would be. I crudely got it from google maps.*/

/*I set 45 for how much it should change because it seemed to be correct. Mess with this if it's wrong, it could be a sensitivity thing.*/
debug = Vr920.yaw+(sin(vr920.pitch+var.angle)*sin(abs(vr920.yaw))*45) + ", " + vr920.pitch
[/i]
[hr]

If you wanna use continuousyaw for the tracking, don't change it in the equation. In fact, minus the first VR920.yaw in the line would make it an offset.
*EDIT* - IT WORKS! I did something wrong though. Here's the right equation
var.yawoffset = (sin(vr920.pitch-var.angle)*sin(vr920.yaw)*45)
Add that to the yaw for perfect tracking. However, it goes insane ABOVE the offset degrees.

*EDITEDIT* Fixed insaneness. Has some trouble around poles but works excellent otherwise.

Going to put up a script for everyone soon.

*EDITEDITEDIT*

Integrated the code into the improved crouch/mouselooking script I already put up. Enjoy! [url]http://forums.vr920.com/Topic4679-8-1.aspx[/url]

calibration problem,

BrandonStore — Sat, 19 Dec 2009 00:36:18 GMT

Hi, I can't seem to calibrate it right. I press calibrate, and I turn it left and right, then up and down, and then I roll it left and right. And when I get into Flight Simulator, its completely messed up. And I find the yaw and roll to get filled up while I am "pitching" it up and down, and pitch goes up when I make it go left and right. Is their a how-to video? Am I missing something? The instructions just say, twist it in the directions as illustrated. Thats what I have been trying to do :/

Driver supported camera-based headtracking?

WebDext — Wed, 23 Sep 2009 17:08:31 GMT

Hey Devs....

I wanted to ask why head tracking cannot be supported in the same fashion as the custom S3D drivers?
It looks to me like your current method causes the game to load up your custom d3d9.dll from the project
folder since LoadLibrary looks there first, then that dynamically links to the real d3d9.dll and wraps
all the API calls. Most calls probably just pass right through to the correct DLL, but you can selectively
grab information on the way in and back out as needed. And perform fancy end-of-frame code in the Present call.

So I'm guessing you guys just tack on transform matrices to change the fov, and offset to the left and right,
calling the real present inbetween and then notifying the HMD that the specified frame is being drawn. If that's
the case, it seems like you could just tack on the rotation ( and translation would be nice to
have access to through the API so we could add on support for Wiimote positional tracking, just leave it as the identity
matrix for now )

I'm sure it's way more complex than this because you have to deal with different present call orders, some may even be
ahead of time to render to cubemaps etc... and you have to skip those... But pretend that doesn't need to be handled
and this is sortof how I'd see it working:

[code]
// Pseudo VR920 wrapped version of IDirect3DDevice9::Present
HRESULT IDirect3DDevice9::Present( CONST RECT * pSourceRect
, CONST RECT * pDestRect
, HWND hDestWindowOverride
, CONST RGNDATA * pDirtyRegion )
{
HRESULT hr;
D3DXMATRIX mViewOld;
pD3D->GetTransform( D3DTS_VIEW, &mViewOld );

D3DXMATRIX mViewNew1, mViewNew2;
D3DXMatrixMultiply( &mViewNew1, &mViewOld, g_mHMDRotate ); // Rotate the world to view by global HMD rotation matrix
D3DXMatrixMultiply( &mViewNew2, &mViewNew1, g_mHMDTrans ); // Offset the world to view by global HMD translation matrix

D3DXMATRIX mLeft, mRight, mTrans;
D3DXMatrixMultiply( &mLeft, &mViewNew2, D3DXMatrixTranslation( &mTrans, -g_fIPD, 0.f, 0.f ) ); // mLeft = mViewOld * Left Eye Translation Matrix
D3DXMatrixMultiply( &mRight, &mViewNew2, D3DXMatrixTranslation( &mTrans, g_fIPD, 0.f, 0.f ) ); // mRight = mViewOld * Right Eye Translation Matrix

// Render the left eye
hr = g_pD3D->SetTransform( D3DTS_VIEW, &mLeft );
if( !SUCCEEDED( hr ) ) return hr;
hr = g_pD3D->Present( pSourceRect, pDestRect, hDestWindowOverride, pDirtyRegion );
if( !SUCCEEDED( hr ) ) return hr;

// Notify device and block
IWRSTEREO_WaitForAck( g_StereoHandle, LEFT_EYE );

// Render the right eye
hr = g_pD3D->SetTransform( D3DTS_VIEW, &mRight );
if( !SUCCEEDED( hr ) ) return hr;
hr = g_pD3D->Present( pSourceRect, pDestRect, hDestWindowOverride, pDirtyRegion );
if( !SUCCEEDED( hr ) ) return hr;

// Notify device and block
IWRSTEREO_WaitForAck( g_StereoHandle, RIGHT_EYE );

return hr;
}
[/code]

Any chance something like this could be supported in the future?
I think this kind of an implementation would be far superior and standard than say how WoW is currently handled by just offsetting the follow-camera angle with some Lua code. If I'm floating behind my character I want to be able to look around from THAT point, in all directions.

Thanks for taking the time to read this!

Jack

Crysis Warhead Tracking?

BrandonStore — Fri, 18 Dec 2009 09:12:17 GMT

Hi, I can't figure out how to get Head Tracking and 3D to work on Crysis Warhead. I am running the 64bit version, and followed the instructions exactly. I press F7 and F8 nothing happens. I am also running on Windows 7 incase that has something to do with it. Also, how does the Head Tracking for Crysis work when it is working? If I look up, will the camera scroll up and the gun position stay the same? Or does the gun move with the camera?

MSFS and head tracking question

bgaviator — Mon, 23 Nov 2009 02:32:31 GMT

I'm curious as to what most of you do as far as the VR-920 and head tracking when MSFS is concerned? I know the VR-920 is limited to just 3 axis of movement.....therefor, do most people opt for just using the 920s for the display and 3D, and then still use Track IR for the head tracking? Or is it better to set up a combination of the VR's tracking, and Track IR's tracking? I mean, ideally wouldn't it be best to let the VR-920 control the left/right, up/down, roll axis, but then have the Track IR controlling being able to zoom in and out with the head? Is this possible? Can't using something like Glovepie achieve this combination setup?

How do I use it in Second Life?

CarlKenner — Sat, 17 Nov 2007 08:54:53 GMT

I have only one program on the supported list, and that is Second Life.

But I can't get Second Life to work with the VR920.

How do I make it work?

Ctrl+B does nothing.

yaw problem

blkout — Mon, 05 Oct 2009 00:55:45 GMT

hey guys, i really hope somebody can help me with his.

I am a commercial helicopter pilot and also a flight simulator enthusiast, when i ran into the vr920 i made some budget for it and bought the goggles

i got it a couple days ago and i have been really impressed with the addition to positional awareness have given me during simulated flight. video is great, pc runs great, graphics are excellent... but the only problem i have noticed so far is the following...

after several times of calibrating the vr920 i see the same issues in both the calibration tool and glovepie when running the test script; and that is: [b]when i pitch up, the yaw slides to the right 20-25 degrees; and when i pitch down, yaw slides left 10-15 degrees...[/b]

it keeps doing that no matter what i do, sometimes more, sometimes less...

am i not calibrating this properly??? what i do to calibrate is roll 360, pitch 360 and yaw 360. slowly and steadily... am i missing anything???

thnx.

NEAR PERFECT yaw tracking, howto

Feilen — Fri, 11 Dec 2009 22:12:57 GMT

I've messed with the VR tracking enough, and never could quite get it perfect, or even close. Yaw drifts with pitch, since the earth's magnetic north is actually at an angle down from you, not just around.
However, I was trying to create a glovepie script to accomodate this, but I just happened to stumble upon this gem. Not sure if it will work for everyone, but here goes:

1.Open the calibrator, hold VR920 in air in front of you.

2.Spin Vr920 ALL the way around all three axis, several times, slowly. It needs calibration for acceleration as well, which will get mussed up with sharp movements.

3.Hit Lock Calibration. DO NOT ZERO OUT.

4. Place the VR920 flat on a surface that is not magnetic or even near something magnetic. A clear wooden table works, or even just clearing a big spot off a desk.

5.Making sure it's flat, Align it with exactly 179° or -179°. Being flat, it will also line up exactly with yaw and pitch.

6.Zero it out carefully.

The VR920 default yaw is exactly opposite magnetic north. For some reason, forcing it to zero the other direction causes it to be able to accommodate much better.

Try this yourself, then post on here if it works. I haven't been able to test anywhere else than where I am, so I need the input.

GlovePIE 0.30 officially released

CarlKenner — Mon, 31 Dec 2007 08:49:59 GMT

I have finally finished and uploaded GlovePIE 0.30 (in time for a 2007 release).

You can download it from:

http://carl.kenner.googlepages.com/glovepie_download

Please use this version instead of the pre-release versions that I posted here before.

This version actually includes documentation and other such luxuries.

VR920 + GlovePie = General Mouse Movements Script?

Adrealist — Tue, 09 Jun 2009 03:54:13 GMT

Hello,

I got my VR920 today and have spent over 5 hours searching for a script that will let me use the motion tracking in the headset to function as a mouse for generally any game. Is that possible? it seems like there were various posts that mentioned people who managed to do it, and thus not limited to any game. Rather important for me and a friend of mine who play Aion - on a chinese server, not released for another 6 months in the US. In addition to the 3-D interfaces for Windows OS and Internet Explorer, and so many other uses that their compatibilities may never cover. I know nothing about coding and am dumb struck to try and figure out the GlovePie's native language to do this myself. It would be different if I had a base script to build off of and customize myself.

Another question... the Stereoscopic Player that supposedly can give a shallow interpretation of 3-D to a 2-D movie, there were over 40 options to play it in. I started from the top and worked my way down, none of them adding to the quality. That must of been a misunderstanding, both of these situations may not be possible.

Glovepie and Lockon

kitkat — Fri, 09 Jan 2009 17:27:01 GMT

Hi All -

Please help - I've seen on You Tube how great the VR920, Lock on and Glovepie all work together and I want in! Can somebody please give me some simple instructions on how to get it all working?

I have version 0.29 of Glovepie, it does not appear to have a VR920 directory, which I noticed was referenced in another post? I've copied a number of scripts into the first page of glovepie and pressed run, then I've ran Lock on, however the emulation does nothing - Nothing happens?

Please please please help!

Cheers -Dave

What FPS games have separate head tracking from movement

Bangemdead — Wed, 06 Aug 2008 14:02:50 GMT

Can any body tell me what FPS games have separate head tracking from movement? I believe UT2004 does, any others?

Cheers

IWRGetTracking returning zeros

paco — Sat, 19 Sep 2009 01:44:50 GMT

I'm trying to get access to the tracking data from the headware using the following code (which compiles with no warnings under mingw gcc) :

[quote]#define IWEARDRV_EXPLICIT
#include
#include "iweardrv.h"
#include "iwrstdrv.h"

// ***************************** Main windows entry point *******************************
int APIENTRY WinMain(HINSTANCE hInstance,HINSTANCE hPrevInstance,LPSTR lpCmdLine,int nCmdShow) {
printf("started");

HINSTANCE m_hIwear = LoadLibrary(TEXT("IWEARDRV.DLL"));
if (m_hIwear) {
IWROpenTracker = (PIWROPENTRACKER)GetProcAddress(m_hIwear, TEXT("IWROpenTracker"));
IWRCloseTracker = (PIWRCLOSETRACKER)GetProcAddress(m_hIwear, TEXT("IWRCloseTracker"));
IWRZeroSet = (PIWRZEROSET)GetProcAddress(m_hIwear, TEXT("IWRZeroSet"));
IWRGetTracking = (PIWRGETTRACKING)GetProcAddress(m_hIwear, TEXT("IWRGetTracking"));
IWRSetFilterState = (PIWRSETFILTERSTATE)GetProcAddress(m_hIwear, TEXT("IWRSetFilterState"));
}
else {
printf("Error opening tracker");
exit(1);
}

printf("opening tracker");

DWORD open_res=IWROpenTracker();

if (open_res==ERROR_SUCCESS) {
printf("tracker opened ok!");
long yaw=0;
long pitch=0;
long roll=0;
printf("getting tracking...");
//DWORD trk_res=0;
DWORD trk_res=IWRGetTracking(&yaw,&pitch, &roll);
if (trk_res==ERROR_SUCCESS) {
printf("tracker polled ok!");
printf("yaw: %lu pitch: %lu roll: %lu",yaw,pitch,roll);
}
else {
printf("Error polling tracking location");
}
IWRCloseTracker();
}
if (open_res==ERROR_DEV_NOT_EXIST) {
printf("Error opening tracker - not connected to computer!");
}

if (m_hIwear) {
FreeLibrary(m_hIwear);
m_hIwear=NULL;
}

printf("finished!");
return 0;
}

[/quote]

For output all I get are zeros! Can anyone tell me why? The iWearMonitor seems to be working fine. I can even read version numbers correctly - but not the tracking!!!!!

get error form "HelloTracker2"

lw89 — Wed, 19 Aug 2009 08:57:42 GMT

hello:

i have download Iwear sdk. and i study with "HelloTracker2". but when i run it in vc++ 2005, I get error about cant convert to vc2005. I try build a new project use vc2005 and use code file form "HelloTracker2" . i get some error i can finger out.

libcmtd.lib(wwincrt0.obj) : error LNK2019: unresolved external symbol _wWinMain@16 referenced in function ___tmainCRTStartup

1>C:\work\orgeTutorial\vr920\Debug\vr920.exe : fatal error LNK1120: 1 unresolved externals

so what can i do. is "HelloTracker2" can run in vc2005. Do i need to change something. by the way, is the right place i ask about this question.

Linux driver progress

Mal — Tue, 31 Jul 2007 23:43:38 GMT

Hi. As some of you might know I've been working with figuring out the data the VR920 sends to the computer to build a Linux driver/programming interface for the head tracking (and hopefully stereo 3D in the future). Well, I've made some progress so far...

Here's a link to a picture of what it looks like with my little test program right now. Note that the on-screen object is mimicking the alignment of the VR920.
[url]http://cybersanitarium.com/tmp/vr920_Linux_1.jpg[/url]

There's a little programming interface I've created that basically just allows a coder to get three vectors (up, right, back, and their inverses) that define the alignment of the VR920, the ability to set a zero alignment, and the ability to get a matrix (to transform an object) or inverted matrix (to transform the world around the viewer, possibly) that can be passed directly into OpenGL as a transformation matrix (see: glMultMatrixd()).

Now, I'll be the first to tell anyone that my skills with vector and matrix math aren't quite what they were when I last took a college linear algebra class. So I'm not entirely sure how to get yaw, pitch, and roll values individually without running into problems with "gimbal lock" almost immediately. I think it's probably a symptom of any Euler angle representations like that, but it would certainly help for more simple applications of the tracking features.

There's also the problem of calibration that I need some help with if the developers would be so kind as to lend me a hint about this. The tracking works fine for some angles, but starts to get pretty twitchy at others. This is only concerning the yaw rotation, though, as I can almost always seem to accurately determine the pitch and roll.

So this is what I determined to be the data that the VR920 was sending to the computer every time it read data from it...
3 bytes that do not seem to change
3 16-bit integers giving an 'up' vector
3 16-bit integers that give a vector going up and to a side
1 more byte that does not change

Is this (more or less) accurate? Should I be looking at the data a different way? The 'up' vector is there, and I take the cross product of that with the other vector to get the headset's z-axis, then the cross product of that z-axis vector with the 'up' y-axis vector to get the x-axis vector. All the vectors are then normalized so their magnitude is 1. The transformation matrix is then made from that.

I was going in a different direction early on, and would find min/max values for each of the 16-bit integers as I thought that's what was going on in the calibration in the Windows driver. It would then turn each number into a floating point number from -1 to 1 from that, meaning that the lowest they would go would always be -1, and the highest would always be 1. I'm wondering, is this an approach I should use? Would it fix the problems of it becoming really unstable at certain angles?

Thanks for any input anyone might have. I'm really having a lot of fun working with this thing.

As for my code, I'd like to clean it up and solve this instability problem before posting it up. I also need to add more error checking so the test app doesn't freeze horribly when you unplug the thing. :D

How to make rotation smooth

lw89 — Fri, 28 Aug 2009 04:39:23 GMT

Hello:

I got tracking work in my project. i use tracking to rotate camera. but tracking data always changed, even u put goggle on the table. I have convert tracking data into degree. Is any idea that can make rotation smooth, dont too sensitive.

how to start program tracking!!!!!!

lw89 — Mon, 17 Aug 2009 08:23:14 GMT

hello:

I am new here, and i plan use vr920 tracking in my project. so can someone tell me how can i start with it. I use ogre3D and vc++ 2005. I dont have any idea to start it. what do need to do first, or some website have move infromation about program tracking with vr920.

thank you in advanence!!!!!!!!!!!!!

6-DOF using the VR920 and a Wiimote

Steffan — Sat, 30 Aug 2008 09:30:55 GMT

Howdy, I'm new here, and I thought of an idea to get 6-DOF using a Wii Remote and the VR920.

Okay, so here's what you need.
-A Wii Remote
-A Sensorbar (or any other kind of infrared-light source)
-An iWear VR920 (durr)
-A Bluetooth dongle

Kay, assuming you have all this junk, let's get started.
First of all, connect your Wiimote to your computer. (A lot of people use [url=http://www.bluesoleil.com]BlueSoleil[/url], but I don't care for it)

Second, find a way to attach your sensorbar to the VR920.
I just used tape to make it stick to it, see.

[img]http://img501.imageshack.us/img501/1297/01mo7.jpg[/img]
[i]My VR920 with a Wii Sensorbar on top.[/i]

Okay, now, put your Wii Remote on top of your monitor, like I did.

[img]http://img511.imageshack.us/img511/6095/02hb7.jpg[/img]
[i]Don't ask me how I got it to balance on there...[/i]

Okay... so using this set up, you can get 6 degrees of freedom
Now, the Wiiremote can sense your motions.
You can now move up, down, left, right, backward, and forward.
Combine that with the 3 degrees the VR920 has, and [i]voila[/i], 6-DOF!!

And the last step, download GlovePIE and make it run this script.
[CODE]FakeTrackIR.yaw = (vr920.Yaw - var.offset)
FakeTrackIR.pitch = vr920.Pitch
FakeTrackIR.roll = -vr920.Roll
FakeTrackIR.x = -(Wiimote.dot1x-500)/1024
FakeTrackIR.y = (Wiimote.dot1y-500)/1024
FakeTrackIR.z = smooth((Wiimote.dot1size/5)-0.5)
debug = 'X: '+FakeTrackIR.x+', Y: '+FakeTrackIR.y+', Z: '+FakeTrackIR.z

//Written by Steffan Mitrovic! :D[/CODE]

Please note, I've only tested the script in Live For Speed, but it worked great, so it'll probably work fine for other TrackIR games as well. (You [i]might[/i] need to tweak the sensitivity, though)

Hope you'll enjoy my cheap method of being able to get 6-DOF using just a VR920 and a Wiimote. :D

yet more head tracking problems

tzetsin — Wed, 06 Feb 2008 23:45:16 GMT

ok i dont want to be a [meanie] but at what point do i finnaly say i think my glasses are pooched? i've been trying and trying and trying and i absolutely CANNOT get turning left and right to work with any kind of reliablility. on the off chance i get it to work in the calibrator it'll be completly useless in fsx or il2, then i'll switch back to the calibrator to see if its functioning and it "seems" to be moving left and right properly, just not within the application.

dont say calibrate it for an hour, if i gotta calibrate these sobs for anouther 10 mins i'll run em over with my truck.

No Tracking

Rascal — Tue, 23 Jun 2009 09:00:40 GMT

Greetings,

I am just looking for some insite as to why the tracking does not work in any game, I can calibrate it just fine, however when in games like IL2, or Warbirds, Even the Bonus Games that came with the installation CD have no tracking,

Am I missing something?

Tracking in opengl

tavigan — Thu, 07 Aug 2008 09:51:38 GMT

The vr920 comes with example software in the sdk, and i want to use this in opengl, so

1) Has anyone used the vr920 in opengl, i am only talking about the head tracking capabilities?

2) How do you do it?

3) how do you load a webcam into opengl?

Headtracking in FSX... Yet again.

Cronoz[DK] — Mon, 29 Dec 2008 03:44:18 GMT

Hello.

My apologies for bringing this subject up once again. I have read through all the topics in this forum regarding the headtracking feature. So far, I haven't found a single post, with advice that worked for me. I may have missed something... but here goes:

Rig: A shuttle PC model SX38P2 Pro (Intel X38 chipset) running on an Intel Q9300 CPU, 4 GB ram, and a 8800GT. OS is Vista Ultimate (32 bit).

Although I do have other games, that supposedly support headtracking, FSX has been my primary concern. (FSX, standard edition, updated to SP2.) I managed to get the headtracking to work once. When version 2.3 of the drivers came out. I have absolutely NO idea how. My pc was recently reinstalled, so FSX is now a clean install also. I have of course tried downgrading the drivers from 2.4 to 2.3, but the tracking in FSX still doesn't work now. I have tried all the suggestions I could find on this forum; copying the files manually, pointing to the directory, where FSX is installed (not the default one). No go.

When I booted up FSX the first time, after I used the Iwear monitor to install the files automatically, it did ask me whether I wanted to run Itracker.dll (forgot the exact name...) and make it run everytime FSX started. I clicked yes. No go though. No tracking inside the game whatsoever. And furthermore, I noticed that it, for some reason, disabled the normal mouselook function of the game. (When you hold space and move the mouse, you can look around...) The little cross appears as normal, when spacebar is pressed, but no view panning when the mouse is moved. Dont know if this has anything to do with anything.

I KNOW for a fact, that the tracking works. It calibrates just fine, and those little applications, that comes with the driver downloads nowadays, works just fine too. (that psychedelic music player for instance...) :-)

Anyway: If there is anyone in here, preferably someone running Vista as well, that has this thing working as it should, I would be profoundly greatful, if you could give me the exact instructions as to how you got it working... Cause this thing is starting to get on my nerves. :w00t: :hehe:

/Anders

error in tracking

jordi — Mon, 06 Apr 2009 05:58:59 GMT

hello, i'm currently doing my research project on the vr920 and i have found a problem.

i am monitorizing the yaw, pitch and roll when i move the glasses. i have created a program in matlab that shows the variations of each of them in degrees when i move. the problem is that when i move the glasses horizontally on a table (no rolling it), about 20-30 cm, i find a deviation of around 15 degrees in yaw only. i understood that it should be constant. otherwise, how do i diferenciate whether i'm moving horizontally or rotating? is it a problem of the glasses?

thanks in advance

As much as I like looking at the sky...

sketchystories — Fri, 27 Mar 2009 22:18:08 GMT

I'm trying to use the VR920 with glovepie for mouse look on unsupported games. I've got it working pretty well but I've come across a stubborn problem. The Y axis gradually drifts up when I look left or right, so after looking side to side a few times I'll be looking skyward. I've tried recalibrating using the Vuzix calibration tool but I always encounter the same subtle drift up whenever I look left or right.

I figure the best way to solve this problem would be to write something into the current script I'm using (found here on the forum) that counteracts this upward pitch whenever the yaw changes. I know nothing about scripting however so I was hoping someone here could help me out or has an alternate solution.

All the issues with FSX and tracking

daytonabeach — Sun, 22 Mar 2009 11:31:32 GMT

Hi!

Ive been reading dosens of post about problems with tracking in FSX, but still havent found the solution to my problem...

Ive finally managed to calibrate the glasses so that they apperar to work properly according to the calibration software, also after the zero settings, BUT, when i start FSX it always points to the right section of the cockpit, and if i try to turn to the left, it barely moves that direction.

It doesnt seem so react the same way in FSX as in the calibration software, why, and what im i doing wrong?

Ive alos noticed dozen of similiar post but no solutions or reply to them, does that mean that FSX isnt fully supported with the VR920?
I assume so sine support left the answers to it unreplied...

Would be nice to get a honest answer and not "pretending" it should work answers....

Thx

Chris

Zero Set Not Seeming to Work

bobxor — Tue, 23 Dec 2008 07:31:14 GMT

Hi,

I've gone through the forum posts with finding someone complaining of a similar issue but no answer as to a solution. So I thought I'd start a new post.

I'm having a problem where it doesn't seem to record where I set the zero set. I'll face east and zero set, or face south and zero set, but when I pull up the monitor the Yaw values turn zero at the same yaw angle (south-east). I'm annoyed because it's tracking great except not seeming to zero set properly.

By the way, I'm not sure if there is a correlation to where you use zero set and where zero Yaw is reported by the manager. I only notice that where zero Yaw is reported in the monitor is where dead-center is in FSX.

Thanks for any help!

How To setup COD4 for head tracking

djjoke — Tue, 26 Aug 2008 14:08:46 GMT

I´ve just a little problem.

I buyed VR920 and all functions done, but in cod4 only the
stereoscopy is functional.

I installed VR920 v2.2 and updated my nvidia grafic drivers. But the
head tracking wouldn´t work in cod4......why.....??

could someone help me?

AV 230 XL

Leo — Thu, 05 Feb 2009 12:53:14 GMT

Hi there i am a new customer to the vuzix experience and have just bought a AV 230 XL that simulates a 44'' screen from 9 foot away can any one please tell me if is compatable with the xbox 360? thank you for your time and replies.

Tracking not working in any game

Lifespan — Fri, 02 Jan 2009 21:29:35 GMT

Is there a trick to getting tracking to work in FPS'? I have calibrated my glasses and they seem to line up quite well with the indicators onscreen, but one I start playing the game they do not work at all. For example, in both COD4 and TF2, large motions will only result in a strange yaw jerk (often in the wrong direction) and no pitch change. I have toyed with the mouse settings in each game, but it does not help.

Glovepie VR920 Scripts missings

kitkat — Sat, 10 Jan 2009 05:39:37 GMT

Hi -

IS it me or are the Glovepie VR920 folder missing from the Glovepie download site?

Cheers - Dave

FSX and GlovePIE with vr920 any clue ?

LukeDuke — Fri, 22 Feb 2008 15:10:29 GMT

Hi folks,
I have a problem with headtracking while playing FSX, it shakes a bit in yaw axis and didnt managed to figure out how to fix it. Ive tried to calibrate it for 5 minutes etc... so I decided to have a look at GlovePIE, managed to smooth the script for faking the mouse so the cursor is not shaking and not moving by itself but have no clue how to get it into FSX. Is there any dll needed by trackIR or FSX itself has support for trackIR so I might use Faketrackir function from GlovePIE ? Did anybody get it work ? Thanks for help

Any one knows what this means??

pilotguy22 — Tue, 13 Jan 2009 18:37:12 GMT

Does anyone know what this means, "IWRProxy: startup IWRProxy: Locking 1, RenderMethod 0
IWRProxy: Shutdown". I found this in the FSX directory under VR920flight.log..

I have no tracking in FSX, but the 3D stereo works well.... Is there anything I could do to make the tracking work??? I currently have FSX SP 1 & 2 installed with updated drivers for the VR920 (2.4)... I have tried removing the modules in FSX to see what happens, but no luck... I have also tried the steps in the info package in the VR920 iWear, but nothing helped...

Also, I have notice that every time I try to add FSX in the IwearMonitor, it seems to load forever and nothing happens...almost like if it freezes...any one have this problem before and solved it???

These are my specs: Intel core 2 Quad, 8800GT, and Windows Vista 64...Thanks for any help..

Combat Flight Sim 3 - Tracking

DesH — Mon, 24 Mar 2008 12:46:01 GMT

I'm having real problems getting CFS3 to work with headtracking, has anyone got any suggestions ?

I've got stereo3D no probs with and have been using Glovepie perfectly with other titles however I cant find an option in CFS3 to enable TrackIR ? Am I missing something ?

Regards

Des

Very Disappointed with FSX and VR920

kitkat — Thu, 08 Jan 2009 17:03:54 GMT

Hi -

Just got my VR920 a few days ago, its kept me up most evening since! Unfortunately for the wrong reasons! Nothing works with FSX! I've done the CRTL F7 and CTRL F8, I've upgraded FSX to SP2, the drivers and firmware on the VR920 appear to be the latest, I've taken it off the application monitor list then re-added it. After reading the posts the only conclusion I can come to is that the device asks you to put a DLL file in a FSX directory - that file structure does not exist on my windows XP system. I've noticed a lot of posts about FSX and the majority of them appear to be not answered.

I may have not bought the device had I known that it was going to be so much trouble.

Could the Techies sort a simple crib sheet for setting up FSX on the VR920? Is this too much to ask?

Ta - Kitkat

GlovePie and Vr920

sf — Sat, 23 Aug 2008 14:32:18 GMT

Hi,
I just got vr920 and would like to use it for Trakmania and other games. I heard there is this program called GlovePie that enables us to do just that(use vr920 in games not supported by vuzix drivers).
Aparently, we have to configure a specific file for each game, question is:
Aren´t there users of Glovepie who have already configured this files and are ready to share them?

Linux Driver

MWorks — Sat, 20 Dec 2008 06:12:37 GMT

First of all sorry about my english. So, Mal, how's it going? I would like to help you with the driver, in my free time XD. I'm about to have one VR920 so after that I'm ready.

Maybe you can give me the latest version of your driver, that would be a good beginning. Im working with ubuntu linux, by the way.

No FSX Tracking

Justis — Wed, 23 Apr 2008 17:26:23 GMT

My FSX tracking is not working, can anyone help? Thanks :)
BTW, mouse look in general isn't working in FSX, when it was working fine before booting into the vr920. Also, is there a test for stereoscopy?