FaceTrackNoir: Unable to look straight up

[SCG_Cryptiks]

Hello everyone,

 

So I've recently moved onto this game after a long 1 year break from flying, however I have encountered a problem that I have to yet to solve and seemingly there is no solution online either. I am unable to look straight up, the camera being blocked when it reaches around 60-70°. I tried increasing my Pitch curve however this just results in the camera angle just jumping from 60-70° to straight behind me. I have been using Face tracking since I broke my Delan clip while moving home so I can't even jumple over to any alternative for the time being. 

 

I was unable to find any answers on the following threads:

 

https://forum.il2sturmovik.com/topic/7821-cant-look-straight/

 

https://forum.il2sturmovik.com/topic/14740-headtracking-issue/?hl=%2Bfacetracknoir&do=findComment&comment=245651

 

https://forum.il2sturmovik.com/topic/19992-cannot-look-trackir/

 

If anyone has a solution I'd be very grateful as this is making tracking rather difficult. 

 

Thanks!

Edited August 18, 2017 by Crypticks

[III/JG52_Otto_-I-]

the camera being blocked when it reaches around 60-70°. I tried increasing my Pitch curve however this just results in the camera angle just jumping from 60-70° to straight behind me....

 

I had this same issue with Facetracknoir. Fixed by swapping to Opentrack...

Well, i've investigated the problem because I used FacetrackNOir from the beginning, when the game released. ..but some months ago I switched to OPENTRACK, and the problem still almost the same, but It is less exaggerated. If the camera point of view is limited about 60-70 degrees upward with Facetracknoir, ..with Opentrack it is limited to 80-85 degrees upward. it is only a few degrees limited..

Note that, if you set the camera pitch axis movement in the Joystick hatswitch, the point of view is increased to about 95 degrees upward.

Therefore  the user with old TrackIR devices, freetrack, or Facetracknoir (who I think, using the same source code) only they can feel the problem in more exaggerated manner. 

The rest of the users, who they not using old headTracker devices, are not reporting the problem because  probably they never tested how the mouse, or hatswitch works..

BTW The people who using the joy hatswitch, preview keys setting, or the mouse for moving the cockpit camera, they have complete movement.

 

My conclusion is that the problem is 50/50 fault of FacetrackNOir, and 1C Studios, and I'm afraid that neither of both will fix the problem. 

Edited August 21, 2017 by III/JG52_Otto_-I-

[J2_Bidu]

I had the same problem in Rise of Flight. The solution here is similar, but somewhat more imperfect.

 

You can edit the current.map file that is located in the game \data\input directory, and paste the following over the default values.

 

[bc_head_pitch]

data_row0 = -2.000000, -1.960000, -1.920000, -1.880000, -1.840000, -1.800000, -1.760000, -1.720000, -1.680000, -1.640000;
data_row1 = -1.600000, -1.540000, -1.500000, -1.460000, -1.420000, -1.380000, -1.340000, -1.300000, -1.260000, -1.220000;
data_row2 = -1.180000, -1.140000, -1.100000, -1.060000, -1.020000, -0.980000, -0.940000, -0.900000, -0.860000, -0.820000;
data_row3 = -0.780000, -0.740000, -0.700000, -0.660000, -0.620000, -0.580000, -0.540000, -0.500000, -0.460000, -0.420000;
data_row4 = -0.380000, -0.340000, -0.300000, -0.260000, -0.220000, -0.180000, -0.140000, -0.100000, -0.060000, -0.020000;
data_row5 = 0.000000, 0.020000, 0.040000, 0.060000, 0.080000, 0.100000, 0.120000, 0.140000, 0.160000, 0.180000;
data_row6 = 0.200000, 0.220000, 0.240000, 0.260000, 0.280000, 0.300000, 0.320000, 0.340000, 0.360000, 0.380000;
data_row7 = 0.400000, 0.420000, 0.440000, 0.460000, 0.480000, 0.500000, 0.520000, 0.540000, 0.560000, 0.580000;
data_row8 = 0.600000, 0.620000, 0.640000, 0.660000, 0.680000, 0.700000, 0.720000, 0.740000, 0.760000, 0.780000;
data_row9 = 0.800000, 0.820000, 0.840000, 0.860000, 0.880000, 0.900000, 0.920000, 0.940000, 0.960000, 0.980000;
data_endrow = 1.000000

 

 

