I've done some further checking on this issue.
Started FSX and loaded the FSBuild-exported route for NZDN to NZWN into FSX active memory via its flightplanner. Then entered in into my Wilco/FT 737 FMC via the ROUTE REQUEST LSK on the RTE page. This worked fine.
Then saved this route from within the Wilco/FT 737 FMC. This created a file named NZDNNZWN.U10.fpl in the C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\feelThere\CustomDB folder.
Exited FSX and restarted it. Loaded the company route NZDNNZWN into the Wilco/FT 737 FMC by typing in the route name into the scratchpad and pressing the LSK 2L. Worked fine.
Exited FSX again. Moved the file NZDNNZWN.u10.fpl as previously exported by FSBuild to the above folder (I had moved it away first to make room for the Wilco/FT 737 FMC generated file) after renaming the one created by the Wilco/FT 737 FMC.
Started FSX again. Tried to load the FSBuild-generated company route NZDNNZWN by typing in the route name into the scratchpad and pressing the LSK 2L, and got a message ROUTE NOT LOADED.
Exactly the same thing happened with another flightplan first created with FSBuild.
Somehow, there must be a difference between the files AAAABBBB.u10.fpl as exported by FSBuild and as saved by the Wilco/FT 737 FMC.
Ernie, would you have any idea what is going on ? I can send you the route files in both formats if this is something you would be having a look at. It may not be a priority for you to fix it, but I would very much appreciate at least a comment from you.
Cheers,
Emile.
|