Issues to be aware of

New Features in 0.18

Improvements to UI

1.Changed the FPL review box to include the flight ID header information

2.Added a header to the NOTAMS section of the Operational Reports so it is clear when the data was generated and the valid interval

4.Fixed the aircraft setup so that ‘out of order’ levels can be added and FPP sorts them correctly.  This makes it easier to add performance data in the middle of the table

5.Improved the chart so all relevant data near the mouse (airports, nav aids and airways) is shown rather than the ‘most important’.  Now each airway is shown separately (linked to the change in airway structure).

6.When the mouse is moved over the route each node now shows its distance from the departure point

Bug Fixes Changes

1.Improved memory error checking when printing to detect out of memory conditions

2.Cleaned up the print logic to reduce memory usage and prevent conflict from the screen chart and print chart

3.Pressing cancel while routing should now have a ‘cleaner’ exit

4.Fixed a problem where an extra blank page was printed in the trip kit and where many extra pages were sometimes included in the chart printout.

5.A problem where on some occasions a route via waypoint was removed by the autorouter has been fixed

7.Changed the charting logic to prevent labelling over icons to reduce the chance of confused graphics (note, the airway labels are still not declutttered so will have overlaps

10.Adjusted terrain mapping to ensure better match of graphic to underlying terrain data (there was a shift of about 2 nm in the terrain map between maximum and minimum zoom.

11. 11.Correct legend for profile graph(the colour coding was wrong)
    

12. 12.Key route labels now print correctly (they were printed very small)
    

13.Fixed an issue handling ROUTE130 errors (unknown designator)

14.  Fixed an error where some versions of PROF198 (CDR 3) were not being processed correctly

Database changes

1.Cities have been put back in the database

2.Added LIQS IFR entry points

3.Airport database updates fixing Newmarket and adding a range of Spanish smaller airports

Routing improvements

1.Changed the logic for reporting level caps to ignore those below the selected MEA

2.Fixed an issue where consolidated airports (i.e. EDM* where not correctly evaluated in the internal RAD check)

2.    Have included many of the CDR3 routes (outside ED, ET, LO, LS where they can be time dependent) and German VFR only restrictions in the database

3.Have added FPP Specific restrictions for a number of forbidden arrival/departure points

4.Corrected an issue where a mandatory link earlier in the routing process which was later determined to be forbidden would prevent FPP from finding a solution.

5.Airways between the same points are no longer consolidated.  On several occasions the properties of the airway (i.e. direction or CDR status) depend on the name.  This was creating routing errors)

6.VFR arrivals can now transitioning above FL170 (previously not allowed) - which prevented routing into Sion post the ILS decommissioning

7.Changed the logic for Types from an assumption based on performance to a lookup against the icao type list

1. •Recently some restrictions have been added by CFMUY that are not included in the Electronic RAD.  To the extent these involve a level cap or a mandatory routing, FlightPlanPro will not be able to resolve these.
   

2. •If you get a No Route message, check that the minimum and maximum altitudes are sensible. 
   

3. •FlightPlanPro should be able to process all Mandatory Route messages.  However, the logic has required extensive testing and reports of any failures to correctly resolve these restrictions will help develop the product
   

4. •Note, the altitude optimisation uses too much memory and can cause a programme crash on longer routes.
   

5. •The cloud profile doesn’t always work correctly for routes over 1000 miles.
   

6. •If you are flying a circular route (same departure/destination), the Notam brief will give an error.
   

The list of known issues that are being worked on is here