Test version 3.2.0.143 * NEW 08/10/2017 *

[normandean]

Hi Tim, I have now found why the UK2000 airports are not loading for me. I have installed them using the new P3D system with addon xml files, and Plan G is not searching for those. I did not point to the location of ach individual airport, but only to the UK2000 scenery folder. When I tried again just pointing at Gatwick it was picked up OK. What I don't understand is why the FSDT airfields, loaded by the same method, were found and yet Tallin, also loaded this way, was not.

Log file attached.

Norman

Edit: I was wrong, the FSDT airports are not being found.

[tim arnot]

Hi Norman, Could you please try the attached build? It should now be working properly with the scenery_add-ons.xml file.
Please remove the entries from your Plan-G AdditionalSceneryLocations.

The Attachment contains only the .exe file, so back up your existing exe and unzip over the top.

Let me know how you get on.

[normandean]

OK I'm, will report back.

Norman

[normandean]

Hi Tim, well, some success. I now have the UK2000 airfields 9n the map, and also Tallin, but I am unsure about the FSDT airfields because although some show as addons and airport diagrams appear similar to the model layouts, others are not so represented. It could be that airfields in the FTX LC are showing instead.

Log file attached.

Norman

[tim arnot]

Thanks Norman. This should fix those last remaining airports. (somehow the line that checked the path didn't already end in \scenery didn't get copied to the new code block  :-[ )

Please delete your log file before doing the next run - it's getting kinda large!

[normandean]

Thanks Tim, its my wedding anniversary today so I will report back later or tomorrow.

Norman

[tim arnot]

Happy anniversary!  8)

(Don't expect a quick answer after today - I'll be heading up to Cosford for the show . . .)

[normandean]

Hi Tim, everything now works out fine. Log file attached.

Enjoy the show

Norman

[tim arnot]

 :c017:

[dempsey]

Tim,

Upgraded to 3.2.0.142 and rebuilt the database from X-Plane 11.05r5.

CYBW ILS loc is still 343^o and thus wrong. CYKA (Kamloops) ILS is still 85^o and should be 87^o.

Attached the log file. What surprises me is that you process earth_awy.dat from Default Data (AIRAC 1611) rather than from Custom Data (AIRAC 1710).

[opjose]

Hmm... Mine attempts to build from Custom Data... see below, but does later go to the older 1611 later in the process.

Of course it fails building intersections and the latest version still doesn't show the X11 data from the posted file.

---

20:02:03.3 Building database for X-Plane. Folder is: D:\Program Files (x86)\Steam\steamapps\common\X-Plane 11
20:02:03.3 Preparing database for new data
20:02:03.3 Erasing
20:02:03.4 Creating Data Source = F:\Users\Jose M. Sanchez\Documents\Plan-G Files\Data\PlanG3_XPX.sdf
20:02:03.6 Scanning usa.txt
20:02:03.6 Writing 0 Airspace Boundaries
20:02:03.8 Hand-placed localisers earth_nav.dat found.
20:02:03.8 Scanning D:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Data\earth_nav.dat
20:02:03.9 Decoding D:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Data\earth_nav.dat
20:02:03.9 PC format
20:02:03.9 1100 Version - data cycle 1710, build 20170901, metadata NavXP1100. Copyright (c) 2017 Navigraph, Datasource Jeppesen
20:02:04.4 CPT
20:02:04.5 EGTK
20:02:05.4 Scanning D:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Data\earth_fix.dat
20:02:05.4 Decoding D:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Data\earth_fix.dat
20:02:05.4 PC format
20:02:05.4 1101 Version - data cycle 1710, build 20170901, metadata FixXP1101. Copyright (c) 2017 Navigraph, Datasource Jeppesen
20:02:30.9 Scanning apt.dat
20:02:31.0 Decoding D:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Scenery\0KGNV\Earth nav data\apt.dat
20:02:31.1 PC format
20:02:31.2 Decoding D:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\Custom Scenery\26N Ocean City NJ Municipal Airport\Earth nav data\apt.dat

[Gunduran]

Hi Tim,

Thanks for the answer and the first implementation.

Unfortunately, it only works, if a well defined data base already exist. You can't come to the Options folder if there is no data base found as the only allowed actions are to Generate a new Data base or to use the data tools....
So please add a "path" setting field directly on the "Generate Database" screen otherwise it will drive us in circles.

Thanks.

Best wishes
Detlev

I would prefer, to be able to select a data path individually before creating the data base!

P.S. As a data Provider I use Navigraph.

You can. :) This was added to the current build (see the notes). Change the path in Settings->General, and restart Plan-G.

[tim arnot]

OK, wilco.

[tim arnot]

Hmm... Mine attempts to build from Custom Data... see below, but does later go to the older 1611 later in the process.

Of course it fails building intersections and the latest version still doesn't show the X11 data from the posted file.

Can you attach the full log for that, cos it shouldn't.

[tim arnot]

What surprises me is that you process earth_awy.dat from Default Data (AIRAC 1611) rather than from Custom Data (AIRAC 1710).

Spelling error!  :-[