Opentrack - 2.2a2 file (allows 90degree pitch view)

[216th_Xenos]

Hi all, with the recent update, a lot of Freetrack users have apparently not been able to play anymore due to it not working with BOS.

Opentrack is working absolutely fine right now and I would highly recommend it.

 

The newest version of opentrack does not seem to allow 90 degree pitch view, so here is an older version, all you need to do is unzip it. The download version of the site does not include an installer and is near impossible to set up, so here it an actual folder containing it named 'Install1'. Unzip and it should all be ready, up to you guys to tweak it to your liking

 

https://www.dropbox.com/sh/o1ivjr51s0ilj3z/AABVEgxJkImkdAvZf-I4vnp1a?dl=0

 

This is version 2.2a2 for those interested.

 

Hope it works, let me know if you have any problems,

 

Xenos

Edited November 11, 2014 by xenos1234

[SAG]

I Just downloaded, configured and tested this version (which is very hard to find on the internet BTW) and works GREAT!  

 

i recommend this to people who havent been able to run FREETRACK since the patch (it also works better than freetrack).

 

you need to configure the curves to your liking since the default ones are a little oversensitive, but that is just personal taste.

 

i use it with a PS3EYE cam and works wonders.

 

i hope this helps evryone out there who is having trouble with alternative options to TrackIR.

 

Thanks for all the help Xenos and for making this possible!!

 

S!

[No_85_Gramps]

I'm getting 90 degree pitch with the 2.2 (out-of-alpha) version. Did you check the Freetrack protocol settings to be sure that the EZCA box is ticked?

[Feathered_IV]

Is it possible to force trackir hardware to use this program?

[SAG]

I'm getting 90 degree pitch with the 2.2 (out-of-alpha) version. Did you check the Freetrack protocol settings to be sure that the EZCA box is ticked?

I did, and the OpenTrack interface shows 90 degrees, but ingame it only goes about 50-60 degrees up. i have heard other users had tha same problem with your version, so maybe you got lucky or maybe you dont realize you can actually look up in a steeper angle, scheck this version out and see if it makes it better (it did for me)

Is it possible to force trackir hardware to use this program?

the program recognizes webcams, so if there is way out there for TrackIR hardware to be reccognized as a webcam on windows (IDK if it all ready does) then im gussing YES, other than that, i couldnt tell since i dont own a TRACKIR.

[reve_etrange]

I did, and the OpenTrack interface shows 90 degrees, but ingame it only goes about 50-60 degrees up. i have heard other users had tha same problem with your version, so maybe you got lucky or maybe you dont realize you can actually look up in a steeper angle, scheck this version out and see if it makes it better (it did for me).

 

After checking with the mouse, I realized that you're absolutely right (in my case). Thanks for posting the older opentrack build, it actually works much better than either current stable or current unstable. It's possible this just comes down the Accela Mk4 DLL, I haven't tested it yet. In the newer versions, smoothing is much less effective.

 

I've been digging into the PointTracker and Acella Mk4 code to try and figure things out recently, but now I have an anchor point to go back to in the code repository to look for the important differences. Hopefully I'll have some definitive answers soon.

[SAG]

After checking with the mouse, I realized that you're absolutely right (in my case). Thanks for posting the older opentrack build, it actually works much better than either current stable or current unstable. It's possible this just comes down the Accela Mk4 DLL, I haven't tested it yet. In the newer versions, smoothing is much less effective.

 

I've been digging into the PointTracker and Acella Mk4 code to try and figure things out recently, but now I have an anchor point to go back to in the code repository to look for the important differences. Hopefully I'll have some definitive answers soon.

 

No problem, though all credit goes to Xenos since he is the one that actually helped ME out (and now US). 

 

i think we would all appreciate it if you post again here after you make some progress on those "definitive answers"

 

S!

 

SAG

I'm getting 90 degree pitch with the 2.2 (out-of-alpha) version. Did you check the Freetrack protocol settings to be sure that the EZCA box is ticked?

Apparently REVE-ETRANGE got better results with this verison as well.

maybe give it a try yourself (i think youll be happy with the results)

since the software doesnt need installation, it only takes a couple of minutes to see for yourself!! :D

 

S! 

Edited November 12, 2014 by jsags

[reve_etrange]

No problem, though all credit goes to Xenos since he is the one that actually helped ME out (and now US). 

 

Yes, my mistake, thanks Xenos!

 

