Any plans to make the DME associated with an ILS omni-directional (as in real life)?
Currently this DME only works in a 180° arc along the direction of the ILS. Some IAPs use ILS DMEs for non precision approaches on the same runway but on the non-ILS end. Currently such procedures can’t be used in MSFS due to this DME limitation.
Any plans to increase the permissible range of an ILS DMS/LOC beyond approx 27 NM?
Many real life ILSs have a much longer range but MSFS seems to have this as a hard coded limit for all ILSs.
Is there any possibility that developers for commissioned hand crafted airports for World Updates be encouraged to ensure all such airports are functional in an aviation sense as well as looking good?
Issues that sometimes arise include incorrect taxiway paths/hold short placements that reduce the ability of these airports to work with live traffic or sim injected AI traffic.
Sometimes terraforming by the developer also reduces airport functionality. Eg EDDS, Stuttgart, has a sloping runway in real life. In MSFS it has been “flattened”. The result is a threshold for RWY 25 that is over 100 feet higher than what it should be, leading to it being impossible to use a correct ILS GS for autoland as the new “touchdown” zone is before the runway threshold among the approach lights.
Living World Configuration controls what vehicles are available for use on airports. Unfortunately, it is region based on the scale of countries. This places fire trucks and buses and many other vehicles on small ga airports that would never or at least would very rarely see them.
While we are allowed to create new Living World config files, those files change the whole region.
Since the sim was pretty much released there has been a request that, like “Airport Services”, Developers be allowed to create airport specific Living World configuration files. Has there been any thought put into this feature request? Can we expect such a thing at some point?
Maybe allow Airport Services some feature that can override the Living World Configuration file.
Bespoke airports with bridges seem to cause a lot of crashes when taxiing on them. There seem to be two issues: Sometimes there are invisible holes that you fall through, and in other cases, terrain elevation changes create large gaps/lips that the aircraft cannot pass over. Do we have possible long-term solutions?
Different airports often have different suppliers of fuel than others. It would be cool if the fuel trucks and other sim object liveries could be controlled in the Airport Services file so airport specific changes could be made.
Is there any progress being made for autogenerated airports to ensure that runway approaches are free from trees/tall buildings that make landing a bit of an obstacle course?
Is it possible to introduce AI algorithms to add exclusion polygons to all AI generated airports for all runway approaches to ensure they are free from such obstacles?
One of the few areas where X-Plane has a scenery advantage over Flight Simulator is in its default autogen airports. The scenery gateway will help fix some issues, but my understanding is that won’t allow for new object models. Are there any plans to replace some of the hideous default terminal buildings (that look like apartment buildings with solid yellow windows)? See LaGuardia for a good example. Also, autogen airports badly need some night lighting in the ramp area.
Airports: When can we expect a general fix that avoids placement of trees near runways, especially in the final part of the approach zone? Example Venice Airport LIPZ, but you’ll find it all over the world:
Some of the POIs released in World Updates have very poor LODs (Level Of Detail), Devils Tower and the Dover Cliffs are two prime examples where they would not load up until you were practically on top of them and this was with LOD settings maxed out. These two examples have since been fixed to some degree (Dover Cliffs still not visible from Calais when they should be), but new ones are released with poor LODs in practically every world update.
So my question; What assurances can you give that POIs will have proper/better LOD support in the future? So that they are visible from long ranges and don’t just “pop” into view 5nm away, Thank you
Aircraft parking spots are sometimes oriented incorrectly (even 90 degrees from the direction they should be) and/or placed correctly. Will these be corrected?
when a RWY designator change happens in the AIRAC cycle and Navigraphs MSFS Database gets updated, the procedures associated with it get deleted in MSFS since it doesn`t allow Navigraph to change the RWY designators as well.
MSFS should not drop those procedures but keep them or allow Navigraph to change the designators according to the AIRAC cycle to solve that problem.
Latest examples SBGR, SVMI which had their designators changed.
Regarding airports (seems like a weather-engine question at first, but I’m not sure it is):
Will it be possible to let wet airport ground textures stay for longer after the rain stops? I’d really love to see some puddles even when the sun came out again after some rain…
Thanks!