Hi Dave - yes, I edited those files manually too, adding the missing runways at EIDW into the runways.xml file. The problem I found is this (or at least there may be others - but this is the brick wall that I hit): I ran MakeRunways.exe to get a clean copy of the runway files. I then ran PF3 db updater and, as expected, it ran fast and completed in 10 seconds or so. I then opened the csv file in MS Excel and saved it again, no changes. An Excel dialogue appears saying that certain features of the file will not be retained if you save in csv format. You can either continue and lose those features (whatever they are, the 'Help' option didn't help!) or save as a file such as xls or xlsx (which presumably PF3 wouldn't recognise).
When you run the PF3 db updater on an unchanged, but re-saved csv file, as above, it now runs far more slowly and ends with an Update Failed notice. I have no idea how to add data to the csv and save it without it resulting in a file PF3 rejects.
Then of course, you'd have to be pretty keen to edit the runways.xml file manually for every update - it requires lots of information, which I did for EIDW as an experiment, but it is clear that editing these files is not an option. And editing the PF3 files directly Dave? I am guessing that's no more feasible than what I tried.
Oh well, at least now I know! Unless the developer of PFEtoX-Plane can suggest something, or the developer of the MakeRunways for X-Plane does produce a version for PF3, then we've presumably reached a dead end. (Slightly annoying that PFEtoX-Plane, as payware, does not have the facility to update the PF3 database, which will gradually contain more and more errors as a result: I didn't realise that when I bought it: an annoyance rather than a deal breaker though. At least I can use PF3 in X-Plane with this plugin!).
Enjoy your Sunday!
Martin |
