Jump to content

Recommended Posts

After launching an aim120c with TWS & RWS immediately the opponent aircraft receives sound warning for missile. This is not correct. The missile is supposed to be pitbull first ! We need a Hotfix for that

Link to post
Share on other sites

In other news, at 1.16mach @40,000ft I looked up a Mig in TWS and fired a 120c @50nm way and got a hit!! When did they change up the 120c range poor Mig didn't even get a shot off 120c hit home and he was still 18nm away from me

Acer Predator 500 Laptop i7 8750 @ 3.9MHz /16GB DD4 / GTX1070 / 256 SSD

 

Youtube https://www.youtube.com/channel/UC3FtEcJlj_34i3IVqx6pE_w?view_as=subscriber

Link to post
Share on other sites
In other news, at 1.16mach @40,000ft I looked up a Mig in TWS and fired a 120c @50nm way and got a hit!! When did they change up the 120c range poor Mig didn't even get a shot off 120c hit home and he was still 18nm away from me

 

Since a couple of patches ago when they introduced a new lofting logic which increased dramatically amraam range, especially on high altitude, high speed shots.

 

Supposedly the amraam will be completed with new AFM based on CFD and improved logic in June, after that the same work will be done iteratively in all missiles. I hope the r77 and r27 receive some love before 2020 ends so everybody is happier.

Link to post
Share on other sites
the new missile guidance API cannot come soon enough...

 

What has this got to do with the issue OP reported?

i7-4770k | EVGA GTX 980 SC | 16GB DDR3 | TrackIR 5, TM Warthog HOTAS, Saitek Pro Flight Rudder Pedals

 

DCS: F-16C, F/A-18C, F-14A/B, AV-8B, FC3, A-10C, Black Shark II, UH-1H, F-86F, MiG-21bis, Mirage 2000C, AJS-37, F-5E :pilotfly:

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...