Jump to content

Limitations of Connected Flight Deck


Joshua Che.

Recommended Posts

As CFD is experimental, it's a precursor of our A330 development. As testing of something like this is incredibly complex we decided to release what we got now (it actually is pretty stable and very cool) but there are limitations such as:

  • Both Flights must start with the same panel state (doors, lights AND CORTE if you want to use it etc). (Use Ready for Taxi since door synchronization is buggy).
  • No dual FMGS, First Officer will have to use 2D Panel or go to Captain FMGS.
  • FMGS NavData MUST be the same. (Cycle and Provider)
  • FMGS Scratch Pad desync is possible. As Keyboard Input is not synchronized, use that to clear unwanted scratchpad characters. Confirm FPLN changes on each FMGS before inserting.
  • Altimeters are not properly synchronized due to the current A320 Shared Architecture.
  • Some amount of lag will be noticeable in high latency connection.
  • Presently, CFD don’t provide voice communication. Your own voice sever is needed (Skype/TeamSpeak).
  • Doors synchronization (except for Front Left) is buggy, turn connection off, then close doors then back on.
  • Setting Trim when Slave is jittery.
RECOMMENDED SYSTEM REQUIREMENTS
A minimum of 100 kbps connection that has less than 100ms latency is strongly recommended. Additionally, your frame rate should have already met the minimum 18fps requirement at all times.
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use