Special Aircraft Service

Battlefield - Airborne - Tactical (BAT) => BAT Lounge => Topic started by: Chaoic16 on September 12, 2021, 04:31:44 PM

Title: Air.ini / plane.properities secondary aircraft name possible?
Post by: Chaoic16 on September 12, 2021, 04:31:44 PM
Hello everyone

As always, thank you for your time to answer my questions.

I have been pondering about this, is it somehow possible to give aircraft an alternative name?  For example, if I want to have an exported version of aircraft for a specific nation,  then aircraft would have an alternative name.

If it is not yet possible, I will post it it in a request post.

Cheers
Title: Re: Air.ini / plane.properities secondary aircraft name possible?
Post by: FL2070 on September 12, 2021, 04:38:50 PM
Yes. Here's an example:

air.ini
Code: [Select]
Bf-109G-6         air.BF_109G6 2                                g01   SUMMER
Bf-109G-6_2         air.BF_109G6 2                                g01   SUMMER

plane.properties
Code: [Select]
Bf-109G-6         Bf 109 G-6 #1
Bf-109G-6_2         Bf 109 G-6 #2

This is also partially used in the default ModAct 5.3 air.ini, in which air.Placeholder is referenced many times throughout with different names to denote different sections of the plane list. Note that you cannot differentiate between two references of the same plane class in missions, because missions refer to planes by their class name (air.BF_109G6) and not their air.ini name (Bf-109G-6 and Bf-109G-6_2). Unfortunately, to differentiate between two or more copies of the same plane, you'd need to create new classes for each variant, which would be a great way to run straight into the Java wall.
Title: Re: Air.ini / plane.properities secondary aircraft name possible?
Post by: Chaoic16 on September 12, 2021, 04:50:45 PM
Yes. Here's an example:

air.ini
Code: [Select]
Bf-109G-6         air.BF_109G6 2                                g01   SUMMER
Bf-109G-6_2         air.BF_109G6 2                                g01   SUMMER

plane.properties
Code: [Select]
Bf-109G-6         Bf 109 G-6 #1
Bf-109G-6_2         Bf 109 G-6 #2

This is also partially used in the default ModAct 5.3 air.ini, in which air.Placeholder is referenced many times throughout with different names to denote different sections of the plane list. Note that you cannot differentiate between two references of the same plane class in missions, because missions refer to planes by their class name (air.BF_109G6) and not their air.ini name (Bf-109G-6 and Bf-109G-6_2). Unfortunately, to differentiate between two or more copies of the same plane, you'd need to create new classes for each variant, which would be a great way to run straight into the Java wall.

That is noted.  I intend to have cloned aircraft with different names while having the same references. This is another great news!  I am back on re-working aircraft list for WAW and TGA projects.

About About having different references (class), that is noted. I will keep that in mind.  Thank you for the information.