Issues resolved in FliteBrief 1.23
The following issues were resolved in version 1.23 of FliteBrief.
- The OFP no longer fails to process a DP002 message received from JSI when the FilingHistory parameter is included in the message.
- FliteBrief now correctly displays flights that weren't displayed because of calculation errors related to the tropopause data.
- FliteBrief now correctly processes ASHTAM information in certain time-related circumstances.
- FliteBrief now correctly links sector attachments (sent by FTP) to flights.
- Certain fields in the ETOPS Release form are now populated with relevant data from the OFP.
- Aviator users no longer see an error while deregistering a device.
- The RVSM Check Point field in the En-route module of FliteBrief no longer displays an error.
- When an updated OFP is received, the Fuel Required and Fuel Order information is now correctly updated with data from the previously retained OFP.
- The RoutePlotter and associated merged range rings are enhanced to make sure that charts are now correctly generated for flights.
- FliteBrief no longer displays extra lines on the following charts
when:
- Pacific and Australian tracks crossed the 180-degree dateline.
- ETOPS rings overlapped the 180-degree dateline.