N22YF

The flight director cross is displayed only when you're in ILSN steering mode, regardless of whether you switch into that mode manually or automatically, so if you were trying to follow the flight director cross, you were in ILSN steering mode. Also, you will be better off following the instruction in the Instrument Landing System training mission, which is to allow the steering mode to switch to ILSN automatically when you arrive at the appropriate waypoint. If you deviate from those instructions and switch manually instead, you may be switching at a time when you're less well-aligned with the approach path, which will make the approach more difficult.

Hello! You should be using your HSI to keep track of your orientation relative to the runway. Remember that the HSI will indicate the bearing and distance to the runway, as well as the heading of the runway (which will tell you whether you're aligned with the runway, or approaching from an oblique angle or from the wrong side). If you don't know whether or not you overflew the runway, you're not using the information on the HSI enough. Really large jumps of the flight director cross typically means that you're so misaligned with the proper approach path that the navigation computer is having trouble guiding you. If your HSI indicates that you're not where you should be (that is, aligned with the runway and heading towards it), try to manually correct this first, and then resume following the flight director cross. I recorded a flythrough of this mission here - hopefully that helps! Thanks for letting me know about your struggles with this mission - I'll review the training missions to make sure that I didn't miss any important points!

@BIGNEWY this bug is still present years later (in version 2.7.10.19473) - is there any chance it could be fixed soon? (In a nutshell, this bug is that the number in the "course" window in the A-10A's HSI is totally wrong, which can be quite confusing until you realize that's it's broken.) Hopefully it's an easy fix Thank you!

No no, this mission starts in flight in NAV mode already, so pressing "1" would switch to ILSN steering mode. The mission is supposed to finish once the player progresses through the training instruction and then successfully navigates to WP3.

Hey, glad you found them helpful! Thank you for letting me know about this issue! Unfortunately I looked into this mission and I couldn't reproduce the issue myself. Your problem is that you couldn't get the notification that the mission was complete by navigating straight to WP3 as requested - you had to first turn around and go back to WP0, and then fly to WP3, is that correct? Would you be able to upload a track file from when you fly this mission and encounter this issue? (After you fly the mission and end it, you can click "Save Track" in the "Debriefing" window to save a track file of the flight.)

Hmm, I had a similar problem on DCS version 2.7.9.18080. I made a bunch of super low passes (definitely under 400 feet AGL) over the town and could see the shooting, but nothing happened after the passes. I'm pretty sure my passes started more than 4 minutes after saying "preparing for our run" (it took me some time to enter the coordinates and fly to them, and figure out how to release flares), but the shooting was still going on during my passes and I didn't get any further dialogue. (Another minor issue I ran into in this mission was that I couldn't get the displayed altitude autopilot mode to work - only the amber light would come on when I pressed the button.)

I believe the Flanker has a trigger on the stick for only the run-up brake (the DCS command is "Wheel Brake Start"), and the pedals are used for normal wheel brake control. (At least, this is true for the Su-27, and I don't imagine they changed it for the Su-30.) Here's an example line from the Su-27SK flight manual: which, according to Google Translate, is:

Glad to hear that! Alright I uploaded an updated version of the missions - the space bar issue in the aerial gunnery mission should be fixed now! Thanks again for reporting the bug!

Oh my gosh, I think it is broken - thank you so much for pointing this out! (In all my testing, I think my beta testers and I always used a joystick button to fire the gun, and so we never noticed this issue with the space bar!) I will fix this and get an updated version out within a week! (I would do it sooner, but I'm away for the holidays at the moment.) In the meantime, you can certainly bind the "Weapon Fire" command to another key and/or a HOTAS button as a workaround, as you and @Rudel_chw mentioned.

The main skill required in this mission is following briefing instructions, not missile evasion Make sure you read the whole briefing and are following the instructions as written! (And make sure you're using the latest version of these training missions, which is v1.2 posted on June 30th.) If you're still having trouble after doing that, though, let me know! Maybe I need to make the instructions more clear. Hard to say without knowing the specifics, but that's certainly possible! Glad to have helped!! I also felt like it was a great jet to learn DCS on, since the cockpit is in English and it's much simpler than e.g. the Hornet (and much cheaper too)!

Thank you! I was attempting to do a much better job than the provided FC3 training missions and I'm glad it was appreciated! However, I think you might not disagree that a new set of MiG-29 or Su-27 lessons wouldn't be worth the effort if you knew how much effort such an undertaking took!

Neither, actually - I tried to explain this in that training mission, but maybe I didn't do a good job? Here is the text from the HSI description from that mission - could you let me know if some part of this is confusing or unclear, so I can improve the explanation? I know what you mean! I actually like the FC3 planes a lot for that reason - you lose some realism vs. full-fidelity modules, but it's much easier and quicker to get up to speed on how to fly them when you're starting out, and easier to remember if you take a break and come back. Well there are already MiG-29 and Su-27 training missions provided with the game - they're a little bare-bones, but they're complete enough that I don't think it would be worth the effort to create a whole new set of training missions (in contrast to the F-15, which does not have any provided training missions).

Apologies if the training mission for this topic (04 Navigation, Autopilot, & Fuel Management) wasn't clear enough! Here's the text from that training mission that covers this - could you tell me which part was confusing, so I can improve the explanation? (This is also explained on pages 47-48 of the DCS F-15C manual.) Note that the bank steering index isn't related to the bank angle, at least not directly. The bank angle is the roll angle between your wings and the horizon, while the bank steering index shows where you need to bank and steer to in order to follow the course line. You could use a steep bank angle to steer to this quickly, or a shallow bank angle to steer more slowly.

They do not go in any "MissionEditor" folder. The folder with the training missions should go in the destination mentioned in the instructions (that is, in your Saved Games missions folder). For a specific example, if your Windows username is "Johnspar" and you're running stable (not OpenBeta), that destination will typically be "C:\Users\Johnspar\Saved Games\DCS\Missions\" for English Windows installations. I'm not sure how other language versions of Windows translate these folder names - for Italian, it may be something like "C:\Utenti\Johnspar\Giochi Salvati\DCS\Missions\" instead. Hope that helps!

Hello Giovanni! Did you happen to see the provided instructions?

Alright I uploaded an updated mission set to the user files (same link)! This update fixes issues caused by that weather bug, and also I adjusted the conditions (QNH) so the altimeter reads more accurately on the instrument landing challenge. This update requires version 2.7 for a few missions, but hopefully most people have upgraded by now anyway. I looked into this issue - I believe it's this bug: I was able to work around it by putting a truck in front of the wingman which drives out of the way only once you get close to the runway, preventing the wingman from starting his taxi until you're about to take off anyway. Hopefully ED will fix this bug soon and I can remove this workaround Thanks again for pointing out this issue!

Different aircraft have different optimal ways to perform a crosswind landing, due to differing handling characteristics. For the F-15C, the prescribed procedure is to hold the crab through touchdown.

Thanks! (If you're running 2.7, then you are running OpenBeta. The latest stable release at the moment is 2.5.6 - specifically, 2.5.6.61527.3. You can see this here: https://updates.digitalcombatsimulator.com)

Thank you so much for all your feedback! I'm away from my sim computer for the next week or so, but I'll look into your spacing and speed suggestions when I have a chance. But if you follow the instructions from the previous lesson to throttle back to get to on-speed AOA after passing the initial approach fix, you should be at 160 kt with gear and flaps down at the outer marker regardless - see my flythrough here (the outer marker is passed at 3:51): Also, you should be coming out of the clouds at about 500 ft AGL (as you can see in that video). Are you running OpenBeta, and if so, are you using the latest version of the missions as described above? I suggest using the flight director cross on the HUD rather than the director bars in the ADI in general, since that allows you to keep your head up rather than looking down at your instruments (not that it matters in an instrument landing, but handy when you do have visibility). If I'm understanding what happened right, this is not exactly a bug - the problem is that the DCS F-15C has no way for the player to adjust the altimeter setting, so depending on the weather, the altimeter can be wrong: I just noticed this discrepancy in this mission recently, and plan to adjust the weather conditions so that the altimeter reading is accurate on my next update of these missions. Thanks for pointing this out! (Luckily there's no combat scores in that mission to lose!) Which version of DCS are you running? I'll look into this and see if I can replicate it and find a workaround, but it's possible this is an unavoidable AI bug in the current DCS version, and we'd just have to wait for ED to fix it.

The current implementation with the "RR" lighted letters (which does indeed mean "ready") is correct (that is, realistic), and the manual is outdated and incorrect. It is always two R lights when the store is ready for release, even when only one "weapon unit" is present. The manual really should be updated at some point, since these sorts of discrepancies are confusing. There is a problem, though, in the white lighted numeral in the bottom-left of the weapon station select switches: the number should correspond to the station number, rather than just being "1" for every station.

Alright I looked into it! Turns out this is due to a bug currently in the OpenBeta 2.7 release: Hopefully this bug will be fixed soon, but in the meantime, I added a patched version of this mission to work around this bug (by using a weather preset instead of manually setting cloud parameters). Please try this version and let me know if you still have problems! https://www.digitalcombatsimulator.com/en/files/3313014/

Here's another example, with a cloud base of 3281 ft, thunderstorm, density 10, and my F-15C flying at an altitude of 2500 ft MSL (the altimeter is wrong): Stable 2.5.6.61527.3: OpenBeta 2.7.1.6430:

Thanks so much for bringing this to my attention! The missions are designed for the stable release (2.5.6 at the moment) and I have not fully tested them on 2.7 yet. I'll look into that problem this weekend and see if I can find a good solution!

Oops, I ran into this problem too and didn't find this thread when searching, so accidentally started another thread about the same bug: I don't know if there's any way for the mods to merge the threads, but @BIGNEWY there's some more data in that thread which hopefully will help y'all fix this bug!

Glad to hear these were helpful! Please let me know how giving it another go works out - I may look into further revising this mission if the correct approach is too unclear.