REDEYE_CVW-66 Posted January 13, 2020 Posted January 13, 2020 Flying on mission and seeing contacts on the scope, it is really frustrating to spam 'lock enemy contact' only to hear 'unable' dozens of times until a lock can be made. While I understand that has to do with the parameters needed for Jester, he should be able to understand a simple message like "Lock up the first enemy contact you get!" without having to navigate the Jester wheel and spam the command continously. Yesterday I was in a MP mission with multiple red contacts on our nose. Awacs was blabbering and we were deconflicting with a second flight of Tomcats on SRS. It has a Jester wheel nightmare. Perhaps it could be under 'contract' as this could be agreed between the pilot and RIO given the specific mission. Hope to see something to this effect implemented.
Mr. Big.Biggs Posted January 13, 2020 Posted January 13, 2020 Yep I had a bogie 45 miles out hot on my nose and jester kept locking a target 60+ miles off my 2 o’clock flanking Right with a friendly in pursuit. Had no choice but to break off and ended up taking a missile up the ass. I got out, jester wasn’t so lucky. How do I explain to his digital family that his incompetence got him killed and not my desktop?? I9 (5Ghz turbo)2080ti 64Gb 3200 ram. 3 drives. A sata 2tb storage and 2 M.2 drives. 1 is 1tb, 1 is 500gb. Valve Index, Virpil t50 cm2 stick, t50 base and v3 throttle w mini stick. MFG crosswind pedals.
draconus Posted January 13, 2020 Posted January 13, 2020 Two things: 1. Make sure the contact is confirmed by Jester/WCS as enemy to use "lock enemy". If not use "lock target" instead. 2. Make sure you have actual radar contacts - not data link pointers. 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