Rhinozherous Posted July 10, 2019 Posted July 10, 2019 Hello! I am quite untrained in air to air and want to change this. I set up a mission with some Mig 21 for training purposes and tried to lock it on radar. Situation is flightlevel 220 for me and the mig, about 100 nm away. I trie to get a lock all the way down to dogfight range. But the mig is just appearing for very short times on the scope. Not long enough to get a lock. I am in TWS mode, trie different ranges, 2bar and 4bar search and no crazy up or down looking with the radar. I understand how the radar beam works, the cone shape and so on, but do you guys have tips and tricks for me on this topic? Thanks! i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only DCS - XP12 - MSFS2020
Jak525 Posted July 11, 2019 Posted July 11, 2019 (edited) Potentially a low closure rate, is beaming you, or (this is probably it) your trackfile/contact aging setting is very low. Head to the DATA sublevel; the top right corner gives you an option to set in seconds. Try the maximum of 32. If the Mig is the only contact around, use Sensor Control Switch right to activate Automatic Acquisition (AACQ); be sure to be in A/A master mode for this. AACQ will enter Single Target Track (lock) as soon as it sees something pop up. P.S. Track While Scan isn't in yet. You probably mean Range While Search (RWS) with Latent Track While Scan boxed; RWS processes trackfiles just like TWS, it just doesn't support AMRAAM guidance nor does it limit the scan volume. Edited July 11, 2019 by Jak525
Preendog Posted July 11, 2019 Posted July 11, 2019 The key is to learn where the contact is first, then set your radar to scan at the correct angle and elevation. Then you might pick up a fighter sized target as far away as 20 miles. I find F10 is really handy for this.
Rhinozherous Posted July 11, 2019 Author Posted July 11, 2019 Potentially a low closure rate, is beaming you, or (this is probably it) your trackfile/contact aging setting is very low. Head to the DATA sublevel; the top right corner gives you an option to set in seconds. Try the maximum of 32. If the Mig is the only contact around, use Sensor Control Switch right to activate Automatic Acquisition (AACQ); be sure to be in A/A master mode for this. AACQ will enter Single Target Track (lock) as soon as it sees something pop up. P.S. Track While Scan isn't in yet. You probably mean Range While Search (RWS) with Latent Track While Scan boxed; RWS processes trackfiles just like TWS, it just doesn't support AMRAAM guidance nor does it limit the scan volume. Thank you, didnt thought about the aging settings, will trie! Yeah, I ment RWS, it shines thru that I have a lot of training to do :) The key is to learn where the contact is first, then set your radar to scan at the correct angle and elevation. Then you might pick up a fighter sized target as far away as 20 miles. I find F10 is really handy for this. Thanks! i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only DCS - XP12 - MSFS2020
Rhinozherous Posted July 11, 2019 Author Posted July 11, 2019 There is one more question I have tough... When in one of the ACM modes, like boresight or vertical search, selecting sensor switch right should go back to search, or RWS I think. But it does nothing and I have to deselect aa mode and activate again to find me back in normal search mode. Which is a bit clunky to use. i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only DCS - XP12 - MSFS2020
Jak525 Posted July 11, 2019 Posted July 11, 2019 There is one more question I have tough... When in one of the ACM modes, like boresight or vertical search, selecting sensor switch right should go back to search, or RWS I think. But it does nothing and I have to deselect aa mode and activate again to find me back in normal search mode. Which is a bit clunky to use.Negative (this is an error in the DCS manual confirmed by Wags). ACM mode is exited via the Undesignate button (pinky button on stick). Here's a current resource https://wiki.hoggitworld.com/view/F/A-18C
majapahit Posted July 11, 2019 Posted July 11, 2019 Have (2) button(s) for range, have (2) button(s) for Radar elevation Then you're ready for everything coming at you. BTW the RL F15/FA18C " .. elevation Switch is a potentiometer actuated by a switch on a centering spring, so more travel would be faster movement, but, it will center back to null when released. This is -15 stuff of course, I’m going to bet -18 would be similar but don’t know that to be fact" Radar elevation centers back to the middle. WTH? | VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |
deadpool Posted July 11, 2019 Posted July 11, 2019 The key is to learn where the contact is first, then set your radar to scan at the correct angle and elevation. Then you might pick up a fighter sized target as far away as 20 miles. I find F10 is really handy for this. Is this really a correct range for the FA18 radar to pick up a hot target? 20 nm? Sounds to me like you should have picked it up ages ago! Lincoln said: “Nearly all men can stand adversity, but if you want to test a man's character, give him power." Do not expect a reply to any questions, 30.06.2021 - Silenced by Nineline
Rhinozherous Posted July 11, 2019 Author Posted July 11, 2019 Negative (this is an error in the DCS manual confirmed by Wags). ACM mode is exited via the Undesignate button (pinky button on stick). Here's a current resource https://wiki.hoggitworld.com/view/F/A-18C Good to know! Thank you very much! i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only DCS - XP12 - MSFS2020
steak1606688831 Posted July 11, 2019 Posted July 11, 2019 Is this really a correct range for the FA18 radar to pick up a hot target? 20 nm? Sounds to me like you should have picked it up ages ago! You pick up a fighter at about 80nm.
Lordzarj Posted July 11, 2019 Posted July 11, 2019 It depends on the size of the the fighter doesn't it? The Mig-21 is pretty small, a Mig-31 should be picked up at a longer range.
DeltaMike Posted July 11, 2019 Posted July 11, 2019 It's still a little buggy, sometimes you have to restart the mission to get it working right Assuming it's working, there are two major issues and one minor to consider 1. Beam geometry 2. Refresh rate 3. Pulse repetition frequency If you're scanning say 80 miles out you have to make sure nobody slips in under your beam. You may be scanning from sea level to angels 45 at 80nm, but may only be covering 20-21 10 miles out. Very easy for someone to slip in under your beam. Put the TDC cursor where you think the target might be (bogey dopes are useful here) and make sure you have it bracketed altitutude-wise using your radar elevation control. If you're in LTWS with a multi-bar scan, it takes forever to refresh the image. Twice as long if you have PRF in interleave mode, looking for a guy who is 60 miles out. Narrowing the azimuth and/or bars will help you pick up bandits that are moving and changing aspect frequently. 4-bar 80 degrees works pretty well in LTWS; for a higher volume search consider flipping into RWS. Finally, picking either PRF hi or PRF med can help. PRF hi is useful for hot aspect targets a long way away. PRF med gives you a little better ranging information and is helpful if the target is changing aspect, flanking, or running away at something close to your speed. But only useful for somewhat closer ranges, like 20 or 30nm. Either way you'll pick em up faster than if you leave it in interleave mode Even then it can be literally impossible to see somebody who is either notching you, or doesn't have closure Ryzen 5600X (stock), GBX570, 32Gb RAM, AMD 6900XT (reference), G2, WInwing Orion HOTAS, T-flight rudder
Recommended Posts