ekosif

Hello! As can be seen from the title, taxi lights, TO lights and Landing lights are not working. They just illumunate for a few seconds and then they dissapear. They are also not visible from outside as well. NAV and beacon lights were OK. Thanks!

I don't think they banned you, there must be some other issues

Helloooooooo!!!! @iniSteven @iniBuilds VNAV is NOT working properly, are you aware of this?

No, I am not using any addon.

I kinda agree with you @Bob57, just think about it, they brought HUD to the sim which is very cool but guess what, the most obvious thing which is alignment of the HUD data is not reflected to the correct position so you have to adjust your sitting position to see all of them properly. I am sorry but I still cannot understand how this can be missed... It is literally first thing to see when you want to check it in the sim

Hello @iniSteven, Is there any update on this one? I made another flight right now again to Istanbul airport and aircraft made the same behaviour again, it's not following the restrictions during approach. Also, even though it has been reported many times ago, HUD alignment is still not correct. When should we expect any update for it? And also, Landing checklist is not correct for flap item, it turns to green on flaps 3 even though full flap landing is configured. Unfortunately, we are not getting any update especially for MSFS 2020 even though some major and critical features are not working correctly.

Jeez, keep wondering how they were making taxi without ANF since Wright Brothers. I saw you commented and said having problems with ANF and BTV.

Hello! Thanks for your interest. It was the flight from Antalya(LTAI) to Istanbul (LTFM), SISPI1A arrival, ILS 35R. I am also attaching OFP here in case it helps. Thanks! LTAILTFM_PDF_1754520514.pdf

Hello, I will try to explain with help of a few screenshots: As can be seen from above, there is a altitude restriction at SISPI, which is at or below FL280. But aircraft descend profile is not following it and it starts descend just before the waypoint. In this case, it is not possible to be at/below FL280. Second case during the same approach, again as can be seen, even though I have already passed 11000 feet restriction and also another 11000 feet restriction in front of me, VNAV shows FL142 is on track. Also, during this time, aircraft is not descending and stayed leveled, so it is not overshoot issue. Also again during same approach, even though there is a restriction on the next waypoint which is between 5000 and 6000 feet, VNAV is not following it. I switched to OP DES to catch it but it shows I am 4700 feet below at this point according to VNAV. And also here, there is a speed restriction there (not below 210 know, it is at 210 knot) aircraft activates the approach mode and disregard the speed targets. If you also look at the VSD, it shows I will climb first and then I will descend again.

Hello, As can be seen from the screenshot, bird is not visible if there is crosswing during approach. It's like there is a gap on the left side of the hud, between the middle part and the speed section and if the bird goes to the left side due to crosswind, it becomes unvisible.

Hello ini Team! I just made my first flight with v1.1.1 on MSFS 2020 and it was great flight, this was the best flight since last couple updates. Thanks for the effort! I had 1 issue: During the cruise, I got direct from ATC to initial approach fix and applied it, but after speed setpoints changed from mach to knot and it was 200 knot at FL410, which does not make any sense. I also attached a screenshot for it. It was showing the .85 mach again at T/D. Other than that HUD was very good but I suppose it needs small position adjustment, bottom line is not visible at default looking position. And also, please bring back the "autobrake off" callout 😄 Thanks again!

How could it be HW problem if the problem was not exist before update and suddenly pop up after update? And because you don't have any problem does not mean that there is no issue.

Thanks for the tip, but I tried every possible restart scenarios 🙂 none of them worked. I restarted the flight, sim, pc and tried each of them Ps: I am in developer mode for last ~3 years, just didn't try the normal mode.

Well, good for you, but this doesn't help anything unfortunately

I don't think there is any roll back function