Ironhand

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.

Enjoy your vacation! And, BTW, there are some Su-27 ILS issues, too. More later in a new thread.

PM Flappie and ask him to check this thread, when he has a chance. He’ll let us know, if there’s anything else he needs. Creating the video only took a total of about 20 minutes. So I’d hardly call it going “all out”. Just thought a visual aid might have more impact.

@Newbie62 Just to add to the fun (evidence), here’s a comparison of the F-15’s and Su-27’s “ILS” ground track using the same mission. The F-15 is the aircraft that surges ahead at the start of the video and, then, stays to the left (above in the video) of the centerline while on the glideslope. (I was fast forwarding each track at different times during recording which is why an aircraft slows down/speeds up. Video is no real time.) You may want to change this thread’s title to something like F-15’s ILSN does not keep aircraft on centerline in crosswind conditions. To me it almost feels like it keeps you aimed at a point on the runway rather than points on the glideslope. Without a crosswind, you might not notice it.

Works the same. I hadn't checked that mission. When I did, "0" is indeed there but you can cycle up through all the WPs as well as back down to "0" normally. It may be that I've just never noticed the "0" WPs before. In that particular mission, though the graphic at the start shows WPs 1,2,3, you can only cycle 0,1,2 because WP 3 is the landing WP.

You're right. I forgot that, when I make an ILS landing with a strong crosswind component in the Su-27, the HUD indicators keep me looking out the side of the canopy straight down the runway's center line. It doesn't "circle" me in like what's happening in the F-15.

Oh, there’s a problem. Just don’t know what combination of factors causes it. It’s not the wind alone. Unfortunately, every time I fast forward your track, it breaks in some way. So that’s not a viable option. I did find the track I thought I was uploading the other day. It’s attached below (F-15C HUD Preselected ILSN Vaziani). Like I said in an earlier post, I removed everything except the wind and, then, added an F-15 starting closer to Vaziani to fly. It may be important that I selected Vaziani as the landing runway in the Editor because ILSN took me in perfectly. My landing/crashing at the end, though, was anything but perfect. I did find the runway, however. I set up another mission with the same winds without a landing runway selected and flew again (using an approach position closer to your own)—F-15C ILSN Non-Preselected Bug. This time, I ended up to the right of the runway as opposed to ending up to the left as you did. So something is wrong somewhere. I made a quick baseline flight into Butami. There was no wind and Butami was not selected for landing in the Editor. It worked perfectly. So… 1) It’s not wind alone since both flights into Vaziani had wind. One was successful. One was not. 2) It’s not preselection of the runway alone. Both Vaziani and Butami had success. 3) It’s not Vaziani alone simply because there was success at Vaziani. EDIT: Just noticed your edit. No, nothing that complex should be necessary. While you should always be in the habit of cross checking your instruments, you should be able to follow the HUD all the way down. F-15C HUD Preselected ILSN Vaziani.trk F-15C ILSN Non-Preselected Bug.trk

I just downloaded and checked a few quickly. You're seeing a "0" WP, when the mission starts in active pause which is interesting because, as soon as the sim is unpaused, the "0" turns to "1" and it never appears again. But I can see how that would be confusing. You can interact with it in active pause when airborne but not in a cold start on the ground.

@Newbie62 My apologies for wasting your time. I have been severely under the weather since Friday and I have no idea what I did in saving the track. I reviewed what I uploaded and that isn’t the one. Again my apologies. I’ll try and locate the right one and, if not, try flying it again.

Seeing "0" as a WP is very strange. I don't recall ever seeing it myself. So I'm not sure what was happening there. The "O" WP is a Mission Editor item. It marks your start point. In an air start and, possibly, a ground start away from an airbase (a road for instance), it's your starting coordinates. In a ground start at an airbase it used to mark the center of the runway--and still may do that. It's been a long time since I've checked. But that then becomes to point from which the distance to WP1 is measured. Draconus clarified your other concern. As always, if you have questions, ask. Someone will be along to help.

@Newbie62 I still haven't viewed your subsequent tracks but I did take your original track, edited out all of the units and the clouds but kept the winds. I then added an F-15 to fly. The HUD took me right in to the runway. The landing went just about as well as expected...unfortunately. Track attached. Newbie62_F-15C ILSN_VFR.trk

When I watched your track, you cycled forward thru all 5 WPs and stopped at WP 1 as you began cycling forward again. You then tried cycling in reverse but couldn't because you were already at the start (WP1). While you can cycle forward indefinitely, you can only cycle back to the beginning. If you try to force it beyond that, it will briefly show you your starting point (WP0). But you should not, and I did not see, it cycling 0,1,2,3,4,5,0,1,2,3.... If you cold start, you are not in any NAV mode, when you first turn on electrical power. You have to bring it up by pressing of the "1" key.

Yes. The ploy of unlocking, then relocking using the same missile after the radar falls out of mem mode, no longer guides the missile as should be the case.

I haven’t spent any quality time in the F-15C’s cockpit in about 12 years. Most of my time is in the Russian birds. So I’m less familiar with the information presented on western HUDs which is why I was focusing on the ADI and HSI. Those are familiar in any cockpit. I’ve downloaded the additional tracks but haven’t had a chance to view them. Hopefully I will by the end of the weekend. BTW, a 19 m/sec crosswind component is well beyond the 15 m/sec allowable for the Su-27 (my usual ride). I’m guessing that the F-15 would be similar. But that shouldn’t effect the instruments negatively. In the Russian FC3 aircraft, the ILS needles don’t go live until 8 km (4 plus a little nm) from touchdown which may or may not be correct. Something similar might be going on in the F-15C pit.

When I watched your track, the ILS bar was indicating that you were to the left of the runway for most of the way down from at least 8 km out. Then it suddenly centered and red flagged as you flew completely out of the beam. It sounds like that's not what you experienced on your end but, for me, you ended up where the ILS bars said you would.

Sure. It’d be nice to have Romania, Bulgaria, Moldava, and Ukraine fully modeled but that was never its intent. The Black Sea is there to give the Kuznetsov and other ships somewhere to sail other than immediately off the Caucasus coast.

Great news!

LCtrl+Z to speed up (each press of combo ratchets it up) LAlt+Z to slow down (each press of combo ratchets it down) LShift+Z returns to normal speed.

Even by your definition, the Black Sea itself is complete. Where the Black Sea has water, there is water. Neither the Sea of Marmara nor the Augean Sea are part of the Black Sea. There was never any intention to model the topography (or civilization) other than what we already have. That land is there simply to provide the Black Sea’s boundaries. Those details are already in the map. Or is that what you're saying.