Concorde - Unable to Enter Airways
-
Hi,
Summary: It seems impossible to enter airways in the current implementation of the FMS onboard the Concorde. When entering airways via r-keys on the flight plan page, the scratchpad is automatically filled with "< RETURN" (looks like all keys are somehow misaligned). Typing any airways thereafter is futile. Please look into this, thanks!
How to reproduce:
- Boot up a flight
- Go to the flight plan page, select a waypoint and enter the airways entering page
- Unable to enter any airways
Platform: PC
-
Hi,
Summary: It seems impossible to enter airways in the current implementation of the FMS onboard the Concorde. When entering airways via r-keys on the flight plan page, the scratchpad is automatically filled with "< RETURN" (looks like all keys are somehow misaligned). Typing any airways thereafter is futile. Please look into this, thanks!
How to reproduce:
- Boot up a flight
- Go to the flight plan page, select a waypoint and enter the airways entering page
- Unable to enter any airways
Platform: PC
-
@ewky Thanks for this, I'm checking it out ready for the first update, might just be an error in a line of code in the html_ui or similar.
@dc1973
also unable remove waypoints correctly or selecting a different approach, it keeps the old approach in the flightplan and adds the new approach as an addition. Very buggy this FMS and very frustrating to make any changes to the point where one just stops using the aircraft, at least for me, will wait for an update before using it again. Not really fair to everyone that bought it!Norbert Finger
Webmaster Noble Air
nobleair.net -
@dc1973
also unable remove waypoints correctly or selecting a different approach, it keeps the old approach in the flightplan and adds the new approach as an addition. Very buggy this FMS and very frustrating to make any changes to the point where one just stops using the aircraft, at least for me, will wait for an update before using it again. Not really fair to everyone that bought it!@nfinger The FMS belongs to Asobo, not us, so it's really not our fault that it's buggy. We simply placed the same system in Concorde. That said, a lot of people happily using it without issues so I'm not sure why you're having problems. I myself am not an expert in using an FMC so cannot comment on it really other than to say we will keep an eye on things and see if we can improve them if required.
-
@nfinger The FMS belongs to Asobo, not us, so it's really not our fault that it's buggy. We simply placed the same system in Concorde. That said, a lot of people happily using it without issues so I'm not sure why you're having problems. I myself am not an expert in using an FMC so cannot comment on it really other than to say we will keep an eye on things and see if we can improve them if required.
@dc1973 thanks for the fast reply.
The FMC reminds me of the early version FBW A320 which had the same shortcomings, after the changed the coding and made it their own it works beautifully and is solid. Perhaps you can borrow the coding and make your own that actually works. I think for a paid product is a must and these corners should not be cut to meet perhaps a deadline? In a fast aircraft like the Concorde the FMC and or reliable INS is vital.Norbert Finger
Webmaster Noble Air
nobleair.net -
@dc1973 thanks for the fast reply.
The FMC reminds me of the early version FBW A320 which had the same shortcomings, after the changed the coding and made it their own it works beautifully and is solid. Perhaps you can borrow the coding and make your own that actually works. I think for a paid product is a must and these corners should not be cut to meet perhaps a deadline? In a fast aircraft like the Concorde the FMC and or reliable INS is vital.@nfinger Hi, we didn't cut any corners - it is Asobo's requirement to ensure that their own product meets standards. To "borrow" another developer's code would be highly unethical. This is something that either Asobo will fix, or we will figure out in time. I'm sure we will understand the issue before long and correct it.
-
@nfinger Hi, we didn't cut any corners - it is Asobo's requirement to ensure that their own product meets standards. To "borrow" another developer's code would be highly unethical. This is something that either Asobo will fix, or we will figure out in time. I'm sure we will understand the issue before long and correct it.
-
@dc1973 The question remains why did you not develop your own reliable FMS before releasing the aircraft? Aerosoft's CRJ have got a reliable working FMS and even the free FBW A20N is working great.
-
@nfinger Largely because typing that is a lot easier than actually doing it :) As I said, the Asobo FMS should be reliable and we have not had any other reports of issues. We'll keep an eye on things though.
@dc1973
I will sent some screenshots soon, to show what is happening every time and can be replicated.To replicate:
- start Concorde on egll airport gate for cold and dark startup.
- enter your flightplan departure and destination icao eg. egll/kjfk
- enter your waypoints, so good so far
- enter your departure runway and sid
- in cruise enter your destination runway and star
- try and change destination runway and star
- all waypoints from previous star are still there as a additional waypoints
- delete additional waypoints manually - problems occur
-
@dc1973
I will sent some screenshots soon, to show what is happening every time and can be replicated.To replicate:
- start Concorde on egll airport gate for cold and dark startup.
- enter your flightplan departure and destination icao eg. egll/kjfk
- enter your waypoints, so good so far
- enter your departure runway and sid
- in cruise enter your destination runway and star
- try and change destination runway and star
- all waypoints from previous star are still there as a additional waypoints
- delete additional waypoints manually - problems occur
