That is actually very much "in progress" Graeme and I anticipate switching to that dataset asap. I wrote extensive nav data routines for parsing XP11 navadata quite a ways back in prep for this eventual port....so the heavy lifting is mostly done. It will look for the custom data if it exists (from Navigraph or Aerosoft...XP11 format), and if not present, defaults to Laminars dataset. I posted on it in the forum somewhere way back when where the left FMS was running with the XML dataset and the right FMS was running with the XP11 navadata format; however, at that juncture, it was only displaying procedural names from the parsed data, not loading anything into the flight plan. We have a 'de-coupled internal' format we use for the FMS data, whereby we read in the XML data and cast it into our own data structure...so in theory, I now only need to write the 'caster' between the XP format and our internal format and it should be mostly done. TBH, I'm hoping it will just work with minimal troubleshooting...so yea, we're right on the same page.
-TomK