Santi871 Posted September 8, 2019 Posted September 8, 2019 The "radar contribution" circle is missing from the HAFU tracks. IDK if its just a WIP issue or a missing piece. You can think it's linked to this cue?
Beamscanner Posted September 9, 2019 Posted September 9, 2019 You can think it's linked to this cue? I dont think it has anything to do with that.. It's just on the DDI HAFUs. Hopefully ED has material on it.
Nagilem Posted September 10, 2019 Posted September 10, 2019 So after reading all of this, I think what is being said from a put into practice list is - 1. radar acquires targets as radar bricks or HAFUs if donated 2. One can use TDC press to L&S one target, and DT2 a second target giving some info 3. As targets approach, TDC Depress on either target OR SCS toward the radar ddi should move the L&S contact to STT 4. Employ weapons and SCS right to AACQ the DT2 target Does this sound correct? In all of the talk between real and in sim, I am trying to understand what is available and how to employ. What I have found so far is AACQ does not priority lock the L&S contact, so I end up having something random locked and having to use the cursor with TDC press to STT the specific target I had L&S (or DT2) soft locked. :pilotfly: Specs: I9-9900k; ROG Strix RTX 2080ti; Valve Index HMD; 32GB DDR4 3200 Ram; Samsung 970 EVO 1TB SSD; TM Warthog with pedals, 3 TM MFDs
Harker Posted September 10, 2019 Posted September 10, 2019 2. One can use TDC press to L&S one target, and DT2 a second target giving some info You can also place the TDC over a third contact, making it TUC (Target Under Cursor) and also get info on that. You just lose the info if you move the TDC away. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Nagilem Posted September 10, 2019 Posted September 10, 2019 @harker - ok good! I think I've seen that so far. My big question is how should one lock up L&S or DT2 targets IN DCS? Should the SCS right (or left depending on ddi) priority lock the L&S Target? Should a second push move the lock to the DT2 target? Sorry if this is detailed earlier. I saw the discussion, but the jumble of real vs DCS is confusing me... :pilotfly: Specs: I9-9900k; ROG Strix RTX 2080ti; Valve Index HMD; 32GB DDR4 3200 Ram; Samsung 970 EVO 1TB SSD; TM Warthog with pedals, 3 TM MFDs
Harker Posted September 10, 2019 Posted September 10, 2019 @harker - ok good! I think I've seen that so far. My big question is how should one lock up L&S or DT2 targets IN DCS? Should the SCS right (or left depending on ddi) priority lock the L&S Target? Should a second push move the lock to the DT2 target? Sorry if this is detailed earlier. I saw the discussion, but the jumble of real vs DCS is confusing me...Right now, there isn't a reliable way to immediately lock either the L&S or DT2 target in DCS. SCS Right (AACQ) sometimes locks the L&S, sometimes it doesn't. NWS doesn't switch between the L&S and the DT2 yet. We're missing a lot of functionality. The only way to reliably lock the targets is to go with the TDC and either hit TDC Depress until you get in STT or go with the TDC and hit SCS Right. SCS Right works (at least I think, it's worked for me), but only for the TUC. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Nagilem Posted September 10, 2019 Posted September 10, 2019 @Harker - Excellent sir... Thanks for the concise and simple clarification summary. I'll give it a try! :pilotfly: Specs: I9-9900k; ROG Strix RTX 2080ti; Valve Index HMD; 32GB DDR4 3200 Ram; Samsung 970 EVO 1TB SSD; TM Warthog with pedals, 3 TM MFDs
Boogieman Posted September 10, 2019 Posted September 10, 2019 Just a quick aside here, but has anyone else noticed that LACQ mode only seems to lock targets when used off-boresight? Whenever I try to use it via the HUD nothing happens, but if I use it to lock an off-bore target with JHMCS it works fine..?
Recommended Posts