The airports should now be placed in the 'airports' directory and no longer in the 'places' directly. All folders should also be lower case, without white spaces.
Problem definition**: User created airports outside the commercial DLC area's are not appearing on the map or search when created (following syntax info in several messages in this tread) in the folder '/scenery/airports' (for DLC areas there is probably al ready data in de new navigation folder). When these user created airport folders are moved to 'scenery/places' as airports in a lot of DLC packages at this moment, the some airports are visual on the navigation map or via search, but no navigation data (ORIG, RWY, DEP, ARR, APP, DEST) can be filled in for these airports, so no flight plan can be made.
Most of this day I was testing. I removed al the data in the DLC folders and user created areas, so I had a rather clean AFS2 configuration. (I have added my lm.log). I have downloaded 12 FScloudport airports mostly in Europe also some in US (Hawaii). I changed names of folders en tsc's in lowercase and checked other syntax. No airports appeared on the map except for those who where previous* in a DLC package, except for some bigger German airports ( Koln, Frankfurt). From 12 created airports only 5 are recognized during startup --> tm.log 2.88-tmworld_airports: supported airports: 295 (290 airport are in AFS2 us/ch areas)
When I moved the 12 user created airports to the scenery/places folders all the airports appeared on the map and in the search, but no navigation data (ORIG, RWY, DEP, ARR, APP, DEST) for the airports outside DLC area's could be filled in, so no flight plan can be made.
For airports within the DLC areas some data In the new folder navigation seems complementary for data in the tsc for example rwy info, parking locations and some info seems the come from the world_airport file because most airport names differ from sname of lname and ICAO gets extra airport information (for example AMS/EHAM).
No automatic modifications where made in the navigation folder when a new airport was created. Do airport developers have to do some extra conversion so basic airport information will be added to the navigation folder? I'm aware that not all airports will have DEP and ARR info ( SID/STARS).
Regards
Patric
* edited: (bad translation)
** edited Alpha 3 aug: line trough part that is working, extra text in Italic