
ekosif
Member-
Posts
63 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
ekosif's Achievements
17
Reputation
-
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
-
Unfortunately I've tried uninstall and install again maybe 5 times, didn't work
-
I was really excited when I saw the changelist, but could't even make a single flight so far.. First I couldn't download the update. It stucked on the installation process. After couple attemps, I failed without any chance until I saw one topic in the forum that suggests the alternative download section in iniManager. It worked to install the updates, but... Secondly, after update, there were no aircraft at all! Just cones and ground equipments. I tried many liveries and finally Finnair livery has worked, but.. While I was trying to prepare the aircraft to the flight, FMS is frozen completely.. And also, there was really weird stutter that happens every 3 seconds periodically and fps drops below 10 during this time. It's 3 o'clock in the morning in Sweden and I have been trying to debug it for last 2.5 hours, because as I said I was excited and just wanted to try it. I am sorry but this was the worst update I got so far.
-
I have the same issue with new update. @haza2 please address this as it is a big bug to prevent using the addon completely.
-
I normally first press the SET ZFW and fuel, and click GSX to board. Once the boarding started, ZFWCG is resetting and updating itself during boarding. But I understand your point, makes sense.
-
After boarding completed, no. But during boarding, it changes automatically even without clicking the refresh button
-
I prefer to use the number in the OIS as it is changing over time during GSX boarding, so I presume it is the correct one 🙂