Ironhand

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.

Regardless of how it plays back, every action you took is still recorded. There's a record of every asset (AI or static) in the mission along with their attributes. There's a record of any mod involved, etc. So it still shows them a lot of info. An incorrect playback doesn't necessarily negate its usefulness. And who says that they can only watch it?

Often not correct. But it does show them every action you took, at a minimum, when they read it. And, since they ask for a TRK recording the bug with every bug report, they obviously can get information they need often enough.

Can’t help you there. I’m more likely to be the one lobbing the R-77s at you. But you should have the range advantage. So I really don’t know.

Author Solution Posted just now Watching your track, everything is fine. The same is true if I set up a mission approaching the runway's end. However, I moved your start position so that I approached the airbase perpendicular to the runway from the west. For inbound, ATC gave me directions for a landing on 32 but referred to it as 14. (I had to take control of the aircraft because in your original recording, Soganlug was the 2nd option. Approaching from the west, it's the 1st. Also, here are two more tracks taking off from the runway. In both, the directions for the approach are correct, but the runway number is wrong. If everything is okay on your end, then I guess that's that. Flappie_ Su-27-Edited1-Soganlug landing 14.trk Soganlug Runway 32-14.trk Soganlug Runway 14-32.trk

Unfortunately, I don't own the F-16 and, so, can't check how your track plays out.

I stared at that image for 5 minutes before the penny dropped. I wonder how that happened. Anyway, I’ll check your trk, next time I get to my computer.

Glad you’ve finally gotten a handle on it. 2 bags adds 8200 to the internal load of 13,400. So in my flight I still had the equivalent of a full bag plus a little arriving a Nalchik.

Unfortunately, those are actually from the original BS 2009 manual. Too bad. I’d love to have this to get excited about.

Yes. RAlt + ”-“ and RAlt + ”=“, IIRC.

There is much about how radars work that feels like magic to me. So I’m hardly an expert in this area. That being said, as I understand it, the reason for the target size setting adjusting the estimated target range setting is to (hopefully) place the target in the most focused portion of the beam at the estimated range. That results in less ambiguity in the return. I don’t think it matters in FC3 aircraft at all but, if we ever get full fidelity Su-27s, it will.

I'm hardly ever in the F-15C's pit so I don't know the aircraft well. But it seems strange that your wing tanks are empty by the time you get to Nalchik. I don't know the mission you're flying but, taking off from Vaziani with 2 wing tanks and 8 AAMs, I reached 35,000 ft 49 nm from Nalchik at roughly M0.9. Arrived over Nalchik with 4500 lbs of fuel remaining in the wing tanks (17,900 lbs total). I flew the profile in the thread I linked to earlier. I've attached the TRK file, if you feel like getting bored watching it. This is not a combat mission. Just flew the profile I had linked to. Climb at 350 until M0.9 is reached and M0.9 thereafter. F-15C MIL Power Flight--Vaziani to Nalchik.trk

Unfortunately, unless ED completely scraps the current recording system and creates (or invests) a new one, we are stuck with what we have. Due to its nature, you have to start at the beginning and can leave nothing in between out.

Yes! Pretty please with sugar on top. Separate them again.

The mod only works(ed) on the Su-25, Su-25T, and A-10A. None of the FC3 fighters had the coding that would allow it to work with them.

@Gilligan , you might find this helpful regarding the climb to altitude: