Jump to content

Der Michel

Member
  • Posts

    409
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by Der Michel

  1. Not necessarily a bug! ND: Indicates the highest grid Minimum Off Route Altitude (MORA), in a circular area of 40 NM radius around the aircraft. VD: The VD also displays safety altitudes. However, the VD displays the highest grid MORA or the MSA, along the aircraft trajectory and in the VD range.
  2. The F-PLN shouldn't mess up the upper data area. The F-PLN has to be clipped like the Map-Data.
  3. Hi, I#m not sure about this one, maybe check also your sources.
  4. Wheel numbers are missing
  5. And another example: EDDV27R NDB, The GA has to be blue!
  6. The GA-Wpt have to be drawn in blue also in TMPY-Mode The upper CTV belongs to the GA part:
  7. @Eddie did you notice my feedback?
  8. @Eddie is this also reported/tracked?
  9. @Eddie also tracking/forwarded this one?
  10. During all my flights, the MORA was always indicated with large font numbers. I think there might be a bug: The hundreds have to be shown in small font numbers. Examples from Real AC:
  11. Example: EDDV27R NDB MAP is 0.6 before runway threshold. So the AnchorPoint has to be labeled EP27R The AnchorPoint is missing at the ND. Also the AnchorPoint height need to be checked. It has to be 50ft or the TCH above the threshold. The FLS was guiding me to low. And just for clarification the rules for other MAP placements:
  12. The GS diamond at the ND has to be a double diamond like at the PFD.
  13. The FLS beam has to be cut/removed outside the vertical cut! I marked with red the part that shouldn't be there.
  14. The symbols/labels need to be drawn above the green path layer.
  15. The course indicator is drawn outside the drawing box. Has to be clipped.
  16. The ILS/FLS course indicator overflow box is sometimes drawn, when the course indicator is inside the HDG-tape.
  17. Fenix is running a lot Code outside MSFS (wasm). Coding is complex and the debug tools for msfs are not the best. The A350 is a real complex aircraft, so a lot potential issues. And maybe some coding skills or the beta testers …. who knows. At the end ini is working hard on the wasm crashes and each update is an improvement. And that’s what is important.
  18. Let me add some more information. If iniBuilds is doing CDA, it’s currently just wrong. There shouldn’t be any level off decel segment prior FAF. That's the meaning of CDA. Btw: Also the MFD (FPLN) should indicate that pseudo waypoints.
  19. There is some inconsitency regarding CDA, if this is modeled by iniBuilds. I have two circles with 2 in it at the VD. But not at the ND. Also are two "2" wrong, it should be "1" and "2". ND VD
  20. All relevant runway approaching advisory are not triggered.
  21. If a runway is selected in the FMS, the runway code has also to be displayed.
  22. HI019 is part of the GA and should be blue! Also that leg shouldn't have a -3.0° indication.
  23. If a FROM is entered at INIT page, the ALIGN ON REF has to display by default the airport reference coordinates and not dashes. The dashes have to be two behind the dot: --°--.-- and ---°--.-- (the ones for N/S and E/W are missing). 3. The LAT LONG window does not accept any input.
×
×
  • Create New...