AcroGimp Posted January 11, 2020 Posted January 11, 2020 (edited) I recently took the time to put together Voice Attack profile with 120 commands to have more granular control over where Jester is looking with the radar, specifically the range-at-altitude commands. In testing on a SP development sortie I found he seems to be working OK, in that he does seem to find targets faster than in auto, and I can combine it with directed azimuth as well, i.e., Center-Left, or Right, etc. On MP though it only seems to confuse him - the range markings rarely change, even the azimuth commands are not reliably indicated on the TID repeater. I am not sure however if I recall the range markings changing on the TID repeater when giving him specific range-at-altitude commands during the SP tests. I know we all know a human RIO is the preference but I think we all also know it is not as easy to have a guy in the back office as we would like. So question is, should the range markings change to nearest normal setting (e.g., 50, 100, 200) when we give him a specific spot, or are we commanding a different mode (e.g., Pulse Search, etc.), could be I am changing more than I thought/intended and it is just not presented to me up front as I am expecting, but I would expect to see the scan cone and range markings reflect the combined directions I am giving. Thanks for any clarification. DISCO Edited January 11, 2020 by AcroGimp [sIGPIC][/sIGPIC] A-4E | F-5E | F-14B | F/A-18C | AV-8B NA | UH-1H | FC3 | Yak-52 | KA-50 | Mi-8 | SA-342 i7 8700K | GTX 1070 Ti | 32GB 3000 DDR4 FAA Comm'l/Instrument, FAST Formation Wingman, Yak-52 Owner/Pilot
draconus Posted January 11, 2020 Posted January 11, 2020 When you command Jester to change elevation he just does that - changes radar elevation to cover the altitude at the range you selected. So you should see only angle number and top/bottom altitude changed, not different radar range. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Recommended Posts