Ironhand

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.

Unfortunately, no. Over the years, replay has become worse and worse. And it’s my impression that it’s more of an issue with 3rd party aircraft than ED aircraft and more of an issue with more complex aircraft than simpler aircraft, and more of an issue with complex missions than simple ones…in that order. Also tracks made online suffer more than single player. All that being said, my tracks play back correctly more often than not simply because I fly mostly single player in FC3 aircraft. My aircraft of choice would change, if we ever got a full fidelity Su-27 or MiG-29 but I fear I’ll either be in my grave or well into senility before either of those things happen. One thing you can try is to restart DCS before you play the track. Sometimes that seems to help.

How they behave and how they are supposed to behave are two different things. If this were a FF aircraft, it’d be a bug. As an FC3 aircraft…it’s not something I lose sleep over.

Yes. Same dial controls both. The same is true, for instance, of the weapon release mode switch (on the panel that includes the Master Arm switch) with its SINGLE-PAIRS-SERIES positions. The first two positions apply to both A-G and A-A weapons. What I don’t know about the TARGET BASE switch is whether or not it actually changes the estimated target distance displayed on the HUD. Either I haven’t translated far enough into the manual yet or it doesn’t specify.

I did RTFM:

Just copy/pasted this image in using Firefox... Same version as yours FalcoGer. So I guess it's not universal.

Thanks!

In that regard, you are absolutely correct. Even when they were 99% accurate in the early days, they broke with every update--which back then were far less frequent. But for debugging, the TRKs can have value which is a different issue altogether. They may not provide the needed information for debugging in all situations. But they can provide useful information in other instances whether they play back correctly or not. EDIT: Yes. I once set up a mission with only my aircraft to fly a series of touch and goes. Took off, ran the circuit 5 times, landed and parked the final time. Played the TRK and it showed me landing short and crashing on the first circuit. Reflew it making only one circuit. The 2nd TRK file was much smaller than the first.

Seriously? Please reread what you wrote. Because, as I said, all of your inputs as well as all of the mission particulars are recorded in the track file, assuming you crash during the playback and not during the recording. Again you’re assuming that they can only watch it.