Jim thanks for your very usefull post on "unseen effects" but on Fxplanner forum seem that people are going to move airports "easily" this mean that shortly we will have many "afcad" file over the net that probably contains errors
Ugo
We don't have to wait for Airports to be uploaded to web sites with errors because it is happening right now.
The testing that I have done shows 80 percent of all airports that have been uploaded in most cases destroyed a perfectly working FSX default airport.
This is not do to the Utility used but carelessness and lack of knowledge on the designers part. However, a Utiltity that exposes many parts of a Airport then what is needed by less then a knowledgable designer allows for a greater margin of error.
The following list of errors comes from all the AFX Airports that I have downloaded and studied.
No standard bgl naming scheme
Duplicate Taxiway signs because of no exclusion
Duplicate Approach data in the GPS receiver based on False statements and copied into the User XML
Duplicate Scenery Library GUIDS nesting above the Airport header. Some uploads have more then 140 GUIDS
Duplicate audible markers sitting on top of each other
Duplicate Jetways do to False statements and then Jetways copied into the user XML
Jetways that lost there Parking assignment and now travel to the wrong Parking Spot
Parking spot and Jetways added to Terminals with no Aprons added so the Planes taxi on grass
Many Parking spots at the Main Terminal with Radius values set for GA Planes rather then B737/B757/B767/Airbus type planes
No Airline Codes in the parking spot
Parking Spots not connected to taxiway/Apron Links. One Airport uploaded this week has 22 out of 29 spots not connected.
AI Planes timing out and disappearing on pushback
Taxiways closed which is not honored by ATC
Boundary Fences that pass through Main Terminals and Airport Buildings
Boundary Fences that cross over each other do to vertex scramble that the compiler does not see as a error
Taxiway signs for Runway entrance (white letters over red background) used for other then runways
Apron Lighting no longer matching the deleted or resized Aprons
Animated Vehicle roads not attached to many Parking Path Links
Vehicle roads passing back and forth through Boundary Fences
Vehicle roads that are missing segments causing animated vehicles to default to main taxiways and runways
Taxiway segmentation destroyed
Many Blue Nodes not connected to anything
Taxi/Apron paths passing through default static ground vehicles
Hold Short nodes to far from the edge of the runway
Taxiways with Hold Short nodes entering the Blast Pad or Overrun causing AI Planes to time out.
Airline Terminal Parking spots coded as RAMP instead of GATE causing no animated Ground Support
Multiple Fuel Trucks parking side by side which FSX sees as a error and only one will be dispatched
Teeoff's missing completely including a line ending "T"
Parking Path center line missing so no oil stains are drawn on the aprons
There are 2 sides to every coin. Expose only what is needed (AFCAD concept) to enhance a FSX airport or expose everything in the form of XML. It ends up being a designers choice based on many factors that I don't want to go into at the present time.
Many new Users have found away to design FSX airports and run to upload their work to web sites regardless of any testing or proper knowledge. When e-mails are sent (as per their request) these same designers become very defensive and dismiss problems that other Users are experiencing with the enhanced non working airport.