Hobel

yeah and?

I don't remember exactly, but wasn't it the case that pre flare didn't work? Flares that are dropped before the launch of the missle do not exist for the rocket at launch? That's not quite right - there are already games in the aviation sector that simulate chaff very well and, depending on the amount and aspect, can deceive the radar very authentically. The Razbam modules can also react quite plausibly to chaff.

Hopefully the later versions will get more life time, the aim120c in dcs could theoretically fly 80-100nm but is limited by the 100 seconds.

Maybe yes, but look at the scenarios posted here, the missle usually only misses the target by a few metres 10-20m. Which is still good. However, the real missle would explode at the closest possible calculated point before it simply flies past. In a newsletter a new PF logic was mentioned, maybe such an implementation will come to dcs in the future. And fixes the problem we see here.

No, the track radar was not destroyed or damaged by the shrikes, only when I directly shot at it later with the maverick. You can also see in the Youtube video that the destroyed search radar is very far from the track radar (the column of smoke) And as I said, if the search radar is destroyed, the sa2 is basically blind, but first you have to break the lock once.

Okay? What do you expect the actual function to look like? It's basically the same as irl, tgp is soi, you point the tgp at a target and press TMS UP, then a handoff is given to wpn and the maverick tries to lock the target. And that's how it is in dcs. What is not implemented correctly, the general process is exactly as described in the irl documents for the f16. TMS up handoff and TMS up on the wpn have the same precision in the end if done correctly, I have also linked a video how it works. and especially with units that are close to each other at a great distance, problems can arise, why has already been explained. Oh hum, okay nice.

I agree with you about the bugs, but when WPN SOI and the Maverick is fired, I have to do the SOI back to TGP which is another work step I still save and I demonstrated that in the video. with Auto Handoff I DON'T HAVE to do a DMS down for another shot and can immediately search for new targets and lock them. if you don't see the advantage in this, everyone should play the way they like it.

what do you mean? I posted a video that shows exactly the opposite... here the same again only with manual handoff , the procedure takes much longer and I have to switch back to the TGP SOI for each new destination< MAN: 2x TMS UP + 1 DMS down vs AUTO: 1 TMS UP

As I have already said. you can recognize units much better, you can make better fine adjustments with the TGP and you can Lock directly to the right target and transfer everything with the handoff. Try this in the video without switching back to the SOI TGP and hit the right targets. I simply save time here before I constantly switch between WPN and TGP with the SOI.

This is because the closer you get, the smaller the area in which the tracking gate can lock on false targets. this is because the behavior does not change, if units are very close to each other it can still happen that the seeker jumps around between the units that are close to the tracking gate, here in the example it is under 6nm and the seeker jumps around. When I attack a Farp I want to kill all AAA/SAM units first, with the TGP the detection and identification is very fast and if I have the right unit, I can hand it over at the same time. it should also be said that in DCS you can currently only lock targets up to max 9nm with the Maverick D, the documentation shows that it is even possible to Lock at 20nm! at this distance you can only see a small IR dot with the Maverick search head and can no longer see anything and this is exactly where the TGP and the Handoff come into play.

Here is one Option from high alt. this is a clean scenario where i attack a SA-2 position other missions other challenges. but here's a way to take out the SA-2. Use MK37 tape and Direct Mode(Never use loft mode...) to destroy the EWR/search radar, after that the SA-2 is blind, provided that it loses the lock and you fly out of the "track cone". Attacking the Sa-2 track radar with the shrike is a bit tricky, because if the loft is too high, the missle does not see the emitter, "blindspot". If you shoot the shrike too flat, it loses too much energy, in addition, if the SA-2 no longer tracks, the Shrike no longer sees it either. Tacview-20240708-025832-DCS.zip.ac yes of course there is something to it and one wonders why 65kg of explosives do not destroy or at least disable the SA-8, 2 shrike-45 are a bit much for such a light vehicle.

and that's what I meant you hit the notch of 30kts and often come out but the missle can't see you even though it's over 100 vr do you have the track from the mission?

Nice. Upload Tacview?

Do you have tracks of your situations? And which Sam is it exactly? Used correctly, the Shrike-45 is a very good weapon.

I would slightly disagree due to the behaviour of the aim120 in dcs. If you notch and you are relatively fast and hit the missle threshold of 30kts once, then this increases by 2-4+++ times, so you have more room to notch even though you are fast + the advantage that you are not a lame duck. Here are 3 examples: the faster the target, the later the aim120 tracks the target. Tacview-20240702-021923-DCS-notch 50kts .trk.zip.acmi 80kts.acmi Tacview-20240702-021736-DCS-notch 30kts .trk.zip.acmi

Pls upload a track.

for the shots mentioned, 40angels and +1.5 are perfectly adequate. loft was a bit too much otherwise the missle arrives with a good speed in the target area and I shoot here under 40.000feet and only 1.0M. Of course a human would have avoided this missle, but he still has to go on the defensive and give up altitude. just try it out on GS and only shoot from over 40nm, loft is the key here minmum is 15-20° Tacview-20240703-122539-DCS.zip.acmi

Tacview-20240702-170954-DCS-120_Exploit.trk.zip.acmi

wait a minute buildings? so that makes a certain difference, vehicles standing next to each other in DCS and representing a larger IR source is different from a cold house vs. a Hot vehicle. could you show this scene?

Oh, I see, now ty. but you don't have to edit Lua, enter AFN 111.5 for Kobuleti as an example in the editor, so you can then find the airport with the AFN

And I have explained above what the reason for this is the targets are too close to each other the sensor of the maverick has in relation a too large tracking gate therefore it may be that the wrong target was locked, then you try with the TGP a new handoff with TMS RIGHT/UP, I did it on the 2nd try no problems, this behaviour is pointed out in the docs. If you make a good BSGT, it is more than accurate enough(Btw a bus is not suitable for this.) and the targets are not as extremely close together as in your example, the handoff is a good tool Better target detection and fine adjustment with the tgp and then you can do a handoff directly and that works well in dcs . The only point that could be made is that the D cannot track targets that far, the document talks about over 15nm in some cases, but even then we encounter the same characteristics as already discussed

yes other modules like M2000 or F14 still have the "auto blink", because that's how Jammer basically works, so it's intentional for those modules.

yes there have been changes, there should be a kind of warm-up for ED modules, to what extent it fixes the problem I have not yet tested

100feet or even 30m is not much at all - this is what it looks like for the IR seeker at 8nm 3 targets are in the tracking gate so it is not surprising that the wrong one may be locked, if this happens press (TGP SOI) TMS UP or right to start a relock until the correct target is selected. the Handoff and IR Maverick are very cool tools but targets that are close together can cause problems which is not uncommon. other aircraft have the same problem public document https://apps.dtic.mil/sti/tr/pdf/ADA361645.pdf page 136 https://media.defense.gov/2010/Sep/29/2001329786/-1/-1/0/AFD-100929-043.pdf what exactly has changed? on other aircraft the D Maverick behaves in the same way as on the F16 the logic in the F16 makes it the easiest overall

i would recommend only using direct mode with the current implementation, it is in principle better even with lofts. as shown here the controls of the shrike is very limited and if the launch is not optimal the shrike/loft misses. the direct mode has much more margin for error, and is better in almost every situation