TOViper

Very nice! Thanks!!

Sure, I will do!

I added some more infos on my post above for the devs.

yup

Yesterday I followed the CI, not the HUD When you follow the CI, you will never notice that the HUD guides you wrong, because the HUD follows your turns instead of leading you. You can try it out: Emphasize on the phase 2, and fly turns within this phase. You will notice that the HUD follows you, instead of the HUD leading you to the correct heading. Don't forget to turn OFF the TILS by rotating to a channel different from that of the runway.

If we talk about landing WITHOUT TILS in use, I think that the HUD indications during the 2nd phase (page 151) are not correct. The book says: "Phase 2, TILS not in use All the navigation indications are based on the navigation systems estimation of the aircraft position. The course indicator bug on the course ring indicates the heading towards the touchdown point LF. On the CI, the circle marker indicates the touchdown point. >PICTURE< Steering command along the circumference of the approach circle is displayed on the ADI and the HUD in the following manner. If the aircraft angle of travel after passing LB diverges more than 5° from the extended runway centerline, the pole track and reticule in the HUD move to correspond to a bank angle yielding a 4,100 m turn radius." This is not what's happening in the sim. What happens is that the HUD indication "sticks" to the currently flown heading, and turns with the turning aircraft. So if you follow the HUD only, you end up somewhere, but not aligned with the runway. If you follow the CI, you would never notice that the HUD is not leading, since it simply follows your steering. This issue relates to normal (long) approaches AS WELL AS shortened approaches, both WITHOUT TILS and ST+MT version. This is wrong behaviour I strongly assume. If @Machalot or @MYSE1234 are around, they are welcome to comment too. Any other drivers too of course ...

I watched the track several times now, and I think I am now aware of what is happening. Even if following what is written in the book on page 158, the HUD guidance is not working as I would expect; ADI and HUD diverge, and HUD is "glued" to the currently flow heading. @QuiGon, may you take a look plz. Note: In the mission the TILS is not turned off (or set to a wrong channel), it has to be done after hopping into the aircraft. I have done two flights, one with the original mission, and another one with my own mission (_2.trk). References: page 151, 152, 158 2023-05-07_AJS37_LANDN-NAV_PO_LANDN-NAV_bad_HUD_guidance.trk 2023-05-07_AJS37_LANDN-NAV_PO_LANDN-NAV_bad_HUD_guidance_2.trk

It doesn't, since it only checks the files in the DCS installation folder, not in the DCS Saved Games folder.

Hm. I would start over with suggesting you a DCS repair... Why I suggest this? Very simple: After an OB Update in the past (about 2 years ago, I made a post), I had a mixture of older and new files of F-14 on my disc, which produced funny behavior. The repair did the job ... and I was happy again.

Hm. Are you sure you set the correct BANA GRÄNS for the runway (e.g. 07 for Kutaisi) when landing from WEST to EAST?

Copy, thanks, I will take a look in the late evening.

I wasnt't able to reproduce in MT version. See track. Maybe you can provide a track from MT version? 2023-05-06_AJS37_LANDN-NAV_PO_LANDN-NAV.trk

copy, did you test this in ST as well?

Can you forward your changes to HB?

Hi Snappy! IMHO this behavior exists since the module's existance, and is worth checking! I was just not able to find any thread about this ...

Hey Snappy! I might find a minute very late in the night to test it. Two questions: a) On which runway did you land on? b) I assume you flew by hand, not using AP, right?

Dr.'s quote for you: FLY MORE VIGGEN. Then everything should become better.

Update 2023-05-06: .) page 101 (FPV hidden/visible) .) page 126 (old ECM U22 pod / pre-heat & indication) edit: I currently have problems to upload the file, I will try later this afternoon. edit2: Got my troubles sorted out, file is online now. Hafe vun!

sure I can do that!

Manual now reads the following: null

Hey Rudel! Kola map ... *ufffff* ... how long ... ??? No news, no forum, no nothing ... Anyway, in the meanwhile we are going to stay here to polish up our beloved bird ...

Hey guys! I reworked the section in the RC2.1 slightly to make it more clearly. Please look at the screenshot and go through the text. If you have any comments/suggestions, please leave them right here .... thanks! null

How was it possible that I have overseen this little issue in 7 years??? ShameShameShameOnMe

Now, after having access to my rig again, I figured out that the reference button works on ground (at least for what I consider it to be used). After line-up on RWY07, I entered 0740 (which is 074.0°) into BANA GRÄNS, which is the true heading of the runway center line. This was then shown satisfactorily OK on both the HUD and the ROSE. Then I mis-aligned the aircraft just a bit, and pressed the REF button, with the consequence of the ROSE turning from the current true heading to the entered runway heading of 074. Seems to work, does it? See attached track. Steps to reproduce: Use current OB, MT, Caucaus, single aircraft, out of ME Hot spawn on ground with B0 as starting base Manually entered coords of Kutaisi for LS Manually entered 0740 for BANA GRÄNS (this was somehow necessary two times, don't know what I did wrong ... ). edit: I did a second run, this time with using 9014 as LS, then bad line-up, then REF button > works OK too, see attached track _2.trk 2023-05-02_AJS37_Reference_button_works.trk 2023-05-02_AJS37_Reference_button_works_2.trk

YOU ARE CRAZY. But I love you man!