i think we would all appreciate it if you post again here after you make some progress on those "definitive answers"

 

Of course. The filter version and EZCA settings effects I can test tonight, it's pretty easy for me since I already have several opentrack installations set up. 

[SAG]

Yes, my mistake, thanks Xenos!

 

 

Of course. The filter version and EZCA settings effects I can test tonight, it's pretty easy for me since I already have several opentrack installations set

that would be awesome!! thanks!

[reve_etrange]

Alright, I pretty much have this all figured out. Turns out it has nothing to with the Accela filter, but does involve the EZCA setting. I will talk about three versions of opentrack: 1) 2.2a2, 2) 2.2-end-of-alpha, aka "stable" and 3) 2.3+, aka "unstable."

 

First, it's important to know that applications which need the EZCA setting take a pitch range from -180 to 180. So, what we call "90 degree pitch" will be represented by a value of 180.0 internally in the software.

 

Now, in stable and earlier, the mapping dialog only allows output pitch values up to 90. So, the EZCA setting multiplies the pitch by 2*, in order to achieve the full pitch range. However, between 2.2a2 and stable, a bug was introduced where the yaw is multiplied by 2 instead of pitch. This bug is why I thought EZCA was interfering with smoothing, as the double yaw slope necessitated a higher smoothing value, and why the full pitch range is unavailable regardless of the EZCA setting.

 

In unstable, the swapped axes have been fixed, the mapping dialog permits pitch output up to 180, and the EZCA setting has been removed. However, unstable seems to have some issues with point tracking and I have been unable to find a working configuration. I did make some progress and for anyone willing to help, I suggest starting with steeper mapping curves (as the graph in the mapping dialog has a greatly expanded X-axis). I also had to swap pitch and yaw (unrelated to the issue just described) and invert pitch.

 

I'm going to ask the opentrack developer to release a new stable version, as the axes swap is fixed almost immediately after the tag for stable. For now, I recommend that everyone use the 2.2a2 binary linked in the OP.

 

*Prior to 2.2a2, the EZCA setting also controlled the trackIR dummy executable. However, so many applications require that a process called "trackIR.exe" be present, that  the dummy executable was made to always run.

[NN_RugbyGoth]

Little question : Does Open Track recognize wiimote?

I couldn't make it work but I didn't tried too hard, does someone knows how to make it work?

As a wiimote is a 100fps IR camera, it's the best we can have for head tracking...

[reve_etrange]

Little question : Does Open Track recognize wiimote?

 

I don't think so, although Freetrack apparently does.

 

As a wiimote is a 100fps IR camera, it's the best we can have for head tracking...

 

PS3Eye officially supports 120 fps and can actually run at 180+ fps. Can be had for ~$10.

[216th_Xenos]

Yep, got my PS3 eye second hand for 2 pounds in a local game store (Most of them will have at least a couple lying about somewhere). If you do end using the PS3 eye, you've got to make sure you download the CL-Eye Test program for it, this will allow you to tweak the filters (really important if you have light problems in your room), the resolution and the FPS.

A problem I encountered however is that opentrack would only use the default camera I had (which was my laptop camera), doesn't seem to be the problem anymore though. Anyway, if you run into this problem, go to your control panel - Hardware and Sound - Devices and Printers - Device Manager. In this you will find something called 'imaging devices', from there right click on your default camera to disable it. Downside to this is that it will disable it for everything, but can of course be re-enabled at any time.

[reve_etrange]

A problem I encountered however is that opentrack would only use the default camera I had

 

I am also able to simply select whichever of my two USB cameras I want via opentrack's own menu. Although amusingly when opentrack is opened it cycles through them in order until the selected one is reached (you can see each camera's LED go on in turn).

[No_85_Gramps]

Okay, I went back and checked and you were correct! The 2.2 out-of-alpha does not pitch to 90 degrees. Ran the 2.2a2 version and all is fine. I saw the newer unstable version but as of yet I have not tried it out, maybe tonight. I'll post back with the results.

[SAG]

Okay, I went back and checked and you were correct! The 2.2 out-of-alpha does not pitch to 90 degrees. Ran the 2.2a2 version and all is fine. I saw the newer unstable version but as of yet I have not tried it out, maybe tonight. I'll post back with the results.

 

Roger gramps.

Please do!

[=EXPEND=Dendro]

AWESOME -  been flying sims for a year now and this is the first time I can see straight up with no big blind spot directly above me!!!! Thanks so much guys!

