Runway distance remaining signs have never been part of any stock MSFS objects. Ever. I agree that it’s a rather big omission. Even the ability to create them in the taxiway sign editor (white text on black backgrounds) would be a simple start point.
Simply put, as evidenced by other threads, there is very little in the way of fidelity for airport details, especially the differences in the three sets of standards that govern most of the world’s airports. And it’s a subject that most people don’t know or don’t care about, despite efforts to educate or raise awareness.
1 Like
For U.S. airports, send them a copy of FAA Advisory Circular 150-5345-44K
SPECIFICATION FOR RUNWAY AND TAXIWAY SIGNS
(Which they won’t read) 
1 Like
I find it somewhat laughable that Microsoft/Asobo go so far out of their way to create a realistic flying experience, yet punt on the departure and destination points of those players.
Ah well. back to figuring out how to light a sign in Blender. Enough venting for one day.
I posted AC150/5340-1M in my runway markings wishlist almost two years ago and there’s been no progress.
In fact, I’ve been doing an audit of the world’s airports to see which standard each country follows. The funny thing is there are exactly zero airports that use the precision runway markings as found in the sim. Touchdown zone markings are either 3 - 3 - 2 - 2 - 1 - 1 stripes per side (with a few variations usually based on runway length) or just one per side all the way through. This is true for more than 90% of the airports you might consider “standardized” across many countries. But in the sim it’s a weird 1 (then aimpoint) then 2 - 2 - 1 - 1, omitting the 3-per side completely.
That’s before we get into runway numbers, which are hilariously small for many countries, including France.
At this point, at minimum I just want a switch to edit these independently in the SDK. Then we can fix them in world hub so it’s not a drain on Asobo’s resources.
The ability to scale/select alternatives would be great. They allow you to switch between a NA and EU form of those runway markings, but I don’t know how accurate the EU markings are. Thee NA markings appear to be a bit smaller than the actual markings when you compare the photogrammetry to what the SDK drops down.
It’s a bit complicated. For one, the FAA markings stand alone (but comprise 1/3 of the world’s airports, so a substantial chunk). But it’s very standardized and there aren’t a lot of outliers when you compare one public airport to another (private strips are a different matter).
For the rest of the world, I’ve seen two major configurations, but the big variability is the aimpoint markers. In the US, those are fixed at 1000’ and always replace what would be the second touchdown zone marker. Whereas rest of world, they’re variable and independent of the touchdown zone markings. The ROW also uses metric distances in most cases, versus imperial for the US (and they’re “close enough for jazz” in most cases, but not for purists).
Other variabilities from country to country (even airport to airport) include centerline stripe width and spacing, and runway designator number size. I’m trying to audit and catalog some of these findings to see if there are some presets that would cover, say, 70% of the world’s airports. Then give us the tools to independently adjust where necessary.
So, along with signage and taxi markings, I think this is all worthy of a lift.