VC Posted April 18, 2019 Posted April 18, 2019 When cranking in STT, is there any symbology to help me tell when I'm nearing radar gimbal limits? I've been looking at the TID and I can estimate but there's nothing obvious to help me optimise, and depending on the scan range the locked target can go off the edge of the screen in a hard crank. Plus looking down like that while violently weaving and trying to shoot back in between isn't ideal. Any tips for this scenario? VC =X51= Squadron is recruiting! X51 website: https://x51squadron.com/ Join our Discord: https://discord.gg/d9JtFY4
viper2097 Posted April 18, 2019 Posted April 18, 2019 Isn't the VDI showing the limits? Steam user - Youtube I am for quality over quantity in DCS modules
Mr_sukebe Posted April 18, 2019 Posted April 18, 2019 I asked this recently. The concensus was upto 60 to either side, though clearly you’ll need to manually guesstimate that. 7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat
VC Posted April 18, 2019 Author Posted April 18, 2019 (edited) Yes, I remember your thread but knowing it's 60 doesn't help you visually estimate 60 on a rectangular TID with no additional markings. Can someone confirm if the VDI shows it and maybe post a screenshot of the symbology? Edited April 18, 2019 by VC VC =X51= Squadron is recruiting! X51 website: https://x51squadron.com/ Join our Discord: https://discord.gg/d9JtFY4
viper2097 Posted April 18, 2019 Posted April 18, 2019 I was thinking about the ASE (allowable steering arrow) indication of the VDI, but I gues this will not match the gimball limits... So far, unfortuantely, the whole VDI symbology for weapons employment is still missing in the manual, and also the NATOPS does not really say that much about it... Steam user - Youtube I am for quality over quantity in DCS modules
Mr_sukebe Posted April 18, 2019 Posted April 18, 2019 I’m using the compass. Check the target heading before firing, fire and then fly 45-60 degrees on the crank. A bit crude, but it works fine. 7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat
WindyTX Posted April 18, 2019 Posted April 18, 2019 Agreed you need to use the compass initially but after that the angle will build. The only way to do it properly is to have your Rio talk you through it from the back. A person not Jester obviously it's a shame the 65 azimuth limit lines are not still available in STT. Sent from my ONEPLUS A6013 using Tapatalk I7 3930 4.2GHz ( Hyperthreading Off), GTX1080, 16 GB ddr3 Hotas Warthog Saiteck Combat Pedals HTC Vive, Oculus CV1. GTX 1080 Has its uses
104th_Maverick Posted April 18, 2019 Posted April 18, 2019 I asked this recently. The concensus was upto 60 to either side, though clearly you’ll need to manually guesstimate that. Correct AFAIK there is no visual reference to show you the gimbal limit, you have to manually track your offset. [sIGPIC][/sIGPIC] 104th Phoenix Wing Commander / Total Poser / Elitist / Hero / Chad www.104thPhoenix.com www.facebook.com/104thPhoenix My YouTube Channel
VC Posted April 18, 2019 Author Posted April 18, 2019 Fair enough, I guess you don't always have to crank to the last degree :) I'll practice, maybe see if I can find a scratch or screw on the TDI to act as a quick reference. VC =X51= Squadron is recruiting! X51 website: https://x51squadron.com/ Join our Discord: https://discord.gg/d9JtFY4
Recommended Posts