Dan here from EDTracker. I'm looking into testing FaceTrackNoIR with EDTracker and am seeing some curious behaviour on the raw input values in the joystick plugin.
Checking raw values in windows USB game properties, I'm seeing the expected ranges of +/-32768 on the X and Z axis, with half that on the Y (to be expected).
However FaceTrackNoIR seems to be reporting some odd raw input numbers in the tracker detail screen.
Roll (Z) reports raw values of 0 to 65535
X and Y seem to either be massively scaled down, or possibly reading the wrong bytes/offsets as no number change is reported with device movement until it's rotated about 20 degrees from straight ahead, at which point the raw input values start to increment - it seems to wrap at +/-1000 points. I've certainly not got anything set in the EDTracker software that should cause this, it's on linear scaling with 1:1 axis scaling.
I think what you've possibly done is developed the joystick input against an EDTracker that was configured in exponential scaling mode by accident? Because rather magically, 1000 points on the X and Y (when in exponential mode) maps perfectly to the EDTracker axis limits when it's configured at the default 16/16 values on Exponential scaling!!!
So - if that's the case - my advice would be not to perform any scaling of input values but look for a linear range from +/-32768. We always advise customers to configure their EDTracker to linear scaling and 1:1 when using it with external software like FaceTrackNoIR... so I guess this might be confusing people.
Anyway, hope my interpretation of what's happening is correct. Apologies if not!
Cheers,
Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Dan,
I tried and tested Ftnoir with the Edtracker for Wim.I first had also some problems with the fact that I had to increase the scaling in the Edtracker software to 6(response mode linear) instead of 1 I used with opentrack.But after spending a lot of time in trying different settings and comparing with opentrack I can only have one conclusion.The way Wim has made Ftnoir works great and there seems to be no difference between Ftnoir or opentrack if tweaked well.
Cheers,
Willem
Last edit: WL 2016-12-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd agree, it works well :) it's just the odd built-in scaling of the joystick values makes it rather confusing for users. I mean, you and I managed to work out a kludge to get it responding correctly, which is great - but I would imagine 50% of users out there won't have quite the same amount of patience and will dismiss it as "not functional" fairly early on in their experience ;)
Just wanted to provide the feedback, that's all. If Wim chooses to fix it, great, but there is indeed a (non-obvious) workaround...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm going to raise this as a bug, see if Wim has an interest in addressing it. We always advise users of 3rd party TrackIR emulators to run 1:1 scaling and linear, so this built-in re-scaling within FTNoIR is going to confuse a lot of people, I think. Worth a try ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I want to use EDTracker2 with Prepar3d V4. I have installed v200 with Joystick input & SimconnectSP2 plugins and i have strange "dead zones" near centered EDTracker position. I think few degtrees PITCH and YAW tracker rotation FtnIR not response, zero input data. It this time EDTracker software indicates all movements. With more degrees of declination FtnIR starts to count. Visually same situation in Prepar3d. ROLL axis works perfectly, no any dead zone. Is there some solution to avoid input deadzones?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
what scaling for pitch and yaw are you using in the edtracker software?For using with Ftnoir it must be at least 6.And it can be possible that you have to make a small change in the accela filter setting.Befor you do this make a backup of the original accela filter settings.
These settings can be found in the profile you made :C:\Program Files (x86)\Abbequerque Inc\FaceTrackNoIR_v200\your profile
(I expect that on your pc it will be the same)
I use Ftnoir for IL2-Clod and I have this middle deadzone also but I don't see it as a problem because it makes it easier to look through the crosshair to aim.I have a 27-inch monitor and for me it is just a small zone where Ftnoir shows movement and in game not.Probably if this didn't happen I should ad this deadzone myself.If possible could you make a video of what it looks like so we can see how big your deadzone is and if there is something what can be done about it.Although that it is not a problem for me, I agree that it should be possible to have no deadzone at al.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i hope i'll made video tomorrow. about deadzone thats critical because i use EDTracker with selfmade HMD (bobovr z4 case with Topfoison 6inch mipi display). Before FtnIR i used Opentrack with Joystick input and Simconnect or FreeTrack output depend of game. By using FtnIR i was planned to use second source like webcam to add X, Y, Z axis movement thats Opentrack with EDtracker don't have.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alexey, I also made a short unedited video to let you see what that deadzone looks like in my flight sim.The flight sim is IL2-Cliffs of Dover.With Ftmoir you can also use a second joystick to get 6DOF.I have a Saitek x52-pro stick, rudderpeddals and a BUo836a joystick controller.I don't use the twist and some other axis on my joystick and I use these to have 6DOF.The twist I use to move to the left or right with my head. https://youtu.be/1fG2hP1tp5g
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Wim,
Dan here from EDTracker. I'm looking into testing FaceTrackNoIR with EDTracker and am seeing some curious behaviour on the raw input values in the joystick plugin.
Checking raw values in windows USB game properties, I'm seeing the expected ranges of +/-32768 on the X and Z axis, with half that on the Y (to be expected).
However FaceTrackNoIR seems to be reporting some odd raw input numbers in the tracker detail screen.
Roll (Z) reports raw values of 0 to 65535
X and Y seem to either be massively scaled down, or possibly reading the wrong bytes/offsets as no number change is reported with device movement until it's rotated about 20 degrees from straight ahead, at which point the raw input values start to increment - it seems to wrap at +/-1000 points. I've certainly not got anything set in the EDTracker software that should cause this, it's on linear scaling with 1:1 axis scaling.
I think what you've possibly done is developed the joystick input against an EDTracker that was configured in exponential scaling mode by accident? Because rather magically, 1000 points on the X and Y (when in exponential mode) maps perfectly to the EDTracker axis limits when it's configured at the default 16/16 values on Exponential scaling!!!
So - if that's the case - my advice would be not to perform any scaling of input values but look for a linear range from +/-32768. We always advise customers to configure their EDTracker to linear scaling and 1:1 when using it with external software like FaceTrackNoIR... so I guess this might be confusing people.
Anyway, hope my interpretation of what's happening is correct. Apologies if not!
Cheers,
Dan
Hi Dan,
I tried and tested Ftnoir with the Edtracker for Wim.I first had also some problems with the fact that I had to increase the scaling in the Edtracker software to 6(response mode linear) instead of 1 I used with opentrack.But after spending a lot of time in trying different settings and comparing with opentrack I can only have one conclusion.The way Wim has made Ftnoir works great and there seems to be no difference between Ftnoir or opentrack if tweaked well.
Cheers,
Willem
Last edit: WL 2016-12-01
I'd agree, it works well :) it's just the odd built-in scaling of the joystick values makes it rather confusing for users. I mean, you and I managed to work out a kludge to get it responding correctly, which is great - but I would imagine 50% of users out there won't have quite the same amount of patience and will dismiss it as "not functional" fairly early on in their experience ;)
Just wanted to provide the feedback, that's all. If Wim chooses to fix it, great, but there is indeed a (non-obvious) workaround...
I'm going to raise this as a bug, see if Wim has an interest in addressing it. We always advise users of 3rd party TrackIR emulators to run 1:1 scaling and linear, so this built-in re-scaling within FTNoIR is going to confuse a lot of people, I think. Worth a try ;)
I want to use EDTracker2 with Prepar3d V4. I have installed v200 with Joystick input & SimconnectSP2 plugins and i have strange "dead zones" near centered EDTracker position. I think few degtrees PITCH and YAW tracker rotation FtnIR not response, zero input data. It this time EDTracker software indicates all movements. With more degrees of declination FtnIR starts to count. Visually same situation in Prepar3d. ROLL axis works perfectly, no any dead zone. Is there some solution to avoid input deadzones?
what scaling for pitch and yaw are you using in the edtracker software?For using with Ftnoir it must be at least 6.And it can be possible that you have to make a small change in the accela filter setting.Befor you do this make a backup of the original accela filter settings.
These settings can be found in the profile you made :C:\Program Files (x86)\Abbequerque Inc\FaceTrackNoIR_v200\your profile
(I expect that on your pc it will be the same)
This is what I use
[Accela]
Reduction=75
[Curves-Accela-Scaling-Rotation]
point-count=11
point-0-x=0
point-0-y=0
point-1-x=0.30890052356020897
point-1-y=0.066666666666666693
point-2-x=0.56544502617801096
point-2-y=0.22666666666666699
point-3-x=0.76963350785340301
point-3-y=0.50666666666666704
point-4-x=0.99476439790575899
point-4-y=1
point-5-x=1.2356020942408401
point-5-y=1.61333333333333
point-6-x=1.4764397905759199
point-6-y=2.37333333333333
point-7-x=1.66492146596859
point-7-y=3.1200000000000001
point-8-x=1.80628272251309
point-8-y=3.9199999999999999
point-9-x=1.9162303664921501
point-9-y=4.7066666666666697
point-10-x=2.0052356020942401
point-10-y=5.4400000000000004
point-11-x=2.0052356020942401
point-11-y=5.4400000000000004
[Curves-Accela-Scaling-Translation]
point-count=10
point-0-x=0
point-0-y=0
point-1-x=0.28272251308900498
point-1-y=0.080000000000000002
point-2-x=0.49214659685863898
point-2-y=0.30666666666666698
point-3-x=0.764397905759162
point-3-y=0.83999999999999997
point-4-x=1.0052356020942399
point-4-y=1.62666666666667
point-5-x=1.17277486910995
point-5-y=2.7866666666666702
point-6-x=1.25130890052356
point-6-y=3.6000000000000001
point-7-x=1.31937172774869
point-7-y=4.2933333333333303
point-8-x=1.3821989528795799
point-8-y=4.9066666666666698
point-9-x=1.43455497382199
point-9-y=5.6533333333333298
Related
Wiki: Accela
sorry, thats not work for me. even if i set scaling 16 for pitch and yaw there is the dead zone, less but still there. about filters, i don't use any.
I use Ftnoir for IL2-Clod and I have this middle deadzone also but I don't see it as a problem because it makes it easier to look through the crosshair to aim.I have a 27-inch monitor and for me it is just a small zone where Ftnoir shows movement and in game not.Probably if this didn't happen I should ad this deadzone myself.If possible could you make a video of what it looks like so we can see how big your deadzone is and if there is something what can be done about it.Although that it is not a problem for me, I agree that it should be possible to have no deadzone at al.
i hope i'll made video tomorrow. about deadzone thats critical because i use EDTracker with selfmade HMD (bobovr z4 case with Topfoison 6inch mipi display). Before FtnIR i used Opentrack with Joystick input and Simconnect or FreeTrack output depend of game. By using FtnIR i was planned to use second source like webcam to add X, Y, Z axis movement thats Opentrack with EDtracker don't have.
Alexey, I also made a short unedited video to let you see what that deadzone looks like in my flight sim.The flight sim is IL2-Cliffs of Dover.With Ftmoir you can also use a second joystick to get 6DOF.I have a Saitek x52-pro stick, rudderpeddals and a BUo836a joystick controller.I don't use the twist and some other axis on my joystick and I use these to have 6DOF.The twist I use to move to the left or right with my head.
https://youtu.be/1fG2hP1tp5g