I have noticed that almost all speed constraints on SIDs (as well as Missed App) like MAX 210kt on the Jeppesen Chart are not correctly indicated on the FMS of ProSim737 (V2.26).
Any chance to fix this in future updates?
Example:
EDDH SID IDEKO6G (Cycle 2310) waypoint DH254 has a MAX210KT limitation. But on the FMS only 210 is shown. This means you need to fly AT 210kt which might trigger a performance warning on the aircraft (unable DH254).
Hi,
let me check it … We have this information in the database, but I’m not sure, if the ProSim database support this flag. I will check it and I will come back to you here …
Thank you for your details and the report
Cheers
Richard
Hi again,
I have checked now the ProSim database, the speed-description is available but in this exampe the “BELOW” is really missing even, that we have it in the source. So, it´s a bug somewhere in our parser.
I just started to analyze it and of course to fix it … sorry.
I will inform you here, when I have fixed it - possible I will create a second revision (depending on the fix and the effort). Thanks for your understanding!
Hi,
I have fixed the issue and we have created a second revision of AIRAC 2310 … so please update your ProSim dataset via manual-installer or FMS Data Manager.
All speed-restrictions should now be include the speed-description too. Thanks for the report … let me know, when something is still wrong.
Hi Richard
Tested it today. Unfortunately it is still the same. No “210B” indication but just “210” for Waypoint DH254 as shown in my pictures above.
I’ve installed “prosim_b737_2310v2.exe” and verified “cycle_info.txt” contains “Version : 2”. So I guess installation was successful. Prosim FMC also indicated Cycle 2310.
Any other ideas or do you think this is now definitively a Prosim Issue?
… the extended leg table with the speed restriction + the speed description in this case B (blue the leg-id for reference):
Thats what we offer now in the database … sorry, but I thing ProSim doesn´t support this column than even when we have added it due a request from ProSim. I would report this to ProSim, you can reference to this topic, if you want … sorry Raphael