Ironhand

This is probably the most important aspect of landing the MiG-29. While everything, obviously, plays a roll in setting you up for a smooth landing, your height above the ground as you make that final speed reduction defines your landing speed. The closer your wheels are to the ground, the slower your landing speed can be (within reason). It’s also one of the most difficult things to judge in the sim. The MiG-29 is the least forgiving a/c in this regard. Most others let you “cheat” a lot more.

I agree. And those of us who have been buying ED’s products since the 90’s should be getting a 90% loyalty discount. It’s only fair.

Actually I just realized that all you have to do is assign the “Pause” command in the UI Layer to a button or button combo on your stick or throttle. I’ve never done it but, now, I just might. I like the idea of not needing to grab the mouse or use the keyboard.

I like the concept but whatever was used would probably need to be something other than a command already in use.

Originally the “Mods” folder was were all a/c lived. As more aircraft arrived, a Core Mods folder added.

Hope springs eternal…

FWIW, it works fine with my equipment. So it’s not a universal issue.

Wonder if the issue was somehow related to the IR missile/flare fix in the patch.

@okopanja So I checked the Syria and Caucasus TRK files you posted. The mission file in both have fog turned off. I have fog turned off in the ME as well. An observation: If I create a mission, I can fly it as many times as I wish and IR missile seekers lock onto the target as they should. If I run one of your TRK file and, then, try to fly a mission created on my machine, they no longer lock as they should. If I remove all elements that the TRK recording adds and fly it as a standard mission file, IR missile seekers will not lock in neither your mission nor one I created.

It could be, if the server mission had fog set to “auto” and others you tried didn’t.

I probably won’t have the time to do that today. OTOH, your other (Syria) TRK played back as you recorded it. No lock.

@okopanja I only had time to play the TRK from the Caucasus. In my viewing you had launch authorization from the moment you locked the target and it continued until you passed over the top of the target.

Oh…that’s not the Pandora’s box I was referring to.

Well…it’s certainly going to open Pandora’s box.

Looks like the fire/smoke is being drawn in front of the fog rather than at the right distance behind it.

That’s because the star positions were never designed to change with the seasons. They’ve always been set to a date in Spring. Changing how it works would be a feature request.

Just to specify for OP a bit more. Using 1400 km/hr, you can maintain that speed until the fuel runs out. But using Mach as the reference, you are limited to 5 minutes in the 2.15-2.35 range due to possible degradation of the canopy.

Sure would be nice to have.

This would be most welcome.

I don’t know what’s going on but, since my last post, I’ve had another instance where I couldn’t connect and had a 2 day grace period here on the east coast. No idea now why you don’t.

Late seeing this thread. I downloaded the TRK and took control. AP worked perfectly on my end with me in control. If I just view the TRK, however, I see your difficulty but have no clue as to why.

Have you tried doing a slow repair? And, out of curiosity, when’s the last time you rebooted your computer? I’ve had odd issues pop up in the past with DCS that a reboot solved. Worth a try, if it’s been awhile. EDIT: In looking through one of the links you posted, I noticed that using a VPN was causing issues for some people. Is it the issue for you?

No problem on my end when I played a day or so ago. Couldn’t connect at start and told me I had something like two days to play before I’d need to log in again.

Thankfully, nothing I’m experiencing but I’m also not a VR flier in case the issue arises there.

Just tried that mission and received a mission success message. I took out 2 F-16s. My wingmen took out 1 before all dying. Some other flight took out the last one, I think. I ready didn’t pay close attention to the debrief. It didn’t make much sense to me to fly the 1st waypoint. I went straight across the mountain chain, then headed down the east side until about 80 km from Nalchik. At that point I turned deeper into the mountains looking for trouble. (Edit: the reason for my flight plan was to position myself between Nalchik and the F-16s so I had someplace to run, if necessary. It also helped to let me dictate the fight.) Told my wingmen to attack bandits, while I took on an F-16 attempting to flank us. Killed him. Turned into the fray and killed another but lost my wingmen. Landed before another group of enemy chasing me could catch up.