Great idea. I’ll try that
Kahuna, are you using stock 1946 or any of the mod packs? The file "air.ini" has the info you need.
If you are using one of the mods you can get the entire list at:
* #SAS\STD\com\maddox\il2\objects
* #DOF3\STD\com\maddox\il2\objects
* #TGA3\STD\com\maddox\il2\objects
* #WAW3\STD\com\maddox\il2\objects
* #JTW3\STD\com\maddox\il2\objects
and something similar for other mod packs.
Assuming that you are talking about the planes to allow in homebases in DF, it uses the short code name which is the same as the name used for the Skin folders...
Here is a sampling:
He-100D-1 air.HE_100D 2 NOINFO g01 SUMMER
He-112B-0 air.HE_112B0 2 NOINFO g01 SUMMER
He-112B-1 air.HE_112B1 2 NOINFO g01 SUMMER
He-112B-2 air.HE_112B2 2 NOINFO g01 SUMMER
Bf-109B-1 air.BF_109B1 2 g01 SUMMER
Bf-109B-2 air.BF_109B2 2 g01 SUMMER
Bf-109C-1 air.BF_109C1 2 g01 SUMMER
Bf-109D-1 air.BF_109D1 2 g01 SUMMER
Bf-109E-1 air.BF_109E1 2 NOINFO g01 SUMMER
Bf-109E-3 air.BF_109E3 2 NOINFO g01 SUMMER
Bf-109E-4 air.BF_109E4 2 g01 SUMMER
Bf-109E-4/B air.BF_109E4B 2 g01 SUMMER
Bf-109E-4N air.BF_109E4N 2 g01 SUMMER
Bf-109E-7 air.BF_109E7 2 g01 SUMMER
Bf-109E-7Z air.BF_109E7NZ 2 g01 SUMMER
Bf-109E-7N air.BF_109E7N 2 g01 SUMMER
The short code is the first column. Note that for aircraft such as the Bf-109E-4/B, the Skin directory changes the "/" to "_" because you can't have a slash in a folder or file name.
Now, if you are looking for the code that goes into aircraft definition for an SP or Coop mission you need the second column which has the Java class name. You could use those in DF missions as well for MDS (Moving Dogfight Server) which is now compatible with later versions of IL-2 1946 and BAT mod packs.
And thank you for posting this request... it made me fix my code in the new UQMG project I am coding which relates to the Skin directories (the whole slash thing).