Jump to content

TRACKIR - 6DOF - COCKPITVIEW ANGLE PROBLEM


Recommended Posts

Posted

Hi guys!

 

Whenever I use TrackIR 5 with Z axis on zoomview (either with 6dof addon or not) with Lock On FC2, the game does not use the custom View Angle I put in the "SnapViewDefault.lua".

 

When I center TrackIR (default key F12) I would like to have a slightly zoomed out position, but no matter what number I put in the SnapViewDefault.lua file, the view angle for my F-15 changes only, when I don't use TrackIR.

 

Here is what I mean exactly:

 

Snap[8][13]["viewAngle"] = 88

 

When I change the value in this line, the viewAngle ingame changes only if I don't use TrackIR. When I do use it, then I get an more "zoomed in" Cockpit ViewAngle, when I center my TrackIR.

 

What I don't understand, is that the other values for the different cockpit angles, that are also contained in the SnapViewDefault.lua (see below), actually DO WORK, even when I use TrackIR.

 

For example:

 

Snap[8][13]["vAngle"] = -12

Snap[8][13]["hAngle"] = 0

 

When I change those values I can see the effects ingame, even with TrackIR in use.

Only the "Snap[8][13]["viewAngle"] = 88" has no effect for some reason.

 

I realize that I can zoom with my TrackIR, but what I would like to have is that the ViewAngle setting I put in the LUA file is used, when I center the TrackIR.

 

Does anyone know, how I could get this to work?

  • CPU : Intel i7 8700k@5.0ghz cooled by Noctua NH-D15 / Motherboard:Asorck Z370 Taichi / RAM: 32GB GSkill TridentZ @3600mhz / SSD: 500GB Nvme Samsung 970 evo+1 TB Sabrent Nvme M2 / GPU:Asus Strix OC 2080TI / Monitor: LG 34KG950F Ultrawide / Trackir 5 proclip/ VIRPIL CM2 BASE + CM2 GRIP + F148 GRIP + 200M EXTENSION /VKB T-Rudder MKIV rudder /Case: Fractal Design R6 Define black

Posted

Not near my gaming rig at the moment and I fly the A10 and fiddled with those settings, but hopefully I can shed some info of what I have found in my settings.

 

I run 3 monitors and the default "zoom" with TrackIR was too close. I too found that playing with the viewAngles had no effect on the "default" zoom location. What I found to work for me was to adjust the FOV setting for the A10 in the view.lua file. I'm sorry I can't remember the exact name of the setting, but it's value was something like '= {20, 140}'. Changing the latter value to something larger helped me zoom out some, think I have mine set at {20, 200} at the moment. I hope you can get some help from this. Good Luck!

~Thump.

 

Computer Specs:

i7-6700K@4.00GHz, 32GB, 850 EVO 1TB, GTX 1080 Ti, Samsung Odyssey VR

[sIGPIC][/sIGPIC]

Posted

I hope someone will ge me soon an answer on how to fix this issue, I mean there's a lot of you out there who use trackir and 6DOF ... am I the only one having this problem?...

  • CPU : Intel i7 8700k@5.0ghz cooled by Noctua NH-D15 / Motherboard:Asorck Z370 Taichi / RAM: 32GB GSkill TridentZ @3600mhz / SSD: 500GB Nvme Samsung 970 evo+1 TB Sabrent Nvme M2 / GPU:Asus Strix OC 2080TI / Monitor: LG 34KG950F Ultrawide / Trackir 5 proclip/ VIRPIL CM2 BASE + CM2 GRIP + F148 GRIP + 200M EXTENSION /VKB T-Rudder MKIV rudder /Case: Fractal Design R6 Define black

Posted

What you experience is absolute normal as you have set the zoom to your Headtracker Z-axis.

 

"viewAngle" and "Zoom View" are just different terms for the same thing called FOV -Field of View.

 

The solution would be to un-assign your Z-axis from "Zoom View"(so you aren't changing it immediately when in cockpit ) and assign the Z-axis better to "Absolute Longitude Shift Camera View"

 

I don't have FC2 installed and I don't know if "Absolute Longitude Shift Camera View" is fully supported.

- "Zoom View" may looks similar to moving your head forward in the first place but is technically a diffrent thing.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...