This seems to do the trick. So why imperfect? Well, apparently there's no way to prevent the game overriding these with the default values again but by marking the said file as read-only. This will prevent you from changing the controls in game. And will get you a couple error messages.

 

Best solution I've got so far. I needed a quick fix.

 

[Stumble]

On 8/16/2018 at 6:55 AM, J2_Bidu said:

This will prevent you from changing the controls in game. And will get you a couple error messages.

 

So you can't modify any controls from that point on? it won't mean you have to run with default key mappings?

 

No idea how I hadn't seen this post yet.

 

S!

[J2_Bidu]

3 hours ago, Stumble said:

 

So you can't modify any controls from that point on? it won't mean you have to run with default key mappings?

 

No idea how I hadn't seen this post yet.

 

S!

 

Every time you want to change something you have to make the file writable, enter the game, change whatever you need, exit the game, edit the file to apply this fix, make it read only and enter the game. A bit painful.

Edited January 30, 2020 by J2_Bidu

[Stumble]

Sweet thanks for that Bidu! I've got to try it out some time.

 

S! 

Edited February 5, 2020 by Stumble
Bidu not Budu!!! Apologies :)

[2./SG2_assadoc]

On 8/15/2018 at 9:55 PM, J2_Bidu said:

I had the same problem in Rise of Flight. The solution here is similar, but somewhat more imperfect.

 

You can edit the current.map file that is located in the game \data\input directory, and paste the following over the default values.

 

 

This seems to do the trick. So why imperfect? Well, apparently there's no way to prevent the game overriding these with the default values again but by marking the said file as read-only. This will prevent you from changing the controls in game. And will get you a couple error messages.

 

Best solution I've got so far. I needed a quick fix.

 

this is still the only fix

thank you very much!

[J2_Bidu]

4 hours ago, assadoc said:

this is still the only fix

thank you very much!

 

Glad to help!

 

However I must warn all of you of a possible side-effect of the proposed workaround: since I had the file as read-only, I believe on the latest game update a few new lines that should have been added to the file were not so. What happened? I lost the ability to repair and refuel in Flying Circus, two new options, even though I filled in my key bindings in game. I had two insert those two lines manually. So be alert. Maybe we should back up the changed file, and make it writable before running updates, then comparing the two (with Winmerge, for instance).

[Stumble]

@J2_Bidu Hey bidu me again...

 

With FaceTrackNoIR do you ever have the problem where you cant look down without it snapping away suddenly, looking backwards or at some other random angle. Then pressing the reset center key makes it all fine again.

 

I'm sure I once found a fix for that but i cannot remember anymore...

[Stumble]

 

Also... I've always had this problem but am only just finally trying to find a solution. For some reason my snap views don't save. Pretty much every single time I start a new flight I've gotta set them back up again. Its a real pain!

 

Ive looked in SnapViews folder in the game files (IL-2 Sturmovik Battle of Stalingrad\data\LuaScripts\snapviews) and tried setting it to read only but It didn't seem to work. Have you ever had this issue? I'm wondering if its a problem with my head tracking again...

 

Interesting thing is that my default seating position/view always saves. Its only snap views that dont.

[Stumble]

I finally found out how to fix the whole snap views thing... turns out messing around with the Numpad 5 key to centre the view is not a good idea. It seems to switch into some other mode where snap views are not saved.

 

However I still haven't solved the looking down problem. I'm very close to finally trying to use open track again... lol

[J2_Bidu]

17 hours ago, Stumble said:

@J2_Bidu Hey bidu me again...

 

With FaceTrackNoIR do you ever have the problem where you cant look down without it snapping away suddenly, looking backwards or at some other random angle. Then pressing the reset center key makes it all fine again.

 

I'm sure I once found a fix for that but i cannot remember anymore...

 

I had problems looking down back in the days I had my camera on top of my monitor. Now I have it at the base, which makes it much more natural. I jave occasional difficulties looking at my 7, because the view on one of the 3 dots is blocked by the cable or whatever.

Edited April 11, 2020 by J2_Bidu
Spell check

