Jump to content

Recommended Posts

Posted (edited)

~11.5 miles based on the lua value (18,500m if i remember correctly)

 

 

but, that is because they have not completed the new missile API (missile guidance / realism update). After that it should be roughly 15 seconds to impact.

Edited by Banzaiib
Posted

I hope they also do something about the TTI indicator. Right now, the time is way off especially for medium/long shots. So by the time the TTI hits 15 the target is already destroyed or the missile has went several miles behind it.

i5-8600k @4.9Ghz, 2080ti , 32GB@2666Mhz, 512GB SSD

Posted
I hope they also do something about the TTI indicator. Right now, the time is way off especially for medium/long shots. So by the time the TTI hits 15 the target is already destroyed or the missile has went several miles behind it.

DCS TTI/TTAs and WEZ/DLZ indicators as a whole are quite innacurate

Eagle Enthusiast, Fresco Fan. Patiently waiting for the F-15E. Clicky F-15C when?

HP Z400 Workstation

Intel Xeon W3680 (i7-980X) OC'd to 4.0 GHz, EVGA GTX 1060 6GB SSC Gaming, 24 GB DDR3 RAM, 500GB Crucial MX500 SSD. Thrustmaster T16000M FCS HOTAS, DIY opentrack head-tracking. I upload DCS videos here https://www.youtube.com/channel/UC0-7L3Z5nJ-QUX5M7Dh1pGg

 

Posted
~11.5 miles based on the lua value (18,500m if i remember correctly)

 

 

but, that is because they have not completed the new missile API (missile guidance / realism update). After that it should be roughly 15 seconds to impact.

 

 

Instead of the <5 seconds to impact we have now?

P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria

Posted (edited)
Instead of the <5 seconds to impact we have now?

 

 

11.5 miles (18.5km) at 1500 mph is about 27 seconds...

 

 

11.5 miles at 2000 mph is about 21 seconds

 

 

11.5 miles at 2500 mph is about 17 seconds

 

 

Even at 2500 mph closing speed, it only travels 3.5 miles in 5 seconds... the missile goes active long before that range.

 

 

moral of the story is, you have to be REALLY high up and REALLY fast toward the missile to have it go active less than 5 seconds before impact... if anything, it gives too much warning right now. (unless my math is way off... haven't had coffee yet this morning)

 

 

 

 

Again, this is all with the current functionality we have... this is not how the missile worked IRL. That will come with the new missile API updates confirmed many times by Heatblur.

Edited by Banzaiib
Posted

I thought when TTI hits 16 sec, and start flashing, that's when AIM-54 goes pitbull; is this incorrect?

 

Wonder if I wait longer to extend I'll have higher hit ratio - I usually extend at 16 sec (TTI) and typically launch at <40nm.and end up with roughly 50% hit ratio.

Posted
I thought when TTI hits 16 sec, and start flashing, that's when AIM-54 goes pitbull; is this incorrect?

 

Wonder if I wait longer to extend I'll have higher hit ratio - I usually extend at 16 sec (TTI) and typically launch at <40nm.and end up with roughly 50% hit ratio.

 

 

TTI = 15 or 16 seconds is when it SHOULD go pitbull, but that's not how it works right now because the current missile API cannot support that logic. Right now it's using an older version of the AIM-120 guidance logic and goes pitbull at a specified range 11.5 miles (18.5km)... NOT time to impact. Again, this is confirmed many times by Heatblur.

Posted
TTI = 15 or 16 seconds is when it SHOULD go pitbull, but that's not how it works right now because the current missile API cannot support that logic. Right now it's using an older version of the AIM-120 guidance logic and goes pitbull at a specified range 11.5 miles (18.5km)... NOT time to impact. Again, this is confirmed many times by Heatblur.

 

Ok, thanks for the explanation.

Posted
Title says it all.

 

 

Sent from my iPhone using Tapatalk

 

Theres supposed to be a counter, its not implemented

On the TID theres the TTIP time to impact. thats the countdown on right.

its supposed to start flashing when the Aim54 goes putbill. but thats missing from game now.

Posted
I thought when TTI hits 16 sec, and start flashing, that's when AIM-54 goes pitbull; is this incorrect?

 

Wonder if I wait longer to extend I'll have higher hit ratio - I usually extend at 16 sec (TTI) and typically launch at <40nm.and end up with roughly 50% hit ratio.

 

from my understanding IRL distance isnt what matters - the radar and missile decide. when it flashes its on

however I havent seen the flashing indicating pitbull. an old post by HB said that wasnt in yet

Posted
AIM-120 goes active at 15km

 

is that realistic? what happens if the launch ac loses lock before the missile is 15km?

7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr

Posted
is that realistic? what happens if the launch ac loses lock before the missile is 15km?

 

The missile should go active and proceed in the last known bandit location?

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

Posted
The missile should go active and proceed in the last known bandit location?

Yep, it will turn on its radar, and fly towards the the last predicted bandit position. Unsure if it extrapolates.

Eagle Enthusiast, Fresco Fan. Patiently waiting for the F-15E. Clicky F-15C when?

HP Z400 Workstation

Intel Xeon W3680 (i7-980X) OC'd to 4.0 GHz, EVGA GTX 1060 6GB SSC Gaming, 24 GB DDR3 RAM, 500GB Crucial MX500 SSD. Thrustmaster T16000M FCS HOTAS, DIY opentrack head-tracking. I upload DCS videos here https://www.youtube.com/channel/UC0-7L3Z5nJ-QUX5M7Dh1pGg

 

Posted
It goes active same range as a 120c. 15km or roughly 7nm.

 

And yes, this is a compromise and incorrect behavior until we can utilize the new API to implement proper guidance.

 

thanks for the clarification. any idea on a rough timescale for it?

7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr

  • Recently Browsing   0 members

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