Inline reg overrule regcode-file now?

[vidha 91]

I just updated Transavia as you might have noticed. When in the sim, with the updated regcode-file and updated AIG Summer 2022 for Transavia, I noticed an inconsistency:

From offlineregcodes:  
===> single PH-HSK in off line file for title AIGAIM_Transavia Boeing 737-800WL - SN Sunweb, overrules reg PH-HSJ defined inline

From the log:
TRA633U  PH-HSJ    AMS->VLC TRA B738 =1= AIGAIM_Transavia Boeing 737-800WL - SN Sunweb


From the regcode-file:
AIGAIM_Transavia Boeing 737-800WL - SN Sunweb;PH-HSK
AIGAIM_Transavia Boeing 737-800WL - SN;PH-HSF,PH-HSG,PH-HSJ,PH-HSM,PH-HXA,PH-HXD,PH-HXE,PH-HXF,PH-HXI,PH-HXJ,PH-HXK,PH-HXL,PH-HXM,PH-HXN,PH-HXO

As you can see, the wrong inline PH-HSJ override the correct assignment from the regcode-file. Only PH-HSK should call the livery AIGAIM_Transavia Boeing 737-800WL - SN Sunweb, not PH-HSJ

Edited October 25, 2022 by vhaaland

[kiek 1,215]

Hi Vidar,

You've found a bug (long lasting..) Will be fixed in the next version.

Nico

[vidha 91]

Now it works. Thanks for the quick fix:

From log today:
TRA7U    PH-HSJ             TRA B738 =1= AIGAIM_Transavia Boeing 737-800WL - SN
 

[vidha 91]

This issue seems to have re-appered in latest version. 

Now inline-regcode overule my regcode-file instead of the other way around as it should:

 

As you can see here, these two reg-codes are on the same line in the regcode-file, but calls two different liveries.

From log-file:

AVA9722  N426AV    CLO->BOG AVA A320 =1= AIGAIM_Avianca Airbus A320-200 - CFM - Old Livery

AVA9759  N481AV    CTG->BOG AVA A320 =1= AIGAIM_Avianca Airbus A320-200 - CFM

From regcode-file "regcodes\AIG_Avianca_Summer_2021.txt"

AIGAIM_Avianca Airbus A320-200 - CFM;N230AC,N253AC,N281AV,N345AV,N401AV,N411AE,N411AV,N416AV,N426AV,N4304,N446AV,N451AV,N481AV,N538AV,N567AV,N664AV,N763AV,N862AV,N950AV,N951AV,N954AV,N955AV,N961AV,N980AV,N992AV

From AIG aircraft.cfg:

[fltsim.61]
title=AIGAIM_Avianca Airbus A320-200 - CFM - Old Livery
model=AVA-Avianca_CFM - Old Livery
texture=AVA-Avianca_CFM - Old Livery
atc_id=N426AV
atc_airline=AVIANCA
atc_parking_types=GATE,RAMP
atc_parking_codes=AVA
ui_manufacturer=Airbus
ui_type=Airbus A320-200
ui_variation=Aerovias Nacionales de Colombia S.A.(Avianca)
ui_typerole=Commercial Airliner
ui_createdby=Provided by: JB Filename: FAIB A320 Avianca Columbia FSX.zip
description=FAIB_A320-200_CFM-CFM(fs20)
isAirTraffic=1
isUserSelectable=0
icao_airline=AVA

 

[kiek 1,215]

I have not changed that part of the code to my knowledge. Will look into it when I am back home, Jan 21st. 

You can also check the info file about inline codes overruled by offline files in the mean time.

Edited January 15, 2023 by kiek

[kiek 1,215]

On 1/15/2023 at 7:54 PM, vhaaland said:

This issue seems to have re-appered in latest version. 

Now inline-regcode overule my regcode-file instead of the other way around as it should:
 

@vhaaland What does the info\OfflineRegcodes.txt file tell you about overruling the inline code?

 

EDIT: Forget it, I've found the -long lasting- problem ....For regcodes in a list (not just a single regcode) no check was performed whether the regcode already existed.

You will now see many more corrections due to your offline regcode files!

 

Changed this line in the Manual;

An offline specified single registration code overrules one defined in-line 

==>

An offline specified registration code overrules one defined in-line 

 

Edited January 21, 2023 by kiek

[vidha 91]

11 hours ago, kiek said:

@vhaaland What does the info\OfflineRegcodes.txt file tell you about overruling the inline code?

 

EDIT: Forget it, I've found the -long lasting- problem ....For regcodes in a list (not just a single regcode) no check was performed whether the regcode already existed.

You will now see many more corrections due to your offline regcode files!

 

Changed this line in the Manual;

An offline specified single registration code overrules one defined in-line 

==>

An offline specified registration code overrules one defined in-line 

 

Great that you found the problem and thank you for the fix!