Hobel

And that is correct. I spoke of resolution in this context because the system already tries to deliver the best possible Pic in this area and takes the time it needs. It is therefore not possible or sensible to adjust the azimuth. That's why I sent the link where I go into it and add videos to illustrate it. But I will look at the track again and test it myself maybe I have overlooked something

Is that still the case?

several processes interact with each other and influence each other, but I will only go into the BSGT here and show what is currently happening in DCS Here is the same principle only in a very clean environment to make the behavior clear. TGP has vehicle in point track Maverick lock too, I wait until the vehicle is stationary both sensors are now physically aligned with the vehicle and when i press BSGT this alignment should be saved, but as you can see this is not the case, it jumps back to the starting point and this causes the drift. the same happens for you in the track @Carbon715 you can also see in my video how the TD BOX LOS/SPI glitches back briefly and the system therefore thinks that this is the alignment point. The process is simple and clean and is also applied irl SPI glitch .trk

DBS 1/2 already represents the best resolution. https://forum.dcs.world/topic/337970-cant-change-azimuth-and-scale-while-in-dbs2-mode-a-g-radar/?do=findComment&comment=5336796

However, the Aim120c still needs MLINK updates from the host aircraft. Is this a given when the radar is in silience?

Oh yes, that would be very cool, or at least a mod? I handle it in such a way that I search everything in the HI and lock, if the target flies a notch and hits the gate, the display flashes, then I immediately switch to MED and the lock remains stable. But of course it would be nice to know at anyi Time

Maybe I'm remembering it wrong, but there was a newsletter from ED about this and FC3 seemed to be making good money.

All Pics broke

maybe,but the Shrike-45 has ~65kg warhead. and the SA-8. 5-8mm top armour? would like to see how mobile the thing is after a direct hit

where an SA-8 should be destroyed or have heavy damage on a direct hit

SPI does not move with the TGP, but a fixed SPI is created at the moment the TMS UP is pressed, this point is located behind the airplane on the ground.

Currently, not all radars in DCS RCS can recognize differences. F16/18 radars, for example, cannot do this. I know from F15E/M2000 that RCS is taken into account. Therefore, what you are describing could actually work for these radars. As an example: a naked F16 can be detected with HPRF at ~70nm, fully loaded it is then already ~110nm I have not yet tested whether the type of payload makes a difference, but it could well be possible.

Is already reported

In my opinion, XY is not invalid per se, in fact it is very valid. Our tape is an upgrade, which theoretically means that only new features and upgrades are listed. The basic workflow hardly differs in essence

are you sure that the seeker has a range of ~10km? I think if the Missile would fly the loft profile it would be no problem to see the laser over ~10km.

For our version, the time was simply increased. Maybe it also depends on the DTC settings, but basically it is correct in DCS as it is.

Not every server allows hot start

Yes, I have encountered something similar before, very unpleasant. I'll check again, maybe that's exactly what it is. EDIT: something like the example? TGP JUMP .trk

Would you upload tacview or tracks from the tests?

I have deliberately not opened the wpn page to demonstrate this. If that doesn't change soi. Is it then basically correct?

in principle, but only if the FCR goes into the tracking state, in his example he is not yet in the tracking state only with the 2 TMS UP he would be in the tracking state and thus SOI to WPN page ah understand like this? : https://streamable.com/3o0pbj

but that's how it is in dcs. Did you get this from an lua? Because it feels more like 3° or max. 15°. I'll test it again ingame. I am curious what the correct value is

I have checked again, you are right then I must have made a mistake before. Maybe Same Like here? If the Shrike-45 is not in the sa2 track cone, the missile is blind.

looks good

which Maverick, otherwise set the TGP from MAN to AUTO I saw your track and hmm. if you only want to leave SP then TMS Down should be enough otherwise it means for our version basically, if FCR GM is SOI and you press TMS UP>> FCR GM tracking state = the SOI changes to WPN/MAVERICK. However, your FCR is not in tracking state after TMS UP, but the SOI still changes.