Ironhand

RCtrl+ENTER will bring up the controls indicator. Bring it up and see how your trim is behaving, when using the trim hat. I'm having no issues on my end.

Not that I know of. Then again, the entire cockpit looks washed out.

Excellent.

Add about 8 seconds.

The F-16C is quite speedy, isn’t it?

@okopanja I think that the difference is the climb angle to Mach 0.95. Judging from the plots of our speeds, your angle was steeper than mine. EDIT: That assumes our aircraft were set up identically.

Thank you for the correction. Didn’t know that.

You just open the TRK file directly into the ME. No need to change to MIZ, then back to TRK. But that has nothing to do with your issue. Do you have a shorter MP track file that you can post here? Then we can see if it'll play for us. What map is the MP session on?

Track files: xxxxxx.TRK

As soon as you take control of the view in a track, you have control of the view going forward. The track has no mechanism for taking view control back. Been that way from the beginning.

Try turning “easy comms” on? This is an FC3 aircraft.

That one was somewhat like the afterburner intercept flight program laid out in the real world manual. Yesterday I made one more flight despite my promise to myself not to. That one came in at 1'21". In this last one I used both active pause and jackmckay's 1% unlimited fuel. I hadn't expected much difference but there was. This time I followed the flight program (maintain M0.9-0.95) until I passed through roughly 7000m. If you continue to follow the program from that point, you have to start reducing your pitch angle to hold required Mach and I know from experience that it'll make the flight longer. So at that point I pulled into a zoom climb. It's fun flying with no fuel... Track attached. Su-27 12000 m Climb_Unlimited-1-21.trk

Made a few more runs. My best time so far from brake release to 12,000 m on the info bar rather than the HUD (the HUD gets to 12,000 m sooner) is 1’29”. My previous reported time of 1’27” was from wheels leaving the runway to 12,000 m. I hadn’t noticed TheFreshPrince’s post until after posting. And this is where I’ll probably stop because I doubt I’ll be able to shave more than another few seconds off that time.

I don’t know what’s optimal for the MiG-31 but an Su-27 is not a MiG-31. In my 2nd attempt, I reached 12,000 m in 1’ 27” starting with 28% fuel (the first took 1’49” with 30-something fuel) both of which suggest that your profile is suboptimal. In both flights speeds above Mach 1 were achieved. EDIT: Also just occurred to me that the Su-27DCS has an acceleration drop in the transonic range that ED claims they have data for but is not demonstrated in publicly available data. So given the short time constraint involved, I suspect you won’t get all that close to the P-42 time.

Then you are doing something wrong in your climb. And, if I understood you correctly in your first post, you were unable to reach Mach 1+ speeds in the first climb you reported. That’s another suggestion that there is something wrong in your approach. Not saying that there isn’t an issue. Just saying that the difference is probably less that what you’re seeing.

It landed? So it got it half right…

The Su-25 is the older aircraft, lighter, and has no HUD relying instead on “steam gauge” instrumentation. It’s the premiere A2G workhorse in a number of air forces. The Su-25T, by contrast, has seen limited use but comes with a HUD, more armor, and a wider array of weapon choices. It’s the only flyable RedFor SEAD platform.

Speed has everything to do with it. The air flowing over the wing at 12,000 m altitude is moving roughly twice as fast as at low altitude. So the conditions are not the same. But I am not the one to explain it because I don’t fully understand all the physics involved. Your high altitude flight was somewhere in the M 1.1-1.2 region, wasn’t it? That puts you somewhere in that steep critical AoA drop off from 18 to 8 degrees on your chart. …..

At one time, the AP modes were less complex. "H" dates back to that time. When they added the LAlt+ modes, they didn't remove the "H" mode for some reason.

None.

I won’t be able to take a look at the tracks until tonight or tomorrow at the soonest. So I don’t know what speeds are involved but stall onset at high altitude occurs at a lower AoA than at low or medium altitude. So what’s happening doesn’t seem incorrect on its face. The IAS numbers may be similar but the TAS/Mach numbers most definitely aren’t.

Cool! Thank you.

Well…it’s not exactly leveling the playing field, if it makes the game unplayable or unpleasant for some but not all. It’s just changing who has the advantage. Someone always has an advantage. The only question is, is the advantage unfair?

@Flappie While the focus of Newbie62’s tracks has been the HUD cues, the ADI is obviously non-functional. Lose the HUD and you have no way to make a precision landing in IMC conditions. The pitch steering bar remains locked at the bottom of the ADI throughout. Only the bank steering bar is operative. Neither the glide slope nor course warning flags are in evidence either prior to or immediately after picking up the glide slope, though I don't know if the either should be in evidence. While flying down the glide slope only the bank steering bar is active. There is no movement from either the pitch steering bar or the glide slope deviation indicator. With 4.3 nm (8 km) remaining in the approach, both the glide slope and course warning flags suddenly appear and the ADI now provides no steering cues whatsoever. The 4.3 nm (8 km) distance is notable because this is the distance at which the ILS needles/bars in all other FC3 aircraft become active not inactive. I should add that crosswind has nothing to do with any of the above as the behavior is identical with no wind. EDITED to add TRK file demonstrating ADI/HSI behavior, in case needed. F-15C Preselected ILS Mozdok EDIT Views.trk

Sounds like allow external views got set to “no” in Options somehow. You can either open the TRK file with WinZip or something similar and edit the line in the Options file (use NotePad++) or just open the track file in the Mission Editor and select a light cloud preset. Save the track file as a track file with the new clouds. Now you will have visibility from the cockpit with external views locked. EDIT: Or just post the track and I'll see if I can fix it for you.