Ivandrov

It's just grabbing coordinates and elevation of targets off of the F10 map using the Lalt + click and inputting those values into each pylon in PP mode.

I should say that fiddling with the DLINK page doesn't seem to actually do anything either. It's just a word change in the page with no obvious effect. What are you not seeing?

No, the fiddling with the DED pages happens regardless. The outcome of waiting for GPS SYSTEM vs just switching on MIDS immediately is the same. Datalink information shows up on the HSD and the DLINK page says GPS time is off with a coarse sync. Good catch on the time jumping forward in the F-16 when it switches over. But the original point still stands. 2 minutes 10 seconds is not the 60 seconds that was in the changelog.

I wasn't able to replicate the need to do the procedure in the changelog. It takes 3 minutes for the TIME page to go to GPS SYSTEM and not 60 seconds. I can also turn both GPS and MIDS on at the same time with seemingly no consequences, so I am unsure of what the purpose of the changelog procedure is. I can then go to DLINK and press a number key to switch GPS time on and the Sync goes to fine.

Yeah, PP would completlely bypass anything that could possibly be wrong with the Jet, as you are directly inserting coordinates and elevation into the JDAM. The JDAM has its own GPS/INS systems.

The Hornet grabs elevation data from a terrain database. The Navy specifically has one for precision targeting, but I don't remember what it is called. It can probably get elevation data from several other sources as well. Including GPS. I tried making my baro hideously wrong and still got a perfect hit. Both TPOD des and Radar des.

Supplying two Tacviews, here. One where I used mostly the R-73, and one where I used mostly the R-27R. Eight missiles shot, Eight A-10's dead in each Tacview. The A-10s were stripped of countermeasures, and gun ammo. If you can prove that it matters whether these A-10s are human or AI, then that's something we can explore. But, otherwise, this all seems pretty normal to me. Tacview-20240213-233641-DCS.zip.acmi Tacview-20240213-232850-DCS.zip.acmi

If it's a problem with the A-10 specifically, why wouldn't it be the same? Are you saying it is a problem with the A-10? Or that it matters who or what is controlling it?

Just do it against AI, you can setup a mission in the mission editor, remove countermeasures, and make sure you get good shots on them before you fire the missiles. I can also do it myself, tomorrow, and post the results.

That was an incredibly terrible shot, it wouldn't have guided onto any plane. You're not convincing anyone that there is a problem with the A-10 here if you keep leaving in all of these variables that explain the reasons why your missiles miss. Try isolating things in a test environment, shoot against an A10 with no countermeasures, and with good leading shots.

Radar lock may have been maintained, did the seeker in the missile even have a chance to find the reflection from that close and off-angle? There are severe problems with weapons employment envelope and use of countermeasures in the two cases you just posted.

Well, even if you say it seems like there was no desync. I've seen plenty of cases of proximity fuzes seemingly not firing against a variety of aircraft in multiplayer. Even if everything else seems normal. That seems to be what happened with the first missile. It looks like another was obscured and hit a hill, several look like they were fired without a valid track, whether that is pilot error in aircraft procedures, or tactics of firing against something so low to the ground, I can't say. Point blank firing missiles is also a problem because it takes time for missiles to accelerate enough, for sufficient airflow to be established for manuevering. They have very small airfoil surfaces optimized for manuevering at much higher speeds. As people have said before, the lack of afterburner in the A-10 makes a huge difference for the effectiveness of IR missiles against it. Flares are highly effective on it, and helicopters in-game due to low IR output from the engines. You have too many variables going on here in this track to be able to confidently say whether you are encountering a bug or not. For what it is worth, I've flown the A-10 for a very long time, and I've definitely been hit by SARH and IR missiles. I've also shot down a few A-10's as Redfor. Never felt like there was anything unusual going on other then what I've explained above.

Any update on this?

Same issue was reported here as well.

I tried this on both Persian Gulf and Cacusus. I have a group of 4 BTR's out next to the airfield, they always seem to suddenly pop-in into the radar image at exactly 10 nm away. This seems strange to me when the airfield equipment that is of roughly similar size is showing up brightly on the image from at least double the distance. This also means it is incredibly easy to spot targets as you have an immediate before and after image as soon as you cross the 10 nm mark. Video and track attached. Weird A2G radar behavior.miz.trk