[SAG]

AWESOME -  been flying sims for a year now and this is the first time I can see straight up with no big blind spot directly above me!!!! Thanks so much guys!

 

That IS awesome!!

[Fliegenpilz]

Alright, I pretty much have this all figured out. Turns out it has nothing to with the Accela filter, but does involve the EZCA setting. I will talk about three versions of opentrack: 1) 2.2a2, 2) 2.2-end-of-alpha, aka "stable" and 3) 2.3+, aka "unstable."

 

First, it's important to know that applications which need the EZCA setting take a pitch range from -180 to 180. So, what we call "90 degree pitch" will be represented by a value of 180.0 internally in the software.

 

Now, in stable and earlier, the mapping dialog only allows output pitch values up to 90. So, the EZCA setting multiplies the pitch by 2*, in order to achieve the full pitch range. However, between 2.2a2 and stable, a bug was introduced where the yaw is multiplied by 2 instead of pitch. This bug is why I thought EZCA was interfering with smoothing, as the double yaw slope necessitated a higher smoothing value, and why the full pitch range is unavailable regardless of the EZCA setting.

 

In unstable, the swapped axes have been fixed, the mapping dialog permits pitch output up to 180, and the EZCA setting has been removed. However, unstable seems to have some issues with point tracking and I have been unable to find a working configuration. I did make some progress and for anyone willing to help, I suggest starting with steeper mapping curves (as the graph in the mapping dialog has a greatly expanded X-axis). I also had to swap pitch and yaw (unrelated to the issue just described) and invert pitch.

 

I'm going to ask the opentrack developer to release a new stable version, as the axes swap is fixed almost immediately after the tag for stable. For now, I recommend that everyone use the 2.2a2 binary linked in the OP.

 

*Prior to 2.2a2, the EZCA setting also controlled the trackIR dummy executable. However, so many applications require that a process called "trackIR.exe" be present, that  the dummy executable was made to always run.

 

Thank you for the explanation! Now lets hope the developer of OpenTrack releases a quick fix...

 

Jsags, I suppose I don't need to answer your pm anymore?

[SAG]

Thank you for the explanation! Now lets hope the developer of OpenTrack releases a quick fix...

 

Jsags, I suppose I don't need to answer your pm anymore?

 

Lol. No you dont, but thanks for your help, youre the one who got me to look around for that version!!

[No_85_Gramps]

Didn't have a lot of time to test the 2.3 unstable version. It was giving me fits so I just let it go for now. Will try again tomorrow and see what I can get out of it. Initially I was not able to get any response even though the leds were being tracked. Next time I opened it I could not get point tracker to find the leds. 2.2a seems the best at this point.

[SAG]

Didn't have a lot of time to test the 2.3 unstable version. It was giving me fits so I just let it go for now. Will try again tomorrow and see what I can get out of it. Initially I was not able to get any response even though the leds were being tracked. Next time I opened it I could not get point tracker to find the leds. 2.2a seems the best at this point.

Good to know gramps and thanks for testing!

 

Maybe we need to wait for their Devs to release a new Stable befor we jump into 2'3

[No_85_Gramps]

That's probably what I'll do... but I may give it another try anyway.

[III/JG52_Llucmk]

I donwloaded Opentrack as a Freetrack User. I tested FacenotrackIR a long time ago but i was unable to run that correctly as i was doing with the Freetrack. Now i get this F** problem that Dev's caused and don't know why, they don't want to give support to Freetrack Users or something again... (why you broke this?).

 

Then... i tested opentrack, and i'm for now surprised... But i can't make it work properly... The thing is a use a configuration of PS3Eye with 75 fps and a Official Trackclip Pro...

 

I opened Opentrack and i made some tweaks as you can se below.

 

 

Here i don't know what i'm doing so i putted random things to test.

 

 

 

So i explain the problems i have:

 

-First of all, i can move my head in-game, but for example when i move my body to the left, my sight (in-game) goes to the right, same if i move to the right, my sight goes to the left. 

-If i look back, my track comes crazy and inverts the X axis, for example, if i look back, and move my body to the Left, my body goes to the Right.

-The track acts as i had a Big neck in-game, it's not centered as it was with FreeTrack. 

 

 

¿Any solution? I really want to use Opentrack and leave behind Freetrack (casue the no more updates).

[SAG]

