List of Bugs
-
matpietsch
- Posts: 268
- Joined: Sat Dec 21, 2019 10:02 pm
List of Bugs
Here is a list of bugs that have encountered during one flight were I have made the effort to write everything down and take screenshots.
These have to be adressed to be "beyond study level". Some are serious, some are needed to justify the claim. Here they are in no particular order:
1.Enter only airways on the flight plan page
The real FMS3000 allows for entering an airway right after an airway in the FPLN page. The intersecting fix is then selected by the system. This is very similar to what the Honeywell FMS on the Boeings or the MD80 does. Not possible with this plane.
2. Entering frequencies on the FMS - Dropping the leading "1".
On the real FMS3000 you can skip the leading "1" when entering a frequency and it will autofill it. Not possible with this plane.
3. Performance fluctuations
On my system the planes FPS fluctuate by about 40-50% during all phases of flight. Sometimes they are bad when in cruise and get better close to a major payware airport or the other way around or not at all or whatever. Sometimes they are bad on the ground. Normally as soon as the avionics are powered up they drop and fluctions occur. I think some optimisation of the code is needed because only the King Air showes this type of behaviour.
4. Weather radar strange pattern
On the weather radar I always see the arc shaped pattern like on the below picture. I am no expert on this matter so is this normal or supposed to be?
5. Map display missing
Where to find the display mode like on this picture:
6. PLAN mode - How to move the map
On the MFD there is a plan mode included, but how to move it or to look a flight plan detail further down the path? Right now it is useless.
7. Performance tables
It is not possible to operate the plane correctly without proper tables for takeoff, climb, cruise and landing.
8. Throttle mapping
Been discussed to death already...
9. Wrong calculations
Also been mentioned before. Here a flight from LOWS to EDDF. See this picture:
10. Navigation after TO
It is very strange that after TO for which, from what I learned, you select a pitch angle with the wheel and a heading, the plane will not follow an FMS plan once you switch the lateral mode to that. You have to force it with a Direct To. This cannot be right for such an advanced system. Especially when considering this is single pilot certified.
11. VNAV levels off early
VNAV was supposed to decend to 12,000 ft but did level off at 13,000 ft and had no intention to decend further. Selected altitude was 12,000 ft and there was no altitude constraint present that did require a 13,000 ft level off. The next constraint was the 12,000 ft one.
12. Automatic LOC tuning does not work
From what I know the FMS3000 / PL21 should automatically tune the LOC frequency but is does not. You have do enter it manually.
13. LOC caputure does not work
This is a no go: When in "FMS approach" or however it is called and with the needle visible and pointing aht the correct course selected, the AP just blasted through the 07R Z LOC at EDDF.
14. FMS pop-up to dark
Small one but the FMS pop up display out is way darker than the VC one which makes it hard to read.
15. No radar altimeter callouts despite MDA set
Title says it: the minimums were set but no callout close to the ground occour. I heared them once on a flight but it is not reliable.
16. Opening right side cockpit window does kill the GPU noise instead of making is louder
17. Cabin windows do lack any sign of glass
On the exterior model (which is very nice) the cabin windows just look "punched through" there is no evidence of glass etc. It looks like the people are sitting in the open.
18. Screens in the cabin move though the wood.
Mentioned by Rocky mountain rebel back in October in the video Milviz acutally promoted so you could think they have watched it. Not fixed yet. I admit is super low on the priority list but it shows how unpolished this bird is.
19. Hold function incomplete
Only FAA style is included but ICAO is missing
20. Fix page is missing a lot of functions
The fix page is missing functions like the "Abeam" which should be included in a "extemely accurate and fully functional FMS-3000", allowing me "to take full control over your flight planning".
Stuff like this has to be included then.
21. Navigraph charts
Nuff said....
22. Entering a flight level with "F" or "FL"
On the real plane you can enter a flight level with FL or F.
A lot of the above might be minor things a first but they do add up to a unfinished product that is also advertised with features that are not there and PL21 that is far from complete. They also show a lack of attention to detail for all of them or gross negliance for some serious ones. The fact that they have been found during one flight and by multiple members of your customer base within a few day - and in the few flight they were able to complete between CTDs - is very telling. Yes, some of the above a nitpicky but I want to let you know but still all the avionics stuff is a no-go.
At this point honestly I have no faith in this plane reaching the claimed functionality. My impression, and that of a lot of other customers, is that we will end up with another half backed toy that is sort of working but is not reliable nor enjoyable because so many compromises have to be made. The claim "Beyond study-level - an unrivaled simulation" feels like a smack in the face because I can think of many other addons that will rival and surpass the Kind Air easily. Unfortunately none of them are corporate planes.
I am very sad because I was really looking forward to the release for months to finally have a hardcore corporate plane to fly.
These have to be adressed to be "beyond study level". Some are serious, some are needed to justify the claim. Here they are in no particular order:
1.Enter only airways on the flight plan page
The real FMS3000 allows for entering an airway right after an airway in the FPLN page. The intersecting fix is then selected by the system. This is very similar to what the Honeywell FMS on the Boeings or the MD80 does. Not possible with this plane.
- 2019-12-28 01_26_46-Window.png (285.74 KiB) Viewed 1062 times
On the real FMS3000 you can skip the leading "1" when entering a frequency and it will autofill it. Not possible with this plane.
3. Performance fluctuations
On my system the planes FPS fluctuate by about 40-50% during all phases of flight. Sometimes they are bad when in cruise and get better close to a major payware airport or the other way around or not at all or whatever. Sometimes they are bad on the ground. Normally as soon as the avionics are powered up they drop and fluctions occur. I think some optimisation of the code is needed because only the King Air showes this type of behaviour.
4. Weather radar strange pattern
On the weather radar I always see the arc shaped pattern like on the below picture. I am no expert on this matter so is this normal or supposed to be?
- 2019-12-27_21-56-58-528.jpg (252.56 KiB) Viewed 1062 times
Where to find the display mode like on this picture:
- maxresdefault.jpg (111.21 KiB) Viewed 1062 times
On the MFD there is a plan mode included, but how to move it or to look a flight plan detail further down the path? Right now it is useless.
7. Performance tables
It is not possible to operate the plane correctly without proper tables for takeoff, climb, cruise and landing.
8. Throttle mapping
Been discussed to death already...
9. Wrong calculations
Also been mentioned before. Here a flight from LOWS to EDDF. See this picture:
- 2019-12-27_21-45-43-529.jpg (312.93 KiB) Viewed 1062 times
It is very strange that after TO for which, from what I learned, you select a pitch angle with the wheel and a heading, the plane will not follow an FMS plan once you switch the lateral mode to that. You have to force it with a Direct To. This cannot be right for such an advanced system. Especially when considering this is single pilot certified.
11. VNAV levels off early
VNAV was supposed to decend to 12,000 ft but did level off at 13,000 ft and had no intention to decend further. Selected altitude was 12,000 ft and there was no altitude constraint present that did require a 13,000 ft level off. The next constraint was the 12,000 ft one.
12. Automatic LOC tuning does not work
From what I know the FMS3000 / PL21 should automatically tune the LOC frequency but is does not. You have do enter it manually.
13. LOC caputure does not work
This is a no go: When in "FMS approach" or however it is called and with the needle visible and pointing aht the correct course selected, the AP just blasted through the 07R Z LOC at EDDF.
14. FMS pop-up to dark
Small one but the FMS pop up display out is way darker than the VC one which makes it hard to read.
15. No radar altimeter callouts despite MDA set
Title says it: the minimums were set but no callout close to the ground occour. I heared them once on a flight but it is not reliable.
16. Opening right side cockpit window does kill the GPU noise instead of making is louder
17. Cabin windows do lack any sign of glass
On the exterior model (which is very nice) the cabin windows just look "punched through" there is no evidence of glass etc. It looks like the people are sitting in the open.
18. Screens in the cabin move though the wood.
Mentioned by Rocky mountain rebel back in October in the video Milviz acutally promoted so you could think they have watched it. Not fixed yet. I admit is super low on the priority list but it shows how unpolished this bird is.
19. Hold function incomplete
Only FAA style is included but ICAO is missing
20. Fix page is missing a lot of functions
The fix page is missing functions like the "Abeam" which should be included in a "extemely accurate and fully functional FMS-3000", allowing me "to take full control over your flight planning".
Stuff like this has to be included then.
21. Navigraph charts
Nuff said....
22. Entering a flight level with "F" or "FL"
On the real plane you can enter a flight level with FL or F.
A lot of the above might be minor things a first but they do add up to a unfinished product that is also advertised with features that are not there and PL21 that is far from complete. They also show a lack of attention to detail for all of them or gross negliance for some serious ones. The fact that they have been found during one flight and by multiple members of your customer base within a few day - and in the few flight they were able to complete between CTDs - is very telling. Yes, some of the above a nitpicky but I want to let you know but still all the avionics stuff is a no-go.
At this point honestly I have no faith in this plane reaching the claimed functionality. My impression, and that of a lot of other customers, is that we will end up with another half backed toy that is sort of working but is not reliable nor enjoyable because so many compromises have to be made. The claim "Beyond study-level - an unrivaled simulation" feels like a smack in the face because I can think of many other addons that will rival and surpass the Kind Air easily. Unfortunately none of them are corporate planes.
I am very sad because I was really looking forward to the release for months to finally have a hardcore corporate plane to fly.
-
Taguilo
- Posts: 658
- Joined: Sun May 11, 2014 11:49 am
Re: List of Bugs
Hi,
First of all, thanks for your comments. They are helping us to improve those areas that still need some tweaking and fixing.
I think, however, that you are mixing apples with bananas and treating all as bugs, where some indeed are, when many of them are product of you not knowing how to operate certain systems that are working as expected. And we apologize for not providing a complete documentation timely -it will come asap -.
Let's see:
1.Enter only airways on the flight plan page
The real FMS3000 allows for entering an airway right after an airway in the FPLN page. The intersecting fix is then selected by the system. This is very similar to what the Honeywell FMS on the Boeings or the MD80 does. Not possible with this plane.
Do you know how many versions of FMS3000 software are available in different FMS3000 aircrat, even in different KA models?
Are you sure that what you describe applies for the KA350i version we are simulating. Please notice that, for example, FMS3000 pages on a Citation aircraft are not equal and do not perform exactly the same as in the KA.
Do you have any video/source of a KA350i as a reference so we can check? We have a source precisely on how to enter an airway on FP pages and the intersection is NOT auto selected by the system.
2. Entering frequencies on the FMS - Dropping the leading "1".
On the real FMS3000 you can skip the leading "1" when entering a frequency and it will autofill it. Not possible with this plane.
Are you sure that option is available in the KA350i model we are simulating? Do you have any video/official source for that?. So that we can include it if that is the case. I couldn't find anything related so far...
3. Performance fluctuations
On my system the planes FPS fluctuate by about 40-50% during all phases of flight. Sometimes they are bad when in cruise and get better close to a major payware airport or the other way around or not at all or whatever. Sometimes they are bad on the ground. Normally as soon as the avionics are powered up they drop and fluctions occur. I think some optimisation of the code is needed because only the King Air showes this type of behaviour.
I don't have any kind of FPS fluctuations that are not related to differences in scenery areas, weather complexity, etc. Should this be a bug or more like a feature of you current system configuration?
4. Weather radar strange pattern
On the weather radar I always see the arc shaped pattern like on the below picture. I am no expert on this matter so is this normal or supposed to be?
It is supposed to be a terrain return. But I'm not the coder of the Wx and also not an expert in wx radars.
5. Map display missing
Where to find the display mode like on this picture:
Just press MFD LSK 1L to display Upper Menu Format. Isn't that supposed to be the same as in the example picture ? - which is not from a KA350i -
6. PLAN mode - How to move the map
On the MFD there is a plan mode included, but how to move it or to look a flight plan detail further down the path? Right now it is useless.
First select a compass format different than PPOS in PFD, then select MFD LSK 1R and go to PLAN mode. You can advance the centered wpt using CDU MAP options.
7. Performance tables
It is not possible to operate the plane correctly without proper tables for takeoff, climb, cruise and landing.
I agree. Though there are some tables included in the Release, he hope to be providing more with the incoming Service Packs.
8. Throttle mapping
Been discussed to death already...
9. Wrong calculations
Also been mentioned before. Here a flight from LOWS to EDDF. See this picture:
Yes, both are bugs that will be solved in the incoming SP. We've already aknowledge that and people are all aware.
10. Navigation after TO
It is very strange that after TO for which, from what I learned, you select a pitch angle with the wheel and a heading, the plane will not follow an FMS plan once you switch the lateral mode to that. You have to force it with a Direct To. This cannot be right for such an advanced system. Especially when considering this is single pilot certified.
Selecting NAV from another roll mode will arm FMS mode. To make it active, the aircraft needs to be in a course that will allow the capture of the current leg. No need to DIR TO at all. Just need to know the right procedure, that's it. (our apologies, again, for the lack of documentation).
11. VNAV levels off early
VNAV was supposed to decend to 12,000 ft but did level off at 13,000 ft and had no intention to decend further. Selected altitude was 12,000 ft and there was no altitude constraint present that did require a 13,000 ft level off. The next constraint was the 12,000 ft one.
VNAV in the KA does not perform exactly the same as in other aircraft. And it is a complex system which has been tested, even commented by other pilots here and in other forums, to be working good. However, it doesn't mean there could be some situations that didn't show on the tests.
Unfortunately you comment here does not provide enough info for us to be able to replicate. Could be that you are not following the right procedure?
12. Automatic LOC tuning does not work
From what I know the FMS3000 / PL21 should automatically tune the LOC frequency but is does not. You have do enter it manually.
What you know is not exactly how the PL21 in the KA performs. It will auto tune and capture the LOC only if you arm the NAV-to-NAV procedure.
Which is completely simulated. More info on how to proceed here will be coming soon.
13. LOC caputure does not work
This is a no go: When in "FMS approach" or however it is called and with the needle visible and pointing aht the correct course selected, the AP just blasted through the 07R Z LOC at EDDF.
I don't understand what you mean here. You were in FMS approach and you wanted to auto capture a tuned LOC? Already explained above, you need NAV to NAV for that. Or Select FMS LOC mode. Again, you need to know what to do before "go" (lack of documentation, I know, I'm sorry for that).
14. FMS pop-up to dark
Small one but the FMS pop up display out is way darker than the VC one which makes it hard to read.
Perhaps. But the keys and legends are bright white. Is bright white really hard to read for you? I'm not sure we could be able to change that, sorry.
15. No radar altimeter callouts despite MDA set
Title says it: the minimums were set but no callout close to the ground occour. I heared them once on a flight but it is not reliable.
Hmmm. Never experienced that. Callouts always worked when MDA was properly set. Are you sure there were no other calls - like glideslpe - that might have interfered with the altitude ones?
16. Opening right side cockpit window does kill the GPU noise instead of making is louder
17. Cabin windows do lack any sign of glass
On the exterior model (which is very nice) the cabin windows just look "punched through" there is no evidence of glass etc. It looks like the people are sitting in the open.
18. Screens in the cabin move though the wood.
Mentioned by Rocky mountain rebel back in October in the video Milviz acutally promoted so you could think they have watched it. Not fixed yet. I admit is super low on the priority list but it shows how unpolished this bird is.
Yes, those are minor issues that need to be solved through SP. Obviously they cannot be top priority because, as we state we aim this to be a pilot training device, I'm pretty sure real pilots could care less for those when doing a training session. Not an excuse, indeed. Only an observation.
19. Hold function incomplete
Only FAA style is included but ICAO is missing
20. Fix page is missing a lot of functions
The fix page is missing functions like the "Abeam" which should be included in a "extemely accurate and fully functional FMS-3000", allowing me "to take full control over your flight planning".
Stuff like this has to be included then.
These two are incomplete items, you are right. And will be completed for the next Service Packs.
21. Navigraph charts
Nuff said....
Charts are actually available; there are people posting tutorials on how to load them and make them work. However, a more direct method will be available for the next Service Packs.
22. Entering a flight level with "F" or "FL"
On the real plane you can enter a flight level with FL or F.
Perhaps. Are you sure it applies to the KA350i version? If so, we will be including it for the next Service Packs,
Again, I appreciate your comments, even being not positive. However, I also believe all bells must be heard.
Tomas
First of all, thanks for your comments. They are helping us to improve those areas that still need some tweaking and fixing.
I think, however, that you are mixing apples with bananas and treating all as bugs, where some indeed are, when many of them are product of you not knowing how to operate certain systems that are working as expected. And we apologize for not providing a complete documentation timely -it will come asap -.
Let's see:
1.Enter only airways on the flight plan page
The real FMS3000 allows for entering an airway right after an airway in the FPLN page. The intersecting fix is then selected by the system. This is very similar to what the Honeywell FMS on the Boeings or the MD80 does. Not possible with this plane.
Do you know how many versions of FMS3000 software are available in different FMS3000 aircrat, even in different KA models?
Are you sure that what you describe applies for the KA350i version we are simulating. Please notice that, for example, FMS3000 pages on a Citation aircraft are not equal and do not perform exactly the same as in the KA.
Do you have any video/source of a KA350i as a reference so we can check? We have a source precisely on how to enter an airway on FP pages and the intersection is NOT auto selected by the system.
2. Entering frequencies on the FMS - Dropping the leading "1".
On the real FMS3000 you can skip the leading "1" when entering a frequency and it will autofill it. Not possible with this plane.
Are you sure that option is available in the KA350i model we are simulating? Do you have any video/official source for that?. So that we can include it if that is the case. I couldn't find anything related so far...
3. Performance fluctuations
On my system the planes FPS fluctuate by about 40-50% during all phases of flight. Sometimes they are bad when in cruise and get better close to a major payware airport or the other way around or not at all or whatever. Sometimes they are bad on the ground. Normally as soon as the avionics are powered up they drop and fluctions occur. I think some optimisation of the code is needed because only the King Air showes this type of behaviour.
I don't have any kind of FPS fluctuations that are not related to differences in scenery areas, weather complexity, etc. Should this be a bug or more like a feature of you current system configuration?
4. Weather radar strange pattern
On the weather radar I always see the arc shaped pattern like on the below picture. I am no expert on this matter so is this normal or supposed to be?
It is supposed to be a terrain return. But I'm not the coder of the Wx and also not an expert in wx radars.
5. Map display missing
Where to find the display mode like on this picture:
Just press MFD LSK 1L to display Upper Menu Format. Isn't that supposed to be the same as in the example picture ? - which is not from a KA350i -
6. PLAN mode - How to move the map
On the MFD there is a plan mode included, but how to move it or to look a flight plan detail further down the path? Right now it is useless.
First select a compass format different than PPOS in PFD, then select MFD LSK 1R and go to PLAN mode. You can advance the centered wpt using CDU MAP options.
7. Performance tables
It is not possible to operate the plane correctly without proper tables for takeoff, climb, cruise and landing.
I agree. Though there are some tables included in the Release, he hope to be providing more with the incoming Service Packs.
8. Throttle mapping
Been discussed to death already...
9. Wrong calculations
Also been mentioned before. Here a flight from LOWS to EDDF. See this picture:
Yes, both are bugs that will be solved in the incoming SP. We've already aknowledge that and people are all aware.
10. Navigation after TO
It is very strange that after TO for which, from what I learned, you select a pitch angle with the wheel and a heading, the plane will not follow an FMS plan once you switch the lateral mode to that. You have to force it with a Direct To. This cannot be right for such an advanced system. Especially when considering this is single pilot certified.
Selecting NAV from another roll mode will arm FMS mode. To make it active, the aircraft needs to be in a course that will allow the capture of the current leg. No need to DIR TO at all. Just need to know the right procedure, that's it. (our apologies, again, for the lack of documentation).
11. VNAV levels off early
VNAV was supposed to decend to 12,000 ft but did level off at 13,000 ft and had no intention to decend further. Selected altitude was 12,000 ft and there was no altitude constraint present that did require a 13,000 ft level off. The next constraint was the 12,000 ft one.
VNAV in the KA does not perform exactly the same as in other aircraft. And it is a complex system which has been tested, even commented by other pilots here and in other forums, to be working good. However, it doesn't mean there could be some situations that didn't show on the tests.
Unfortunately you comment here does not provide enough info for us to be able to replicate. Could be that you are not following the right procedure?
12. Automatic LOC tuning does not work
From what I know the FMS3000 / PL21 should automatically tune the LOC frequency but is does not. You have do enter it manually.
What you know is not exactly how the PL21 in the KA performs. It will auto tune and capture the LOC only if you arm the NAV-to-NAV procedure.
Which is completely simulated. More info on how to proceed here will be coming soon.
13. LOC caputure does not work
This is a no go: When in "FMS approach" or however it is called and with the needle visible and pointing aht the correct course selected, the AP just blasted through the 07R Z LOC at EDDF.
I don't understand what you mean here. You were in FMS approach and you wanted to auto capture a tuned LOC? Already explained above, you need NAV to NAV for that. Or Select FMS LOC mode. Again, you need to know what to do before "go" (lack of documentation, I know, I'm sorry for that).
14. FMS pop-up to dark
Small one but the FMS pop up display out is way darker than the VC one which makes it hard to read.
Perhaps. But the keys and legends are bright white. Is bright white really hard to read for you? I'm not sure we could be able to change that, sorry.
15. No radar altimeter callouts despite MDA set
Title says it: the minimums were set but no callout close to the ground occour. I heared them once on a flight but it is not reliable.
Hmmm. Never experienced that. Callouts always worked when MDA was properly set. Are you sure there were no other calls - like glideslpe - that might have interfered with the altitude ones?
16. Opening right side cockpit window does kill the GPU noise instead of making is louder
17. Cabin windows do lack any sign of glass
On the exterior model (which is very nice) the cabin windows just look "punched through" there is no evidence of glass etc. It looks like the people are sitting in the open.
18. Screens in the cabin move though the wood.
Mentioned by Rocky mountain rebel back in October in the video Milviz acutally promoted so you could think they have watched it. Not fixed yet. I admit is super low on the priority list but it shows how unpolished this bird is.
Yes, those are minor issues that need to be solved through SP. Obviously they cannot be top priority because, as we state we aim this to be a pilot training device, I'm pretty sure real pilots could care less for those when doing a training session. Not an excuse, indeed. Only an observation.
19. Hold function incomplete
Only FAA style is included but ICAO is missing
20. Fix page is missing a lot of functions
The fix page is missing functions like the "Abeam" which should be included in a "extemely accurate and fully functional FMS-3000", allowing me "to take full control over your flight planning".
Stuff like this has to be included then.
These two are incomplete items, you are right. And will be completed for the next Service Packs.
21. Navigraph charts
Nuff said....
Charts are actually available; there are people posting tutorials on how to load them and make them work. However, a more direct method will be available for the next Service Packs.
22. Entering a flight level with "F" or "FL"
On the real plane you can enter a flight level with FL or F.
Perhaps. Are you sure it applies to the KA350i version? If so, we will be including it for the next Service Packs,
Again, I appreciate your comments, even being not positive. However, I also believe all bells must be heard.
Tomas
-
trevellwigg
- Posts: 6
- Joined: Sat Dec 21, 2019 9:47 pm
Re: List of Bugs
Taguilo, I can confirm the VNAV issues. Sometimes it works like it should and sometimes it doesn't. For example while flying the RNAV (RNP) Y Rwy 28R into KSFO starting from the IAF ARCHI at 4900ft the aircraft leveled off at about 4000ft between WIBNI and GUTTS. I was able to engage VS mode and force it down to the correct altitude of 3400ft and reengaged VNAV. The aircraft then correctly descended down to the next two altitudes 1800ft and 1264ft. But then leveled off at 743ft and remained there. It should've continued down to minimums 326ft in this case. It seems like the FMS isn't reading the Navigraph data correctly. However the aircraft flies the RNAV (RNP) Rwy 19 into KDCA just fine.
-
tcarter.67
- Posts: 47
- Joined: Sat Dec 21, 2019 10:32 pm
Re: List of Bugs
I have to agree, there a some screwy things that go on with both the NAV and VNav functions. I still think the addon has huge potential and I am enjoying flying it. Hopefully the SP's will fix most if not all these issues and we start seeing some repaints for it.trevellwigg wrote: ↑Sat Dec 28, 2019 4:48 amTaguilo, I can confirm the VNAV issues. Sometimes it works like it should and sometimes it doesn't. For example while flying the RNAV (RNP) Y Rwy 28R into KSFO starting from the IAF ARCHI at 4900ft the aircraft leveled off at about 4000ft between WIBNI and GUTTS. I was able to engage VS mode and force it down to the correct altitude of 3400ft and reengaged VNAV. The aircraft then correctly descended down to the next two altitudes 1800ft and 1264ft. But then leveled off at 743ft and remained there. It should've continued down to minimums 326ft in this case. It seems like the FMS isn't reading the Navigraph data correctly. However the aircraft flies the RNAV (RNP) Rwy 19 into KDCA just fine.
Would request a RFDS version if anyone has the skills to attempt it - here is an example https://www.flickr.com/photos/dave707/21338466036
-
Heronjr
- Posts: 110
- Joined: Tue Jan 20, 2015 1:04 am
Re: List of Bugs
22. Entering a flight level with "F" or "FL"
On the real plane you can enter a flight level with FL or F.
This is working since many builds ago. I use every flight I do.
On the real plane you can enter a flight level with FL or F.
This is working since many builds ago. I use every flight I do.