Ironhand

You can start the engines and get everything set for taxi. You just can't move the aircraft until the alignment is complete or you'll have an issue.

What I noticed, when I took a second look at the flight, was that KC never chanced to AC indicating a target lock. I just suddenly had launch authorization.

It's max range is 10-12 km which doesn't mean that its range is always 10-12 km. The range will depend on altitude and other factors. About 9.5 here I had just launched the first and was about to launch the second.

Thanks all, for the explanation. @Seaeagle, that all makes sense now that I understand the reasoning behind it all.

I’m not clear on something and, hopefully, you can explain it. “Field of regard” is the total area that can be captured by the sensor. “Field of view” is the angular cone that can be perceived at a particular moment in time. What is the “targeting angle” and why is it different from the “field of regard”? Or is the targeting angle simply how far the sensor can slew? In which case there’s no problem covering the 75* field that it can cover. Sorry. It’s been a rough few days and my brain’s a bit fuzzy.

So does your original post reflect a powered glide (idle engines) or a non-powered glide? Just curious.

Since asking the question, I made a few experiments of my own. I assume my engines are out due to having run out of fuel. That seems more likely than losing both due to battle damage since, when that’s the case I’m usually missing a wing or two as well. At any rate, assuming empty tanks and nothing hanging off my wings, best glide speed for distance seems to be right around 400 km/hr. 300 km/hr, on the other hand gives significantly more glide time, if you’re searching for somewhere nearby (field, road, etc) to touch down.

That’s because I wrote that without checking to make sure that the “old” clouds were still being used. At one point they were. That is no longer the case. So, until ED reworks fog to work with the new clouds, the result will be what you’re seeing.

My assumption was that it was “0” wind. As for the rest? Well… IIRC the best speed for glide distance in an empty Flanker was around 400 km/hr. So I was wondering what he found. I don’t think I ever bothered to check speed for glide time.

Out of curiosity, what airspeed and/or sink rate did you use to achieve that 10:1 glide ratio?

In that case, I would be wrong. I was basing my comment on the Su-27 manual which made it sound like a 3-position switch. EDIT: Though I do wonder why you would need a “Medium” position marker, if there weren’t discrete stops. All you’d need is small/large.

3 position rotator: Small-Medium-Large EDIT: Used to set the target base size when using the cannon in “predicted target” mode but it’s also used with A2A missiles. Just don’t remember why for the latter, at the moment. It may have to do with the proximity fuse.

LCtrl

Caucasus map:

Hold down L-Ctrl while slewing.

60% matches the type of flying I normally do and represents the Flanker’s basic fuel load, filling only tanks 2 & 3.

I'd like for the fuel's specific weight to change with temperature, too. That would make fuel calculations even more realistic.

The request is an MP one isn’t it? In the ME you have either option with (Edit: typo. Should read “without”) the need to add or subtract. In MP refueling you only have %IIRC. I only take 60% fuel in the Flanker so I don’t pay attention.

All versions should remain. If I want to fly the Flaming Cliffs MiG-29A, G, or S (all of which I’ve paid for) rather than the FF -A version, I should be able to.

Not really. I read it the same way razo+r did. The AND MAYBE in the OP’s sentence makes what follows sound like a separate request. I was wondering what else he thought would make loading fuel easier in his mind, too.

I stand corrected, then.

No. The “Nothing” selection reverts you back to the old clouds.

You have to select “None” for the cloud preset first. That’ll give you the old clouds menu which has the “Density” setting.

I can confirm @virgo47 's finding. No wind and RW33 is selected. 1 & 2 m/s wind from any direction will shift you to RW15. 3 m/s and higher creating a headwind for a RW33 landing will give you RW33. Any headwind 3 m/s and higher producing a headwind for a RW15 landing will give you RW15. So the issue is the 1 & 2 m/s wind speeds. TRKs attached. Gudauta-No Wind-RW33.trk Gudauta-Wind 151_1ms-RW15.trk Gudauta-Wind 151_2ms-RW15.trk Gudauta-Wind 151_4ms-RW33.trk Gudauta-Wind 151_6ms-RW33.trk Gudauta-Wind 330_1ms-RW15.trk Gudauta-Wind 330_2ms-RW15.trk Gudauta-Wind 330_3ms-RW15.trk Gudauta-Wind 330_6ms-RW15.trk

It would seem that 33 should be the runway used whenever possibly due to the mountains off the end of 15. A DCS instrument landing in low visibility on 15 can make you dead. Interesting that 33 isn’t almost always used.