I donwloaded Opentrack as a Freetrack User. I tested FacenotrackIR a long time ago but i was unable to run that correctly as i was doing with the Freetrack. Now i get this F** problem that Dev's caused and don't know why, they don't want to give support to Freetrack Users or something again... (why you broke this?).

 

Then... i tested opentrack, and i'm for now surprised... But i can't make it work properly... The thing is a use a configuration of PS3Eye with 75 fps and a Official Trackclip Pro...

 

I opened Opentrack and i made some tweaks as you can se below.

 

 

Here i don't know what i'm doing so i putted random things to test.

 

 

 

So i explain the problems i have:

 

-First of all, i can move my head in-game, but for example when i move my body to the left, my sight (in-game) goes to the right, same if i move to the right, my sight goes to the left.

-If i look back, my track comes crazy and inverts the X axis, for example, if i look back, and move my body to the Left, my body goes to the Right.

-The track acts as i had a Big neck in-game, it's not centered as it was with FreeTrack.

 

 

¿Any solution? I really want to use Opentrack and leave behind Freetrack (casue the no more updates).

 

There is some initial configuration you have to set up before using it. I can help you through Teamspeak if you like. in about 2 hours when i get back home

For starters, ypu need to use mk4 filter....

 

Ill be able to help you a bit more in two hours

[III/JG52_Llucmk]

There is some initial configuration you have to set up before using it. I can help you through Teamspeak if you like. in about 2 hours when i get back home

For starters, ypu need to use mk4 filter....

 

Ill be able to help you a bit more in two hours

I'm sorry, i'm not able to stay here for 2 hours, here it's late and i have to wake up tomorrow "early". Maybe if you could tell me some aspects i should change. I can give you all the pictures and info you need about it. 

[SAG]

I'm sorry, i'm not able to stay here for 2 hours, here it's late and i have to wake up tomorrow "early". Maybe if you could tell me some aspects i should change. I can give you all the pictures and info you need about it. 

 

 

Here You Go!! :D

 

 

 

You should use Accela Filter MK4 (its not clear on the image)

 

also when calibrating, you have to have your camera ON otherwise it wont calibrate

 

Cheers!

Edited November 14, 2014 by jsags

[=EXPEND=Dendro]

Yes..... your curves are very important, and by playing with the XYZ curves will help reducing or eliminating completely the "Big neck effect" you are experiencing.

[reve_etrange]

The opentrack stable release has been updated to output proper Pitch values values for BoS with EZCA on, Just as in 2.2a2. So no need to trample Xenos1234's dropbox anymore.

 

Also, I recommend enabling "translation compensation" while leaving "Z-axis compensation" disabled. That will give you correct translations when looking over your shoulder.

Edited November 14, 2014 by reve_etrange

[SAG]

The opentrack stable release has been updated to output proper Pitch values values for BoS with EZCA on, Just as in 2.2a2. So no need to trample Xenos1234's dropbox anymore.

 

Also, I recommend enabling "translation compensation" while leaving "Z-axis compensation" disabled. That will give you correct translations when looking over your shoulder.

Oh, great!! Its good to know we now have a propper stable version for this game ( i dont know if you made that happen, but...) Thankyou!!!

So this would be the 2'2 version right??

[reve_etrange]

Stanislaw (opentrack developer) did all the work, I just bugged him about it.

 

Yeah, it's the 2.2 version, the binary zip archive is called "opentrack-2.2-stable" and the title in the application window is "opentrack-stable-20141112." Direct link.

[SAG]

Stanislaw (opentrack developer) did all the work, I just bugged him about it.

 

Yeah, it's the 2.2 version, the binary zip archive is called "opentrack-2.2-stable" and the title in the application window is "opentrack-stable-20141112." Direct link.

 

Cool man. many thanks

[No_85_Gramps]

This version, so far, is the best. Still trying to find some time to mess with the 2.3 RC.

[-VG-CAriza]

Great info, I was a long time FactracknoIR user but with this latest opentrack stable build Im switching to it.  Specially since I get 90 degree pitch.  Question though: Anyone having problems with the ROLL axis?  If I enable it my tracking goes crazy, cant seem to calibrate any axis when its activated.  Pitch and yaw movements go into roll.  All is working right now with the roll axis disabled.

[SAG]

Great info, I was a long time FactracknoIR user but with this latest opentrack stable build Im switching to it. Specially since I get 90 degree pitch. Question though: Anyone having problems with the ROLL axis? If I enable it my tracking goes crazy, cant seem to calibrate any axis when its activated. Pitch and yaw movements go into roll. All is working right now with the roll axis disabled.

 

Hmmm im sorry to say IDK how to fix this problen since i dont like usin roll on my headtracking. Wotks perfect for me qithout roll though.

[reve_etrange]

Great info, I was a long time FactracknoIR user but with this latest opentrack stable build Im switching to it.  Specially since I get 90 degree pitch.  Question though: Anyone having problems with the ROLL axis?  If I enable it my tracking goes crazy, cant seem to calibrate any axis when its activated.  Pitch and yaw movements go into roll.  All is working right now with the roll axis disabled.

 

I'll try my best to help. A few questions: 

1. Are your model dimensions correct? (Point tracker)
2. Have you tried calibrating the model position? (Point tracker)
3. Is dynamic pose resolution enabled or not? (Point tracker)
4. Is it possible certain axes are switched? (Mapping)

I do use the roll axis but have a very gentle (linear) curve - 25 deg input gives 50 deg output.

 

PS Will be away over the weekend so might not be able to respond til Monday.

Edited November 21, 2014 by reve_etrange

[-VG-CAriza]

I'll try my best to help. A few questions: 

1. Are your model dimensions correct? (Point tracker)
2. Have you tried calibrating the model position? (Point tracker)
3. Is dynamic pose resolution enabled or not? (Point tracker)
4. Is it possible certain axes are switched? (Mapping)

I do use the roll axis but have a very gentle (linear) curve - 25 deg input gives 50 deg output.

 

PS Will be away over the weekend so might not be able to respond til Monday.

 

Thanks for the help:

 

1.  Im using the factory trackir pro clip.  I measured the following dimensions:

 

 

2.  Yes tried calibrating, different ways.  Moving only on the xyz axis and also moving all directions.

 

3.  Dynamic pose resolution in unchecked. What is this?

 

4.  Axis are fine, had to invert a couple. 

 

Im using a Sony PS3 eye cam with the aftermarket lense.  Has worked flawlessly in facetracknoIR.  Tried messing with different camera position orientation angles, that influenced this weird yaw movement but couldnt fix it.  Left the pitch aprox how my camera sits on top of the monitor. -55 degrees

 

Here are some more settings I have:

 

 

 

Edited November 22, 2014 by cariza

[reve_etrange]

cariza, can you try experimenting with a few settings?

1. Try not setting the camera pitch (e.g. 0 or -15 instead of -55 deg, have you measured with a protractor?)
2. Is the camera yaw set to center the point clip?
3. Try putting the PS3 Eye on 320 x 240 resolution (you can then set the frame rate as high as 180)
4. Hysteresis is very high, try zero or low hysteresis (always watch the video feed, make sure you are stable at 3 points when changing point tracker settings)
5. Does the negative Z-axis model calibration make sense for you? I have +12 there with my DIY point clip on my headset.
6. Are you sure roll needs to be inverted?
7. You can dry dynamic pose resolution, but I don't think it will make a difference

Those are the potential trouble spots I can see. I agree with your assessment that it's probably got the most to do with the camera angles - you might try placing the camera right in front of you to confirm that.

 

I also find it useful to bind the recenter command to a controller button (recentering is usually required when playing with opentracker settings, and occasionally required in-game). I set the recenter hotkey to Home in opentrack, and then use a Saitek profile to set a throttle button to Home.

Edited November 24, 2014 by reve_etrange

[Emgy]

Factory trackir clip dimensions are:

30 

40

70

80

 

Did you give it enough time to calibrate? It can take 30-60 seconds for it to really stabilize.

 

Btw if you want accela 4 to use its predictor function to help stability, you need to set low values for Order #2 and #3. Try low values like 10 or even 1.5. This has a potential to make a big difference for stability. I never have to re-center in-game anymore, except if I move my chair or get up/sit down.

Edited November 25, 2014 by Calvamos

[reve_etrange]

Did you give it enough time to calibrate? It can take 30-60 seconds for it to really stabilize.

 

Btw if you want accela 4 to use its predictor function to help stability, you need to set low values for Order #2 and #3. Try low values like 10 or even 1.5. This has a potential to make a big difference for stability. I never have to re-center in-game anymore, except if I move my chair or get up/sit down.

 

I agree with the above. It sounds like his problem wasn't filter-related (though I guess it might be), so I didn't comment on the settings.