Gokul
commented
in reference to scenery pack
55514on September 26, 2017 7:38 AM
Started with the Gateway bot version (USER123) as a base.
Used government published AIP GPS position details to adjust the tower, beacon, the four PAPI positions (two each for 18 and 36), wind sock. Also, cross-referenced these with google earth orthos.
Also used orthos and AIP to position:
runway turnaround areas on both ends,
old, disused, runway turnarounds on both ends (marked with X),
windsock and its base,
radar installation east of the airport lagoon,
ramp flood lights,
fuel depo,
static aircraft (i had to cut back a lot from real life on these),
taxi lines and signs (these are accurate according to the AIP and orthos),
taxi shoulders (dirt) with shoulder markings,
lit and unlit taxiways based on published AIP,
runway hold short lines,
airport vehicle roadways west and east of the apron also follow the orthos.
Tried to match the numerous apron, taxi, runway shoulder and turnaround areas’ surface types with the reality of the airport surfaces (built up organically with various materials…)
In addition to all the static aircraft, there are taxi flows throughout. Fuel, cargo, crew and catering vehicle flows are present, along with parking, destination, etc. And airport flows and rules are implemented (for ATC AI), including a catchall.
There is no established helipad so i positioned heli ramp starts in the north apron.
The runway is notoriously rough. An Emirates flight damaged it gear on landing. Runway roughness is set to 1.0.
Unfortunately the runway markings are non-standard at VRMM and X-Plane cannot replicate them in the default WED options. The closest one is “Non-Precision (US)”. which was used.
Density setting was left at “Default” for everything for the time being.
And finally, if the airport seems haphazard and messy, thats intentional! The real thing is much worse...
Started with the Gateway bot version (USER123) as a base.
Used government published AIP GPS position details to adjust the tower, beacon, the four PAPI positions (two each for 18 and 36), wind sock. Also, cross-referenced these with google earth orthos.
Also used orthos and AIP to position:
Tried to match the numerous apron, taxi, runway shoulder and turnaround areas’ surface types with the reality of the airport surfaces (built up organically with various materials…)
In addition to all the static aircraft, there are taxi flows throughout. Fuel, cargo, crew and catering vehicle flows are present, along with parking, destination, etc. And airport flows and rules are implemented (for ATC AI), including a catchall.
There is no established helipad so i positioned heli ramp starts in the north apron.
The runway is notoriously rough. An Emirates flight damaged it gear on landing. Runway roughness is set to 1.0.
Unfortunately the runway markings are non-standard at VRMM and X-Plane cannot replicate them in the default WED options. The closest one is “Non-Precision (US)”. which was used.
Density setting was left at “Default” for everything for the time being.
And finally, if the airport seems haphazard and messy, thats intentional! The real thing is much worse...
can somebody update it with new runway??
Seaplane terminal requires 'gates' for docks.