More FMS problems
-
kasten.amarant
- Posts: 12
- Joined: Sun Dec 22, 2019 2:32 am
More FMS problems
Since the latest update my problems with FMS increased.
I reinstalled this plane 3 times now, reinstalled the c++ libs that it needs and im out of ideas tbh.
One problem is mentioned here
http://milviz.com/forum/viewtopic.php?f=105&t=11413
But now a few others got added.
As you can see here the distance is increased continuously
https://youtu.be/tCL-KNHmWA0
Then i have altitude values that i cannot understand really. You see here that 10000ft is prepopulated on many waypoints. And inbetween those waypoints suddenly a way lower alt is displayed, with far lower speed too. This causes problems on AP when passing those waypoints. I HAVE inserted the cruise alt. These 10000 feet waypoints are middles in the cruise.
https://youtu.be/8rhFAYiSgE4
Also, lets say in a situation where im in a climb, lets say at 20k feet. Crz level is 24k feet. Then lets say i pass a wp during climb that has a "21k or above" restriction and between this and the cruise phase suddenly again are waypoints prepoluated with alts/speeds that imo make no sense. Then it can look like this
current climb alt 20k feet, next wp 21k or above, the following waypoint after the 21k or above shows 4000 feet, and the following 24k. Then one follows with 3400 one with 4500, next with 6000 and so on. All that when 1. im way over this alt already and 2. the cruise is on 24k and should last for many more waypoints. Why does it show an alt of 4000 and other low alts between those? These are NOT restrictions. Its prepopulated values, autoinserted.
A pic with such weird values can be seen here. But the vid above also shows this. That was in the descent
I was flying at around 18k feet when making this pic. For my understanding, knowing around 5 other FMS/FMC systems these values make no sense. Maybe one can fill me in ^^ Flying on 18k feet the next wps in a descent should show me calculated values until the next restriction, based on my current alt. But these 3154 feet really irritate me.
It looks a bit like the FMC always thinks im still on the ground, not on any alt.
Also the localizer works fine but the glideslope, on 6 out of 7 flights leads to a nosedive. It doesnt keep following the vertical path, instead it nosedives to the ground.
Like mentioned, it follows the lnav, leads to the loc, captures the loc, captures the GS but then nosedives into the ground.
All in all sadly i have many problems with the plane atm what makes it often near unflyable.
Seems not everyone has these problems so i wonder what could be wrong there.
All other planes work as expected (when taking known bugs out of the discussion). I know this doesnt help much and ppl dont want to hear it (for a reason probably, im aware of the fact that every plane can use different .net/c++ libs and has other requirements overall) but i still add it
Sorry
I reinstalled this plane 3 times now, reinstalled the c++ libs that it needs and im out of ideas tbh.
One problem is mentioned here
http://milviz.com/forum/viewtopic.php?f=105&t=11413
But now a few others got added.
As you can see here the distance is increased continuously
https://youtu.be/tCL-KNHmWA0
Then i have altitude values that i cannot understand really. You see here that 10000ft is prepopulated on many waypoints. And inbetween those waypoints suddenly a way lower alt is displayed, with far lower speed too. This causes problems on AP when passing those waypoints. I HAVE inserted the cruise alt. These 10000 feet waypoints are middles in the cruise.
https://youtu.be/8rhFAYiSgE4
Also, lets say in a situation where im in a climb, lets say at 20k feet. Crz level is 24k feet. Then lets say i pass a wp during climb that has a "21k or above" restriction and between this and the cruise phase suddenly again are waypoints prepoluated with alts/speeds that imo make no sense. Then it can look like this
current climb alt 20k feet, next wp 21k or above, the following waypoint after the 21k or above shows 4000 feet, and the following 24k. Then one follows with 3400 one with 4500, next with 6000 and so on. All that when 1. im way over this alt already and 2. the cruise is on 24k and should last for many more waypoints. Why does it show an alt of 4000 and other low alts between those? These are NOT restrictions. Its prepopulated values, autoinserted.
A pic with such weird values can be seen here. But the vid above also shows this. That was in the descent
I was flying at around 18k feet when making this pic. For my understanding, knowing around 5 other FMS/FMC systems these values make no sense. Maybe one can fill me in ^^ Flying on 18k feet the next wps in a descent should show me calculated values until the next restriction, based on my current alt. But these 3154 feet really irritate me.
It looks a bit like the FMC always thinks im still on the ground, not on any alt.
Also the localizer works fine but the glideslope, on 6 out of 7 flights leads to a nosedive. It doesnt keep following the vertical path, instead it nosedives to the ground.
Like mentioned, it follows the lnav, leads to the loc, captures the loc, captures the GS but then nosedives into the ground.
All in all sadly i have many problems with the plane atm what makes it often near unflyable.
Seems not everyone has these problems so i wonder what could be wrong there.
All other planes work as expected (when taking known bugs out of the discussion). I know this doesnt help much and ppl dont want to hear it (for a reason probably, im aware of the fact that every plane can use different .net/c++ libs and has other requirements overall) but i still add it
Sorry-
matpietsch
- Posts: 268
- Joined: Sat Dec 21, 2019 10:02 pm
Re: More FMS problems
Here is another example of this behaviour:
Hilie 2 into KSFF for RNAV 04L
Cruising altitude which was set at PERF and on the MCP was FL280.
Hilie 2 into KSFF for RNAV 04L
Cruising altitude which was set at PERF and on the MCP was FL280.
- 2019-12-29_23-29-21-74.jpg (304.47 KiB) Viewed 692 times
- 2019-12-29_23-29-22-577.jpg (306.39 KiB) Viewed 692 times
- 2019-12-29_23-29-24-970.jpg (299.45 KiB) Viewed 692 times