Hi all,
I’d really appreciate any help in figuring out of where the data for the “Statistics” section comes from. Thank you!
+1
Seems that most aircraft in MSFS have 14,000ft as max altitude, as sort of placeholder. We did report this a while back, during dev beta.
I agree. There’s several places that statistics can be entered, and it’s not clear where each set is being used. And then there’s the issue that, when you have multiple sources of the same data, they tend to get out of sync since many developers are very lazy at filling in this information properly (they pretty much don’t). Please document how each data source is being used, and deprecate and remove the duplicate ones and use a single source.
Thanks,
Tom
P.S. Realizing that most developers don’t care about the details, I love fixing these fields and filling them in properly so I can keep my installation clean and consistent. Sadly, the data sources of the various fields are now mostly encrypted and now the aircraft definition has gotten so complicated I don’t know how to fix it anymore. I’m sure the flexibility might be nice for some planes. But… wow. Then the fact that I don’t know what data is used for what complicates the issue. Data is spread haphazardly, and non-proprietary data is mixed in with proprietary data, and because of that it’s all getting encrypted. This is one of the reasons I don’t purchase from the Marketplace.
I hope someday, when things settle down and the SDK gets better documented down to the details, I’ll be able to wrap my head around it all and make sense of it and be able to figure out how to wrangle it all into an organizational structure in my library that’s usable. Right now, it actually hurts to use 2024 given the library is a total mess, planes are named wrong as far as I’m concerned, choosing a livery is so complicated, and the whole thing is totally unorganized from my point of view. It may make sense to you, but not to me, not the way I want it organized, and the way I’ve been able to organize it for the last 40 years.
P.P.S I don’t mean to say I’m against encrypting the proprietary data like the model and flight model etc.. But this type of data, the statistics, the name of the plane, the classification of the plane, etc., there’s nothing proprietary about that and there’s no reason to encrypt that data. Why in the world is the aircraft.cfg file encrypted??? Sure, it used to contain flight model data, but that is no longer the case and there’s absolutely zero reason to encrypt it, it contains zero proprietary data. And why is it soooo hard to manage the registration number of a plane??? Please, there are some planes where the livery is of a real life plane where the registration number should be fixed (or at least should default to its real reg number). And the fonts that are used on planes in real life are infinite. The font used in FS is horrible looking, and it’s soooo hard to change it. Sometimes I just want to paint the registration number on the plane because it’s so unique, and in a totally different position from other planes. Please fix the atc_id problem! And maybe allow the Reg Data Plate to move around the surface of the aircraft and change size? (And that white plate for the non-user planes, I sure hope that’s gone).
PPPS. But, back full circle, yes, please… Please document where the statistics section data comes from (and the purpose of all the other places were we are told we need to put performance statistics data).
Hello @abarvalg
A dedicated page was added to our documentation:
Additional Aircraft Information
Regards,
Sylvain