X-Plane: Bogus model variations offered for C172
Posted: Sun Apr 03, 2022 9:16 pm
While trying to substitute the default singleprop model with something for ICAO code "C172" I noticed the field "Select a variation" is offering me a huge list of totally unrelated models to choose from:
Among the models in the list are also Laminar's default aircraft such as the F-4.
I presume this is caused by a missing ICAO code in the scanned .acf's as seems to be the case for example for the default F-4 when its "Author" info is displayed in Planemaker:
Now, I didn't have the patience to verify this for all the models in the list but assuming my conclusion is indeed correct it looks like the only way to fix this would be to open each .acf and fill-in that missing bit of info by hand and re-save - which could take a loooong time and is at risk of getting overwritten with each X-Plane or custom aircraft update...
Frankly, if my conclusion is indeed correct I think it would be much better if JFS assigned a unique and potentially "fictional" type code to generated CSL models whose source models don't provide that info in their metadata as this would prevent the C172 to serve as a "catch-all" container for misconfigured/lacking .acf's...
So, 3 questions:
Among the models in the list are also Laminar's default aircraft such as the F-4.
I presume this is caused by a missing ICAO code in the scanned .acf's as seems to be the case for example for the default F-4 when its "Author" info is displayed in Planemaker:
Now, I didn't have the patience to verify this for all the models in the list but assuming my conclusion is indeed correct it looks like the only way to fix this would be to open each .acf and fill-in that missing bit of info by hand and re-save - which could take a loooong time and is at risk of getting overwritten with each X-Plane or custom aircraft update...
Frankly, if my conclusion is indeed correct I think it would be much better if JFS assigned a unique and potentially "fictional" type code to generated CSL models whose source models don't provide that info in their metadata as this would prevent the C172 to serve as a "catch-all" container for misconfigured/lacking .acf's...
So, 3 questions:
- Is anybody able to reproduce this behavior on their end?
- Does JFS indeed assign default ICAO "C172" when it can't find that info for scanned models?
- Ideas for a better workaround than hand-editing the acf's one by one?