Please add the following aircraft.cfg parameters as variables to SimConnect:
icao_type_designator
icao_manufacturer
icao_model
icao_engine_type
icao_engine_count
icao_wtc
icao_airline
These are important general parameters that describe aircraft and its capabilities in a standardized way used throughout the aviation sector.
Prior to FS2024, we could at least scan through the filesystem to read values directly from aircraft.cfg files, but with the simulator now locked down more than before and many files streamed on demand, this not a viable solution anymore.
Knowing these parameters is very important for all kinds of applications that depend on aircraft type. For example, our VDGS module uses ICAO type designator to select proper guidance method and show aircraft type on interactive docking devices.
Someone from Asobo can give some information on this @FlyingRaccoon?, if it is going to be added at some point or some feedback.
It is something much needed, it is also affecting software like Acars to log flights, it cannot read which aircraft the player is currently using accurately, with the ICAO (icao_type_designator).
You can only access atc_model, showing things as generic and unwieldy to make a direct comparison with the ICAO as this: ATCCOM.AC_MODEL_A320.0.text
Thanks by the answer!, If you would kindly take note, please, even if it is a low priority , although I suppose that being on the forum already takes that into account.
It can be challenging when there is no access to that aircraft information.
What I wonder is whether this is even a low priority issue, or whether you haven’t even considered it, and it will just die here in the forum.
There are several posts on the forum discussing this, including this request with 23 votes. I don’t understand why some developers have to create systems to read other parameters and try to deduce the icao_type_designator, for example, when it’s a value that already exists and is there, but it don’t make it accessible.
The previous example of missing an icao_type_designator SimVar, would force detecting the airplane type using unreliable heuristic from the ATC MODEL or TITLE SimVars,
Indeed. The ICAO values that describe the aircraft already exist in configuration files and are used internally by MSFS, but it seems like someone simply forgot to make these variables available through SimConnect when they were added to the sim, which makes the situation very disappointing.
The problem of not knowing which aircraft type the player is flying, or what types are around them, comes up all the time. Moving map displays need this information to show appropriate icons. Logbooks need it to record flight hours by type, and so on and on.
well ideally we’ll end up with some kind of architecture for the sim with access to basic things like variables, events and files not fragmented across different subsystems / languages.
Agreed. The ICAO type designator uniquely identifies the type, and is already part of the aircraft config. It’s just not exposed in a simvar. Aircraft Type Designators . All the vars that do exist aren’t nearly as useful.
I would like to point out that of all the aircraft I’ve purchased, I’d say 10% of authors fill in these variables correctly. Most make up their own values, even though the information to do them correctly is freely available. Also, there are many aircraft that aren’t listed in the ICAO database sadly, many of which are my favorite aircraft, lol. Requiring then it would be nice if there was some sort of standard for how to handle that eventuality for the sake of consistency in the sim. Be that as it may, I have no idea why it’s so hard for authors to fill in this information with the correct values.
Granted, it may be authors would be more likely to actually fill them out properly if the data were available for use?
That being said, I fully 100% support making this data available for use. I can’t imagine any reason it would not be available.
Most make up their own values, even though the information to do them correctly is freely available
That should be the developer’s responsibility; if you buy a product, it should come with the correct configuration files.
there are many aircraft that aren’t listed in the ICAO database sadly
I always manage to find all the ICAOs; otherwise, they can’t fly. They’re certified and assigned an ICAO code, if I’m not mistaken.
I always manage to find all the ICAOs; otherwise, they can’t fly. They’re certified and assigned an ICAO code, if I’m not mistaken.
Well, yeah…. I’m wondering why they don’t. Seriously, 1 in 10 get it right anecdotally. I have to edit it all the time. Of course, since MSFS uses that data, by editing it, am I screwing something up in terms of model matching as I imagine they record each plane that’s ingested into the Marketplace?
Maybe in Europe? In the U.S., they don’t care. For instance, there’s several Boeing P-26’s flying around, no ICAO designator, at least not in the official ICAO database. There’s tons more aircaft I’ve found over the years. Perhaps it’s not complete, but, you’d think they’d list it on their own page.
, although I suppose that being on the forum already takes that into account.