[Stumble]

I'll give that a go. But at the top of my monitor (only 27") it's pretty level with where me head is. So it's looking straight on. 

[J2_Bidu]

Just an additional note: editing the file can be done while the game is running. You just need to make it writable, change it as described and make it read-only again. To force the game to reload it, just go to the key assignment screen and try to change something, hit Accept, et voilá! It refreshes.

[Cingan]

I am frustrated about this Problem. No solution.

This appear with Facetracking FTNoir and with Pointtracking (DIY IR Delanclip) in Opentrack.

Both optical sensor methods dont work for me.

 

Playing with coolie hat is disgusting and no option for longer multiplayer.

 

I turn my back to pointtracking and try a fully new method. Headtracking with accelereometer /gyroscope. Also known as EdTRacker.

This gadget uses a own chip (arduino pro micro) which reduce CPU Load for tracking. Low cost like DYI  IR Tracker.

Several Edtracker User exist for IL2. Its compatible. Many build guides. 

I will report if this work.

Edited October 20, 2020 by Cingan

[No_85_Gramps]

Not sure if this is the fix you are looking for, but with opentrack you need to make sure the pitch max output value is set to 180. No problems looking straight up or down here.

[JohnB6701]

I have tried the current.map fix mentioned above, but it didn't work for me. I find that FaceTrackNoir's "peek" function is so useful in IL 2, and I prefer it generally to OpenTrack.

 

One thing I did discover was that having  the ROLL axis enable with very small settings stopped the "flickering" when looking up more than 90 degrees. However the sudden "flick" back 180 degrees remains. Such a shame....

 

Has anyone come across another fix as yet ?

 

Many thanks

john in Sunny Carnarvon - Western Australia.

[Taiko]

On 8/15/2018 at 8:55 PM, J2_Bidu said:

I had the same problem in Rise of Flight. The solution here is similar, but somewhat more imperfect.

 

You can edit the current.map file that is located in the game \data\input directory, and paste the following over the default values.

 

[bc_head_pitch]

data_row0 = -2.000000, -1.960000, -1.920000, -1.880000, -1.840000, -1.800000, -1.760000, -1.720000, -1.680000, -1.640000;
data_row1 = -1.600000, -1.540000, -1.500000, -1.460000, -1.420000, -1.380000, -1.340000, -1.300000, -1.260000, -1.220000;
data_row2 = -1.180000, -1.140000, -1.100000, -1.060000, -1.020000, -0.980000, -0.940000, -0.900000, -0.860000, -0.820000;
data_row3 = -0.780000, -0.740000, -0.700000, -0.660000, -0.620000, -0.580000, -0.540000, -0.500000, -0.460000, -0.420000;
data_row4 = -0.380000, -0.340000, -0.300000, -0.260000, -0.220000, -0.180000, -0.140000, -0.100000, -0.060000, -0.020000;
data_row5 = 0.000000, 0.020000, 0.040000, 0.060000, 0.080000, 0.100000, 0.120000, 0.140000, 0.160000, 0.180000;
data_row6 = 0.200000, 0.220000, 0.240000, 0.260000, 0.280000, 0.300000, 0.320000, 0.340000, 0.360000, 0.380000;
data_row7 = 0.400000, 0.420000, 0.440000, 0.460000, 0.480000, 0.500000, 0.520000, 0.540000, 0.560000, 0.580000;
data_row8 = 0.600000, 0.620000, 0.640000, 0.660000, 0.680000, 0.700000, 0.720000, 0.740000, 0.760000, 0.780000;
data_row9 = 0.800000, 0.820000, 0.840000, 0.860000, 0.880000, 0.900000, 0.920000, 0.940000, 0.960000, 0.980000;
data_endrow = 1.000000

 

 

This seems to do the trick. So why imperfect? Well, apparently there's no way to prevent the game overriding these with the default values again but by marking the said file as read-only. This will prevent you from changing the controls in game. And will get you a couple error messages.

 

Best solution I've got so far. I needed a quick fix.

 

Hi guys, i looking for the solution. I combine the quote and i limit the Pitch up to 90º on facetrackir and it runs ok, not the best fix but is playable. Sorry for my english. 

Edited August 24, 2022 by Reitug