Jump to content

Help needed on how to setup Track/IR, so as NOT to fight it in 109?


Recommended Posts

Like the title says, Im having trouble setting up the track IR correctly in the 109K. It works pretty much perfectly in the Spitfire and the P51, which is probably due to the fact that they don't have a metal plate directly over the pilots head.

 

Im actually fighting the Track IR more than I am an opponent in battle.

 

Is there a way to set up my head position in the plane, so I can look up without ducking forward first?

 

I use the Zoom function a lot, it's bound to one of the hats on my throttle. However no matter the Zoom setting my head is always located directly beneath the head plate.

 

Some help with this would be greatly beneficial and would allow me to actually track an opponent during a fight, instead of just guessing where he might end up being.

 

So, help? Please? :)

Current specs: Windows 10 Home 64bit, i5-9600K @ 3.7 Ghz, 32GB DDR4 RAM, 1TB Samsung EVO 860 M.2 SSD, GAINWARD RTX2060 6GB, Oculus Rift S, MS FFB2 Sidewinder + Warthog Throttle Quadrant, Saitek Pro rudder pedals.

Link to comment
Share on other sites

RCTRL+RSHFT+NUM2/NUM8 maybe for UP&DOWN ?

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Asus 1080ti EK-waterblock - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus PG278Q 27" QHD Gsync 144Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Link to comment
Share on other sites

RCTRL+RSHFT+NUM2/NUM8 maybe for UP&DOWN ?

 

What does that do? Does it move the in-game virtual head forwards and backwards?


Edited by OnlyforDCS

Current specs: Windows 10 Home 64bit, i5-9600K @ 3.7 Ghz, 32GB DDR4 RAM, 1TB Samsung EVO 860 M.2 SSD, GAINWARD RTX2060 6GB, Oculus Rift S, MS FFB2 Sidewinder + Warthog Throttle Quadrant, Saitek Pro rudder pedals.

Link to comment
Share on other sites

I use deadzones for all axes to avoid the head translation that's happening when looking up/dn. Anyway, the head movement in 109 is.. different than in any other module. I hope they'll fix that too.

Specs:

Asus Z97 PRO Gamer, i7 4790K@4.6GHz, 4x8GB Kingston @2400MHz 11-13-14-32, Titan X, Creative X-Fi, 128+2x250GB SSDs, VPC T50 Throttle + G940, MFG Crosswinds, TrackIR 5 w/ pro clip, JetSeat, Win10 Pro 64-bit, Oculus Rift, 27"@1920x1080

 

Settings:

2.1.x - Textures:High Terrain:High Civ.Traffic:Off Water:High VisRan:Low Heatblur:High Shadows:High Res:1920x1080 RoC:1024 MSAA:4x AF:16x HDR:OFF DefS: ON GCI: ON DoF:Off Lens: OFF C/G:390m Trees:1500m R:max Gamma: 1.5

 

Link to comment
Share on other sites

I too hate that friggin plate. I have had many a frustrating fight because of it. What I do is when I want to look up and back behind me in that annoying hot spot that seems to be my main issue is I zoom out ( I mean way out) until I can see everything around that plate and the plate itself becomes much less of a problem. I saw that there were a lot of guys on Youtube doing this with great success and they were shooting planes out of the sky like swatting flies so I adapted that tactic.

It feels a bit unorthodox to me but I have had good luck with it.

Link to comment
Share on other sites

there's a simple solution:

 

put your TrackIR in pause mode, then put your head/view forward a bit with the mouse or the key combos, save that position and enable TrackIR again.

 

When you look up, the plate will obviously be more behind you and not above you anymore.

Link to comment
Share on other sites

What does that do? Does it move the in-game virtual head forwards and backwards?

 

 

It moves the pilot with those keys, up down left right - Numpad-cross

 

 

Gesendet von iPhone mit Tapatalk

  • Like 1

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Asus 1080ti EK-waterblock - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus PG278Q 27" QHD Gsync 144Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Link to comment
Share on other sites

Numpad-cross

 

Numpad * Forward

Numpad - Back

 

Thank you, thats what I was looking for!


Edited by OnlyforDCS

Current specs: Windows 10 Home 64bit, i5-9600K @ 3.7 Ghz, 32GB DDR4 RAM, 1TB Samsung EVO 860 M.2 SSD, GAINWARD RTX2060 6GB, Oculus Rift S, MS FFB2 Sidewinder + Warthog Throttle Quadrant, Saitek Pro rudder pedals.

Link to comment
Share on other sites

Help needed on how to setup Track/IR, so as NOT to fight it in 109?

 

I have zooms / and * as well as the up down on my throttle's thumb with any aircraft.

 

Glad you found your solution

 

 

Gesendet von iPhone mit Tapatalk

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Asus 1080ti EK-waterblock - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus PG278Q 27" QHD Gsync 144Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Link to comment
Share on other sites

the only way to dodge the roof is to move forward in trackir with a mirrored steep V curve in the Pitch axis for lean, and to have a half steep non mirrored asymmetrical Y axis for look up.

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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