Mr. Crow

The Flight Model is being worked on... As of now, It is surely bugged. It's been that way since 2021. They have stated many times that it is being worked on and it got slightly better already. The LSO still sees the nose coming down hard and still sees the 3 point landing. There is a workaround, however. You can pull up just before hitting the deck. For that, you have to fly a slightly low ball and pull up (hard) at the last instant. I can get it right 90% of the time and get an OK pass. The ease the gun (i.e., EGIW) grade is clearly a bug. You should hit mil power after touch down, not prior. This is very annoying. Once again, the workaround is to fly a slightly low ball and hit mil power, before touchdown (meh!).

This hit me hard. Thanks, man. If not for you, I would have given up. There are very few posts in this forum thanking other people (IMO), so I take this opportunity to sincerely thank you. Yes... The AI is buggy. Yes... It lacks real physics. Yes... It should have been fixed years ago. Yes... It's detrimental to DCS as a whole... However, there are other ways to look at it: for instances, by 1972-1973, USAF and US Navy pilots would routinely encounter expert pilots, who were fighting the air war from its beginning. So yeah... There were some individuals on the other side who would be able to take the Mig-21 above and beyond it's limits. Not to the level the AI uses it... But yeah... It'd be hard to get a good shooting solution and/or a kill. So I practiced, I got killed. I raved at the idiot who said he could easily take down a Mig-29 with an F-4 (don't get me started on this... you are not helping...). And then, I read through every post in this tread and every book I had regarding dogfights (I love Osprey Publishing!). And after hours and hours, I reached a level in which I could consistently kill the AI (up to veteran difficulty). Here are my 10 principles (not rules) to win the fight against the AI (and to be a good F-4E front gunner): 1. As mentioned in the quoted post: be fangs out all the time! Not just when you are gunning the AI down... All the time! It does not matter if the UFO is glued to your six o'clock. The aim is to kill the enemy. There are no second bests in this game. 2. Manage you energy with extreme care, fight the egg maneuver and know when to spend you precious energy. Be very conscious of your AoA. 3. Try and make the fights as vertical as possible (between 30 and 55 degrees worked great, more than that if and when extremely necessary). 4. Get into the fight at around 450 to 500 kts, you are going to need every Newton of energy you can get. 5. Use God's G (i.e., the extra G you get when rolling inverted at or near the top of the egg) and reach you maximum turning radius. Cheat back at the Mig. If you ain't cheating, you ain't fighting good enough. 6. Regain you energy on the way down (unload the jet as much as you dare). 7. If you hear the AoA tone, you are loosing energy fast. Ideally, do not get past the first tone. 8. If a Mig is glued to you 6 o'clock, extend the speed breaks and try to get the AI on a rolling or flat scissors. As soon as it begins to "dance" (you will know when you see it...) and begin to gain on you, AB on, watch it go pass you, hear the fox 2 tone and take the kill. 9. You will only get one to two chances at best! Remember, you will be loosing a lot of energy. Keep doing it too long and you will die or reach a draw and run out of fuel. The AI will not loose energy on the long term. It is not programmed to do so. 10. Use other types of missiles and experiment. Aim-7E-2 and Aim-9J both work great for me. I tried the Aim-9 JULI as well. Works even better. Bonus principle: If you loose track of the enemy, you are probably on your way to being shot down (i.e., loose sight, loose the fight). Try to extend and reengage. Hope to have helped. You can do it! Here are some Tacview examples. One is a surprisingly easy fight I had. Just went vertical, the Mig tried to compensate and lost a whole lot of energy at the top. The other is a scissor defense. Enjoy. Tacview-20240609-185205-DCS-My Gulf F-4E ACM.zip.acmi Tacview-20240609-122238-DCS-My Gulf F-4E ACM.zip.acmi

@Zomalk, Have you tried to use passive reaction to threats? Perhaps this would solve the issue. Let me know if it helps.

That's great! Thanks for the update!

Has this issue been fixed in the latest patch?

It seems there is a workaround for the issue, by going single thread. I have not tested it yet. Edit: It has been tested by others and single thread does not solve the issue, or works around it.

For me, in MT, it crashes when designating using HRM modes. It's happening in single player as well. And pardon me for being pedantic, but a workaround is not a solution. In any case, thank you for pointing out that single thread works around the issue.

Same here. But I found that it happens most often on the more high resolution maps. I have been able to press the TDC on low resolution maps, with some degree of safety. Other than that, I use MT.

I can confirm the delay is not working.

That did the trick! Thanks!

Ok, just made a navigation test flight on the Mi-24P. The simple way to use the map/DISS-15 system is to not turn on the switch labelled "AIRSPD SNSR TO DOPPLER" on the Radio Navigation panel. Do note that the rolling map is not terribly accurate, but it is close enough. However, I do not understand what the switch does. I am afraid the simulation might be correct as is.

Guys, I have come across this post here: I will investigate the matter and double check if it works.

Thanks, guys! It should be me causing the hook to bounce/skip, or simply missing the wires somehow.

I am also experiencing this issue. However, I have noticed this potential "bug" only after a cold and dark start in Single Player. Haven't played the Hind in multiplayer yet.

I have been trying out some landings with the T-45 on the Super Carrier. Even though I follow the exact procedure for a case I recovery, sometimes the hook will not engage, no matter how perfectly I fly the ball, or how precisely I follow the the E bracket down. Is that a known issue?