Jump to content

Recommended Posts

Posted
Autolase doesn't turn off at TTI = 0, it waits a good few seconds (5-10maybe) after timeout.

 

 

 

The Point track gates are WIP ATM afaik, because we are still waiting on the flir renderer. All the pod sees right now is 'an object' without any info on its size.

Autolase already does that? I haven't had much time to check, I mostly went off of other comments in the forums, my bad if that's the case.

The point track gates don't require the new FLIR renderer though. They already work correctly in the A-10C, F-14 and JF-17. They just adapt to the shape of a vehicle or building instead of a contrast difference and they actually do it quite well, for the most part, so the functionality is there. Now, if you mean that they're delaying that feature on the Hornet in order to have it work with the new FLIR outright, instead of "cheating" by tracking game objects, yeah, maybe.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

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

Posted
Autolase already does that? I haven't had much time to check, I mostly went off of other comments in the forums, my bad if that's the case.

The point track gates don't require the new FLIR renderer though. They already work correctly in the A-10C, F-14 and JF-17. They just adapt to the shape of a vehicle or building instead of a contrast difference and they actually do it quite well, for the most part, so the functionality is there. Now, if you mean that they're delaying that feature on the Hornet in order to have it work with the new FLIR outright, instead of "cheating" by tracking game objects, yeah, maybe.

 

It doesn't for me. For me it stops lasing at about 1 or 2 seconds after TTI reaches 0, which 70% of the times makes the bomb miss, so not very well simulated IMHO.

Stay safe

Posted
I would uncage the first mav then switch back to the TGP to slave the mav (which slaves each subsequent mav) to whatever point you designate with the TGP. If the maverick didn't like where it was looking I would continue to designate with the TGP until I acquired a lock.

 

Sent from my SM-A530W using Tapatalk

 

 

Hope that DCS soon fixes the MAV seeker LOS to be congruent with TGP designated target. This futtsing around between MAV and TGP to get a good MAV lock is a royal PIA.

Posted
Hope that DCS soon fixes the MAV seeker LOS to be congruent with TGP designated target. This futtsing around between MAV and TGP to get a good MAV lock is a royal PIA.
Is it possible the seeker slew slew/fidelity is slower on the MAV than the TGP irl? I notice the jitter is much worse if you aren't totally stable while trying to lock up targets. If I'm inbound on target with ALT hold or ATT hold I dont find it too difficult to lock the mav solely from the pod.

 

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

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...