


And why under "aircraft type" dropdown list we can get all sorts of funky stuff listed, like "Comercial Airlin" when a developer mis-spells "Commercial Airliner" for the variable "ui_typerole" which is what is used for that dropdown list. Thats why under the publisher drop down you will get "unknown" because they leave out the ui_createdby= variable. Hope you don't have too many!Ī lot of free plane developers (just average joes like you and me) don't understand what each of the ui_# variables are or really do and either don't put them in at all or mess them up. Then you can easily identify the other plane(s), (in your case its probably another C-152) and then decide which one(s) you want to ultimaly change or keep as the original text), or you can just suffer with finding it amongst all the variations. These variables are only for this list and do not affect anything else so open your new planes aircraft.cfg with notepad and find ui_type=, and change whatever it is to something unique, perhaps just add a -2 to the end of whatever is there and then you will see it show up on the main list. And the list becomes way too large to eyeball search when displaying all variations for all planes, all the time. I do this because I sometimes forget that a unique plane exists. Afterall they ARE unique planes even if of the same type. When that happens to me I identify which other aircraft has the same text for that variable and I change one (or more if there are more) of them to something unique to make them both or all of them show up on the main list. If two completly different aircraft have the same text for the variable "ui_type" in their aircraft.cfg file it treats both planes as if they are the same plane with the ones it reads after the first considered a variation, (as long as the variable "ui_variation=" is unique in each, otherwise it will probably crash).


But turns out, thats not all its logic does. Its confusing because the average person would think that the "show all variations button" is only for displaying the different paint jobs (textures) for each unique plane. Probably whatever is the first one it reads when we click the change aircraft button. How it decides which one it will show on the main list and which one it will treat as a variation I don't know. Or more planes have the same text, say "C-152" for that variable, then only one of them will show up in the main display, any others will only show up when the "show all variations" box is checked. It is also what distinguishes whether or not a plane gets listed as a unique plane in the initial list or not. The text past that equal sign is "part" of the text that gets displayed below the aircraft thumbnail. There are several variables within all aircraft.cfg files related to the user interface and the drop down lists, including one called "ui_type=".
