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

@FlyingRaccoon This seems not to be working on the currently released SU2 version.

we’ve set the FLTSIM.0 entry in the livery.cfg of a modsimobject, it doesn’t get shown in the identification page when selecting that particular livery.

We even tried FLTSIM.1 and got the same result nothing is shoewn. Console reports back that tail number is blank.

Hello @Olympic260

My apologies, it appears these params are being searched in a [FLTSIM] section and not a [FLTSIM.N] section.
I will have this reviewed as I’m not sure this is what we want.

Regards,
Sylvain

1 Like

Hello Sylvain,

Has this been reviewed yet as to whether the section should be called [FLTSIM] as is currently searched by the sim or [FLTSIM.N] as written in the SDK documentation?

Best regards,
Ashleigh

Hello @ashturn

The section name will be [FLTSIM.N].
This is likely to get fixed with Sim Update 4.

Regards,
Sylvain

1 Like

Hi @FlyingRaccoon,

Any chance the simulator could support both? Effectively treating [FLTSIM], if present, as [FLTSIM.0].

Then we can continue to use [FLTSIM] and have it work today with SU2+SU3, and with SU4 and beyond.

Otherwise, we’re left with a choice of:

  • Use [FLTSIM] and have to update a lot of liveries when SU4 releases (painful for developers and users)
  • Use [FLTSIM.N] and have slightly broken liveries until SU4 releases (painful for users)
  • Use both in every livery.cfg, but this feels messy

Are there any other alternatives I’ve missed?

Cheers

Will there be support for atc_airline as well as atc_flight_number in the livery.cfg?

Best Regards
Jonas

Sorry to ping @FlyingRaccoon, do you have any suggestions for the dilemma mentioned in my post above?

Hello @DunNZ

I have forwarded your concern.
I agree SU4 should support the format used in SU3 to avoid any regressions.

Regards,
Sylvain

2 Likes

Hello @some1

This is fixed in SU4 beta and should support both formats.
Please check and let us know if this is all good for you.

Regards,
Sylvain

1 Like