Hobel

And now we're driving round in circles for the second time. again, your videos are old since there have been guidence and pf updates, which has an impact on the scenarios depicted in your videos, so send new tracks if you can. There were also ecm adjustments, so if ecm was used in the video that is another factor. Uploading old videos even though there were updates afterwards and declaring them as proof is not good.

kinematically yes, but here there would be even more aspects to add some missles that have irl 100meter PF have only 20m in DCS, of course there is then a role effective. the same with the Aim120 in DCS, the PF is only 9 meters. theoretically the missle has more than enough information to know whether it will hit or not, for example if the missle is 30-50 meters or more behind the target and has a negative approach speed, it will explode and at least throw fragments towards the target. On the one hand, the missle wants to kill the target, on the other hand, the weapon is disarmed and does not simply fly towards the ground and probably still hits uninvolved parties, similar to a roll, the missle would detonate and thus at least still cause damage.

the thing is simple at the moment, the thresholdof the Aim120 is 30kts. if the target has a slow ground speed, the threshold of the Aim120 remains fixed at 30kts. However, there is a point that as soon as the target exceeds a certain ground speed, flies into the notch and then comes out of the notch 30kts, it seems as if the threshold has shifted by 3-4 times.

I also see an enormous number of user errors... hardly anyone knows what they are doing. specific examples would be helpful i am also on the server from time to time and always shoot my missles at 40-55nm and have a good PK.

when is the streamable video from? the YT video is 3 months old and there have been several updates in the meantime. Basically -wobble fix -PF was increased from 7 to 9m The wobble fix in particular is very important, as the Missle often wobbles to the dead or wobbles past the target. left after the fix xr5piv.mp4.f7c2ff0671d3e843455c437efc0afd02(1).mp4 so the YT scene might already look different now. therefore and due to the fact that there were some fixes new tracks would be helpful.

but this is simply a user error. The objects are very close to each other, just a few metres apart, and basically form one large object, so it's no wonder that the handoff is not clean. In such a situation, you have to lure the Maverick onto the target yourself from the point where you can see that you are lock the bus, I take over and then lock the correct target with the IR mav. In the second example, I make an FC with the TV maverick and also hit the target.

it is simulated and should therefore work

Actually, the weight of the engine increased significantly from the E to the K, so it is not really appropriate to compare the two. The K4 has a 30mm cannon and muntion in the nose + the significantly heavier and more powerful engine.. The tail of the BF109 has hardly changed compared to the engine section, so the center of gravity has probably shifted in other simulations where you can fly BF109E and K4 the difference in weight is sometimes more and sometimes less noticeable in different situations

There are exceptions. If the missle has to fly strong maneuvers, it explodes on contact in the "game context". However, I don't think this makes any difference to the final result and in case of doubt the fuze triggers. It then looks like this. Old examples: https://youtu.be/C42h1dhJwKg?si=FV_hvgS2CGGgD1PB

In dcs the missle always explodes with a certain distance as high as the pf is. With aim120 that would be 9m. A time delay is also mentioned in the lua. With the future new proxy fuze mechanics, however, this could all get a fine tuning.

Simply carry out a clean BSGT, should the Maverick still show a slight offset, you can simply correct it after 30nm is also very utopian, 15nm is more the use case. 2x TMS LEFT triggers the TV Maverick Force Corelate, so you can stabilize the Seeker to a point on the ground and also shoot it, so the method only works for static targets

For this you have the TGP, when you have the right target change the SOI to maverick, then TMS left 2 times and then TMS UP

Use the TV maverick, WPN SOI >Press TMS left 2 times, slewe on a target that is far away, press TMS UP and shoot. My record is 30nm

same here it happens and is also in the nature of the thing. Over time, the DCS Aim120 has been improved so that it is more likely to search for the actual target parameters, but as I said, this is not always a guarantee. this is an old video, Aim120 loses the actual target in the notch and switches to the next one that is "visible" xr5piv.mp4.f7c2ff0671d3e843455c437efc0afd02.mp4

interesting, go to a server with Fox3 and then try to get into a dogfight with someone, it won't take long and a friend will fire in there, the change is almost 50/50 that the missle will hit you

Before the "damper" update I also found it too bouncy, after the update it is extremely good to perfect in my opinion. I hope the other ww2 planes get this too! But it would be useful to upload a track of your situation, maybe there is an airfield which has strange characteristics, who knows...

Yes. In visual range, our rule of thumb is that if a friend is within the HUD frame, the risk is too high.

oh yes, that would be a fantastic idea!

The magic question is also what does the search pattern of our Aim120 look like? here 2 possible assumptions with A the missle could simply not have seen the target, B would guarantee a higher possibility.. or a completely different method, unfortunately I don't know In any case, the target is located in the gimbel limits and the missle knows in which area it has to search, but it still cannot find the target

I have a question, is it intentional that the shrike loses steering ability when it slows down? my observation. it starts to happen at 900 knots and the shrike-45 can no longer use its full 3G the whole thing degrades further and further around ~500knots the missle is almost dead and the control inputs are so weak that corrections are no longer worth mentioning. the result is that the loft mode has hardly any use even if the missle comes into the target area and only becomes active at 18,000 feet, it is usually already too slow and can no longer steer towards the target and does not hit, with the direct mode it is completely different the missle points directly at the target and if the missle slows down and the control inputs become less, the whole thing is no longer so dramatic because the missle already points at the target. here's an example, all shrikes that hit are "direct mode" and those that miss are loft, the leeway you have with direct mode is significantly greater and therefore more likely to end in a direct hit loft Direct.acmi

So I tested a few and the F18, for example, I could only shoot from the angle where the radar was looking, the shrike didn't track from behind

. I have not yet been able to reproduce this, the failure seems to be very random at first. I will have a look at the track and try to reproduce it again, but I can't say when and how long I will need.

Open Beta: F-18C speedgate Norm: ~75knots Wide: ~150knots F-16 MTR LO: ~75 MTR HI: ~115