Hobel

Huh? so spotting is pretty solid for my system. 3440/1440. I can't complain too much. Before the big change it was terrible for me too.

MK22 goes to the search radar which is on continuously. with the others the track radar is only seen by the seeker when it is on, maybe there is a difference between search and tracking radar and search radar gives a sound and tracking does not?

One question is the sound when the Sa-2 tracks you? I will have a look at everything later

below 4500 feet and active pause was not on both can be seen in the video ah you reacted to another video and also here I have said a few times why this happens 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 and i need a second attempt in this case, even if there was no active pause in the example, that would still be okay. and I have now said several times why this is the case, if there are several targets in the tracking gate, it is almost random which target you lock. That's why I also need several attempts, which is completely normal. targets that are close to each other are a problem for the Maverick seeker, especially if they overlap Irl the Maverick would have even more problems with targets that are so close together. here, as can be seen in the video, all targets are in the gate, how is the seeker supposed to know which one to lock if there are 3 or more IR signatures in the gate? If you have a problem with the Maverick in a certain situation then upload a track and we can talk about it. because so far you have not posted a single track of the problem so that we can see your view... Track? i don't have the problem and for the other things you can create bug reports and attach a track if something doesn't work, we don't have to discuss it here

With the Bf109 the effect is very strong with the p51 it seems to go towards 0 but I have to test it again

This is possible and works very well, it also works with buildings but here the ground is hit. With the bunker mentioned here, you hit also roof with this method I looked at the track and the mistake here is, you stop lasing and then you throw the bomb, the bomb misses. I would expect the last position of the laser to be saved and not immediately thrown overboard as soon as you stop lasing. test it again just hold the laser down when dropping here you can see that the laser coordinates are discarded after a few seconds: 2024-08-19_13-58-01.mp4

how to reach 370mph (~595km/h) with the K4 I have just reached around 361mph(580km/h)

To be fair the shots are nose down and over 500m alt. In the Ed Newsletter it says to the other missile, below 500m alt and the missile makes a loft. In these pictures you can see su25 lvl Flight And below 500m And the kh-25 seems to initiate a loft. EDIT: okay i tested something else, in DCS the missle also makes a loft but only when it tracks the laser. with the DCS Su25, the missle drops after the start and only when the Missile sees the laser does the loft occur, but the ILR pictures show that the missle even initiates a loft from the rail The Seeker has a range of 8km but even within this range the KH25 only goes into the loft after flying ~300m

okay, but that's exactly what an “Emergency” is

Yep For testing purposes, I have locked vikher Missile in ACM mode

could you upload a track?

But the differences are not big and most of them are optimizations. And if the MLUs and the like point to this and there are still no documents that speak for or against it. so this is not a big deal here but if HSD is SOI and the radar Cursor disappears it would be a purely declutter measure.

Which weapons did you test this with?

um the whole thing is basically self-explanatory

what you are describing should also lead to problems with the real Maverick, I have now shown several times to what extent tracking works in certain aspects in DCS and everything stands and falls with the >>tracking gate<< if there are several targets in this, which tends to happen at long distances, problems arise. This is likely to be even more dramatic irl than in DCS. I even took the situation of a user here and showed him that it works using his own mission Such situations are quite rare and if you avoid firing like this, what I am showing here would be much more difficult irl.

if you haven't noticed DCS now has an inbuilt "theway" of course not as extensive as the way but you can create and save waypoints now

Here is a small hint. HSD is SOI no radar Cursor visible, but as soon as the SOI changes the radar Cursor jumps back into the picture

can you upload a track? with these parameters, the best tip for now is not to use loft mode Shrike-45

what kind of distances are we talking about here?

Strictly speaking, both sensors work in the same way on both aircraft for HAS/TOO in DCS. it is too precise in both planes the update time is basically the only difference here and this is not far away when it comes to the first blip. and maybe in the F18 the RWR also supports faster updating for the TOO display. The big difference to the F18 is that a nice symbol is shown over the emitter and you only have to put the TGP over it. In the F16 there is no such thing, but there is still something to point the TGP exactly enough on the target, simply place the target on the HAS page in the center of the cross and then the TGP diamond on the FPM. certainly not as pleasant as in the F18, but still possible and accurate enough. TOO/HAS only shows the emitter direction. HTS direction + distance this is a crucial difference. This is why the HTS also has to triangulate and this process takes longer than with HAS. and so you can fire the AGM-88 in one of the PB modes so that it can fly a LOFT profile and you have to do that in the F18 with the TGP to determine the distance. HAS has no LOFT modes. Maybe HAS mode is too precise and the BOX would jump a bit near the target or not be spot on, but in the end the AGM-88C sensor works the same way on both airplanes in HAS mode with only time difference as shown in the video. I think the best thing would be to build in an angular errors that could be 2-5° for the AGM-88C, that would then also affect both planes. if we assume an error of 3°, we have an uncertainty diameter circle of ~3nm at 60nm, which would still be pretty accurate. the function of the F18 is nice but the FOV of the AGM-88 is too small at the end for a reasonable overview, you get targets in the F16 even if you fly in offset and that without fiddling around with the TGP, you also have to create an MK for lofts and then shoot with PB. you can avoid this in the F16.

DTC is more or less related to this implementation, so we have to wait for more. Even though I would like it to work like it did 3 years ago until the dtc is there.

What you want is done with ccrp. There are many irl shots of the HUD, you can see how the pilots use ccrp to approach the target, just before the target the pilots press NWS to quickly switch from ccrp to ccip

Personally, I have to say yes the new INS is really really cool! but the fact that you can no longer use PRE planned jdam, or only to a very limited extent, because the JDAM GPS is still wip, really dampens the joy.

связано ли это наблюдение с этим? пример, показанный в видео, работал только в версии 2.8.1.34667.2, в текущей версии то, что вы видите в видео, больше не работает