Ironhand

Well…mine weighs in at 75.5GB. I’m in the process of updating. It’ll be another day or two before it’s done. EDIT: Ahh… Were you asking what would happen if you purchase them separately after the current update?

In buying and downloading the “West” you also downloaded the “East” in lower detail. In purchasing the “East”, you’ll have to download the high detail East. For people like myself who purchased the complete map, we now have the high detail “East” to download as well.

Maybe so. OTOH, they were able to provide the extended area without having to worry about whose computers will have a harder time handling it. I can just hear the uproar if they provided the detail you’d prefer now and had to back it out later, when the rest of the map reached full detail.

Thank you for your critique. Though I’m not sure 1 meter over 50 was worth mentioning, when the manual gives a range of 50-60 m.

Finally had a chance to fly and figured I’d add a short video of how I do it. Assuming you’re not landing heavy—here I’m landing with roughly 35% (1,100 kg) fuel and 6 R-73s—try to keep the tach in the 77-79% range as you descend toward the runway. Ideally you’re crossing the inner marker at a height of 50-60 meters with a speed in the 300-310 km/hr range. If you’re a little high, shift your aim point to just short of the runway for a bit to flatten out the descent. Then refocus on your original aim point. Your speed crossing the runway threshold should be in the 280-290 range. As the left edge of the runway comes into view, look left and forward, rather than straight ahead, to better judge your height above the surface. FWIW, I seldom pay attention to the AoA. Rather I keep an eye on the HUD pitch scale (notice that, when I shift my focus left and forward, I keep the scale in view). Do not let it go higher than 10 degrees. At 10, there is no chance of your tail or engine nacelles hitting the ground. Add a bit of throttle if it’s approaching 10 with no desire to stop. If you hold it at 10 at this point by adjusting the throttle, the proper landing speed (and AoA) will sort themselves out. Throttle to idle, when you feel you’re just above the runway and settle to the ground.

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.