oho Posted September 10, 2019 Posted September 10, 2019 I have a loadout of 4 MavF. I use a waypoint to slew the TGP on a target via SA page. I Designate the target with the TGP and the Mavericks are slewing to it I can lock on the Targets when in range and fire. I have no Problem doing that with maverick 1 and 2. With maverick 3 and 4 the mav is not slewing to the TGP Location but only near to it. Please check if you can reproduce it.
Greyman Posted September 10, 2019 Posted September 10, 2019 I experienced something like this last night and eventually discovered that pressing the undesignate button freed the cursor up.
Darcwaynard Posted September 10, 2019 Posted September 10, 2019 I ran a mission this morning and noticed that once I press target designate the mav slews to the target fine but it won't lock on properly until I press the press un-designate/nws. Not sure if this is proper behavior but it makes sense in that the mav is being caged to the TGP which is overriding its ability to lock on it's own. This applies to all 4 mavs that I fired. Sent from my SM-A530W using Tapatalk [sIGPIC][/sIGPIC] Amd Fx 8350 4.3 GHz - MSi Gtx 1060 6gb - 16gb DDR3 A-10C - AV8B - F-5E - Mig-21 - FC3 - CA - UH-1H - Black Shark - AJ3-37 - M-2000C - F-16C Viper - F-86F - Spitfire - Fw-190 - F/A-18C - F-14 - Normandy - NTTR - Persian Gulf
ED Team BIGNEWY Posted September 10, 2019 ED Team Posted September 10, 2019 We do have this and is fixed internally, I over looked it this morning. Should be in next open beta patch. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Harker Posted September 10, 2019 Posted September 10, 2019 I ran a mission this morning and noticed that once I press target designate the mav slews to the target fine but it won't lock on properly until I press the press un-designate/nws. Not sure if this is proper behavior but it makes sense in that the mav is being caged to the TGP which is overriding its ability to lock on it's own. This applies to all 4 mavs that I fired. Sent from my SM-A530W using Tapatalk Noticed it too. For me, as long as the IMAV is slaved to the TGP, it very rapidly switches from an unlocked state to a locked one and back. You can see that both on the IMAV page and on the HUD, where an X rapidly appears and disappears over the weapon's name. It's still possible to launch, but the behavior is odd. EDIT: I posted 1 minute after BN, didn't see his answer in time. Thanks! 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
Recommended Posts