Atc_id from aircraft.cfg is not used any more

Version: 1.1.7.0

Frequency: Consistently

Severity: Low

Bug description:

I don’t see a way for the aircraft to use the default atc_id value as defined in the livery FLTSIM section in aircraft.cfg. This was mainly used for real world liveries to display correct registration number without additional action from the user.

In the old simulator if the Tail Number field was left blank in the UI, the default id from aircraft.cfg
was used. So the user had a choice of using default number or his own customized one. But in the new sim this field cannot be left blank, it requires at least one letter input, which forces the custom reg numbers.

I’m posting it here in case it’s a simple UI bug and not a conscious design decision. Low priority, obviously.

1 Like

Hi Asobo team,

I’d like to add a +1 to this issue as well, but also mention that we’d like a way to specify atc_id for Modular SimObject liveries.

If these parameters would go in livery.cfg, I assume it would be in the [general] section? If so, would this apply to some of the other parameters that used to appear in the [fltsim.n] sections, like atc_airline, icao_airline, etc?

We’re preparing to launch a free update to our aircraft that makes it a Modular SimObject, and are in the process of recompiling over 700 liveries. If it is intended for modular liveries to support this feature, we would greatly appreciate some guidance, so we don’t need to update them again if this is changed.

For example:

[GENERAL]
name = "Easyjet 'Europcar' (G-EZPD)"

atc_id = "G-EZPD"
atc_airline = "Easy"
icao_airline = "EZY"

[SELECTION]
required_tags = "A320,CFM,SL"
2 Likes

Hello @some1 @DunNZ

This is fixed with SU2 beta 1.4.7.0.
Please have a look and let us know if this is good for you.

Regards,
Sylvain

Hi Sylvain,

Thank you! I can confirm this is working in 1.4.7.0 (both on the “identification” tab, and the ATC ID simvar).

Could you provide some guidance on where we should set atc_id for a Modular SimObject? I can’t see it mentioned in the livery.cfg documentation.

Cheers

Hello @DunNZ

It hasn’t made its way into the documentation and editor yet but you can redefine [FLTSIM.N] section in the livery.cfg file.
The following parameters are supported:

  • icao_airline
  • atc_parking_types
  • atc_parking_codes
  • atc_id

Regards,
Sylvain

2 Likes