Ironhand

Had time this weekend for 3 quick landings at a gross weight of 13652 kg which is fairly close to @Tin_Rat’s landing weight in his original post. The first 2 were similar to the one I posted above with one wheel coming off the runway. The third resulted in both wheels sticking. Interestingly enough, there wasn’t any wheel smoke either. This was probably the smoothest landing I’ve ever made in this aircraft. TRK attached. (I porpoise in the first minute of the flight. It’s not the TRK misplaying.) Here’s a quick video at 1/8th speed of the few seconds before and after the landing: MiG-29A Senaki--GW-13652kg.trk

Never be afraid to ask a question, especially after you’ve done your due diligence and searched for the answer first. There will always be someone to help. Enjoy the Flanker.

Unfortunately, you read my post before I realized what you were actually referring to and edited it. The TD controller, whatever you call it, is only used to designate the target. TD Control is found in the non-axis section for assignment, while TD Slew is found in the axis assignments section. But both do the same thing. Use one or the other.

The TDC is just that. It moves the TD over the target in Bore and the target mark in the BVR modes in order to lock the target. What it’s called depends on whether you are using the keyboard assignment or binding it to an axis.

Looks like you’re right about that right tire. I didn’t check from that side. From the left side it looked like both stuck. At first I was going to protest that those images weren’t from my track but then I realized that I was using a custom Ukrainian skin. So, of course, you’d see the default Russian skin. Watched your video. From the cockpit, you’d never know that the tires left the ground.

Well… it’s not guaranteed that you’ll bounce. I was both lighter (40% vs 70% fuel) and careful to do this landing pretty much by the numbers (height and speeds over outer/inner markers, threshold etc). TRK attached. If time allows, I’ll try again this weekend with the heavier version. MiG-29A Senaki-No Landing Bounce.trk

I’ll add this track as well. From the cockpit I had no sense that I’d bounced. MiG-29A Landing Bounce.trk

Still…Anything is better than nothing. Great news!

No. You’re not going crazy. I checked from a different angle and the tires definitely leave the runway: As draconus suggested, it’d be best to create a new thread in order to report it. This isn’t the thread to leave it in. Include your track and, if you want, link the above video which is made from your track. Edit: I thought I had posted this 3 hours ago. Just came back and realized I had written it but not posted it. Anyway, I don’t think you have much more chasing to do.

Yes. Over use of the afterburner can boost you into the next century.

Of course. But Section 2-9 in the 1986 revision uses 350 for both profiles, not 300 for one and 350 for the other. That’s why I was curious.

Are you making 1 or both aircraft “clients”? Any aircraft you want to fly in multiplayer must be a client aircraft.

That’s white smoke making it look elevated. The animation wraps the smoke effect around the tire starting from the front. Yes. The strut animation seems extreme.

Well…this is interesting. From the 1986 revision of the manual:

In my viewing of the track the starts compress (a lot) but the wheels never leave the runway. Regardless of weight, the struts should not be unloading like that in a gentle landing.

There are two versions, aren’t there? One from around 1974 and another around 1984. Which is yours, the latter? Edit: Oops. Didn’t notice draconis’s post until just now.

No problem. I had double-checked myself before making the post to Gilligan. So much info to keep track of.

No I didn’t. Both are climb at 350. The difference is the Mach number at crossover.

No. More like 40-45 minutes, I think. You’re dealing with IAS and the higher you go, the more speed that number actually represents. Assuming you’re at 35,000 ft, that 250 knots (IAS) would translate to somewhere around 580 knots at sea level. Edit: 250? I thought the climb was at 350 to M0.9 and M0.9 thereafter. Regardless, it’ll be less than 1:45.

Ahhh...yes. Forgot about that rule...which is too bad.

That’s why I used the qualifier “roughly”.

Ditto. Great way to handle it.

FWIW, I can only watch the FA-18 track, since that's that's the only module we have in common, but F6 works fine on my end. The view switched to the weapon and, once multiples were in the air, switched to the next one in sequence.

Perhaps because the tanks aren’t weapons? Just for chuckles, jump into the Su-25T and drop a bomb. Does F6 work as advertised?

It’s no different than the RedFor radars. A general search is a general search. The only time you would set the estimated target range to anything other than the default would be under direction of the controller. Otherwise you scan with “0” altitude difference for longer range BVR targets and + or - “1” for closer BVR targets. If you are using an altitude differential of 2km or greater, you are already WVR in most cases unless you are flying extremely low or extremely high. Beyond that, in the Su-27, especially, your SA is as good as the F-15’s because of the HDD. You know which bogies are higher or lower and roughly how much. You know which are faster or slower and roughly how much. And you also know where their noses are pointing. The MiG-29 cockpit, unfortunately, is less helpful in the SA department.