Hello Kiek, again. A little big problem here.

[abranpuko 369]

Hello, I will try to explain myself because I have found some errors that could be harmful to the libraries. When I add a new library to "MyMultRegcodesFromAtcids.txt", it is indeed saved.

For example: Fuji Dream ERJ-175 1";JA09FJ 

But, in this same file, there is another JA09FJ, a little further down. This is because I did a massive modification of many titles. These modifications are due to the fact that, when the libraries change, sometimes some titles disappear, or must be modified, or one liverie pass from a tittle A to a title B...etc...

In this case, PSXT has kept these two, since the one below is: "Fuji Dream ERJ-175 6;JA14FJ,JA05FJ,JA09FJ" (the old version)

The same happens with, for example, hundreds of learjets, which I have registered with PVT, etc, etc, etc... Since PSXT now doesn't warn of replays or delete them, what am I supposed to do? Review the libraries one by one each time there is a modification? Sometimes there are airlines that have hundreds of "ids".

That psxt helped in the past to keep the libraries organized, was it a big problem? Thank you

[kiek 1,238]

10 minutes ago, abranpuko said:

 Since PSXT now doesn't warn of replays or delete them, what am I supposed to do?

No that is not true. PSXT tells you in info\OfflineRegcodes.txt what it has done. So it will warn you about clashes. It will also tell you which one remains.

The rest is up to you. You are the one that gives registration codes to livery titles. So you are responsible for doing it right.

 

Edited July 6, 2022 by kiek

[abranpuko 369]

Well, im sorry but, not exactly as you say.

why? because, on my : info/offlineRegcodes.txt, there is not any reference to Fuji dream airplanes. But the true is that their are repeting many times, because i read it on "MyMultRegcodesFromAtcids".txt.

 Another example: on the "Airlinedata.txt" that PSXT has...you can read this.

FDA;E170;Embraer170 FSL;JA01FJ,JA02FJ,JA04FJ
FDA;E75L;AIGAIM_RFSL_EMB-175_NWv3;JA05FJ,JA09FJ,JA09FJ,JA10FJ,JA11FJ,JA12FJ,JA13FJ,JA14FJ,JA15FJ,JA16FJ
FDA;E75S;AIGAIM_RFSL_EMB-175v3;JA03FJ,JA05FJ,JA06FJ,JA07FJ,JA08FJ

as you can see, JA05FJ and JA09FJ are repeated.

of course, every time i put a new liverie, i check all to try to do the less error but now, if i dont see them (its normal beause i have 7000 liveries), psxt dont is not warning me as before.

in this case, even the info\OfflineRegcodes.txt that you say,  didnt warn me with "fuji" and other:

Processing files in liveries\regcodes
   N250NV for Allegiant A320-200 CFMS 2, replaces Allegiant A320-200 CFMS 1
   N317CM for ABX Air 767-300 GE 1, replaces ABX Air 763PW 1
   JA709A for ANA 772ER PW 3, replaces ANA 772 1
   JA710A for ANA 772ER PW 3, replaces ANA 772 1
   N775AV for Avianca El Salvador A320NEO, replaces Avianca Colombia A320NEO 1
   N562AV for Avianca Colombia A320-200 CFMS 1, replaces Avianca Colombia A320 CFM 4
   N632AV for Avianca Colombia A320-200 CFMS 1, replaces Avianca Colombia A320 CFM 4
   XY-AIN for AirThanlwin ATR 72-500, replaces Air Thanlwin ATR 72-210
   XY-AIM for AirThanlwin ATR 72-500, replaces Air Thanlwin ATR 72-210
   YR-BMO for Blue Air 737-800, replaces Blue Air 738W 2
   F-HZFM for Air Corsica Airbus A320, replaces Air France A320 CFM 2
   B-6167 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6172 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6217 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6218 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6231 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6423 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6428 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6429 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-6431 for China Eastern Airlines A319 CFM, replaces China Eastern Airlines A319-100SL CFM 2
   B-HLW for Cathay Pacific A333 2, replaces Cathay Pacific A333 1
   B-LBJ for Cathay Pacific A333 2, replaces Cathay Pacific A333 1
   B-6183 for Chongqing Airlines Airbus A319-100 IAE, replaces Chongqing Airlines A319 CFM
   B-6187 for Chongqing Airlines Airbus A319-100 IAE, replaces Chongqing Airlines A319 CFM
   B-6409 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6408 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6209 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6208 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6203 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6202 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6201 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6200 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6195 for China Southern Airlines A319 CFM, replaces China Southern Airlines A319-100 IAE
   B-6190 for China Southern Airlines A319 CFM, replaces Chongqing Airlines Airbus A319-100 IAE
   A6-EIV for Etihad A320-200SL IAE 1, replaces Etihad A320-200SL IAE 2
   A6-EIT for Etihad A320-200SL IAE 1, replaces Etihad A320-200SL IAE 2
   A6-EIU for Etihad A320-200SL IAE 1, replaces Etihad A320-200SL IAE 2
   G-POWN for Jet2.com opb SmartLynx Airlines, replaces Titan Airways A321-200 CFM
   N650GT for Atlas Air 767-200 GE, replaces ABX Air 767-200 GE 4
   N651GT for Atlas Air 767-200 GE, replaces ABX Air 767-200 GE 4
   D-AKNV for Germanwings A319 CFM, replaces Eurowings A319-100 IAE 1
   D-AKNU for Germanwings A319 CFM, replaces Eurowings A319-100 IAE 1
   D-AKNT for Germanwings A319 CFM, replaces Eurowings A319-100 IAE 1
   D-AGWN for Germanwings A319 CFM, replaces Eurowings A319 CFM 1
   D-AGWM for Germanwings A319 CFM, replaces Eurowings A319 CFM 1
   D-AGWL for Germanwings A319 CFM, replaces Eurowings A319 CFM 1
   D-AGWF for Germanwings A319 CFM, replaces Eurowings A319 CFM 1
   D-AGWE for Germanwings A319 CFM, replaces Eurowings A319 CFM 1
   TF-FIW for Icelandair B757-200WL 1, replaces Icelandair Cargo 757-200F 2
   EI-IMS for itaairways  A319 1, replaces itaairways  A319 2
   C-GOJZ for Jazz air CRJ-900LR 2, replaces Air Canada Express CRJ-900LR 1
   C-GFJZ for Jazz air CRJ-900LR 2, replaces Air Canada Express CRJ-900LR 1
   C-FTJZ for Jazz air CRJ-900LR 2, replaces Air Canada Express CRJ-900LR 1
   C-FUJZ for Jazz air CRJ-900LR 2, replaces Air Canada Express CRJ-900LR 1
   C-GLJZ for Jazz air CRJ-900LR 2, replaces Air Canada Express CRJ-900LR 1
   VQ-BEN for Azur Air Russia 763PW, replaces Azur Air 763W PW 2
   N363CM for Mas Air Cargo 767-300 GE, replaces ABX Air 767-300 GE 1
   ES-ACC for Nordica CRJ-900LR, replaces Xfly CRJ-900LR
   ES-ACD for Nordica CRJ-900LR, replaces Xfly CRJ-900LR
   D-AIKD for EurowingsDiscover A333 RR 1, replaces Lufthansa A333 RR 3
   VP-BFB for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHC for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHD for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHQ for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHR for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHT for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHU for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHV for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHW for Pobeda 738W 1, replaces Aeroflot 737-800 2
   VQ-BHX for Pobeda 738W 1, replaces Aeroflot 737-800 2
   LN for SAS Scandinavian Airlines 737-800 1, replaces NorwegianAirShuttle 738W 8
   ES-ACJ for Scandinavian CRJ-900LR, replaces Xfly CRJ-900LR
   ES-ACN for Scandinavian CRJ-900LR, replaces Xfly CRJ-900LR
   VQ-BRA for S7 Airlines A32N, replaces Azur Air Russia 763PW
   EC-KKQ for uepfly opb Swiftair ATR 72-600, replaces Swiftair ATR 72-500F 1
   TC-JFM for AnadoluJet 738W 1, replaces Turkish Airlines 738W 2
   TC-JHC for Turkish Airlines 738W 4, replaces AnadoluJet 738W 1
   TC-JHE for Turkish Airlines 738W 4, replaces AnadoluJet 738W 1
   JA822J for Zipair 787-8 2, replaces Zipair Tokyo 787-8
   JA826J for Zipair 787-8 2, replaces Japan Airlines 788 1
   JA825J for Zipair 787-8 1, replaces Zipair Tokyo 787-8
   liveries\regcodes\MyMultRegcodesFromAtcids.txt: 16172 new regcodes added, 81 regcodes replaced

   liveries\regcodes\MySpecialRegcodes.txt: 191 new regcodes added, 232 regcodes defined as special

 

i reallty appreciate your help.

[kiek 1,238]

1 hour ago, abranpuko said:

as you can see, JA05FJ and JA09FJ are repeated.

Well, simple, then you have to remove one...  Sorry, but you should do your book keeping yourself! I cannot help you with it.

1) PSXT has given you your history with respect to your use of multiple regcodes (with the file "MyMultRegcodesFromAtcids.txt") . If there are problems in that part, then they have been there already all the time!

2) If you add a new registration code with the Offline method, it is your responsibility to do that right.

 

 

 

[abranpuko 369]

Thanks for the info.
We users, especially the most faithful, are grateful for your free work. I would have no difficulty (I have always said it) in paying for what you have done.
On the other hand, I am also happy that our testimonials help you to evolve, without it, impossible.
In this team that we form, it is strange to notice how there is something cold (suddenly) in the words you write. The decision to change what PSXT used to do is yours, of course.
Consequences don't...
I say this because, every time a user enters some data incorrectly (which is very logical because there are thousands and thousands of "atc---id"), we will have to become software scholars and prevent errors from occurring.
That means more in the long run, that PSXT will be full of bugs all the time and airports will be full of mismatched libraries.

If the program is made to realistically fly (as you advertise) libraries in airports and skies...then the mistake would be that we are going to spend much more time fixing them than enjoying them.

Even spending the time (I've been 10 years or more) updating libraries and cleaning bad data with the old PSXT, there were still bugs that slipped by. Because we are human and not machines. That's what software is for.

Still, if that's stressful for you, you're within your rights.
Thanks.

[kiek 1,238]

I still don't see why you are complaining.

PSXT still supports multiple registration codes.

The only change is from inline via atc_id's to offline via text files.

The results of the old inline way via atc_id's is still saved for you in the file MyMultRegcodesFromAtcids.txt. So nothing is lost.

A major advantage of the new offline method is that we can share these files, so not everone has to spend time assigning regcodes. It looks as you have completely missed the work done by vHaaland and Voske for AIG in MSFS. About 400 users now use multiple regcodes fir AIG aircraft without having to spend 1 minute on it.

By the way you are in the top league of people I spend time on responding to questions ...

 

 

Edited July 6, 2022 by kiek

[abranpuko 369]

Quote

I still don't see why you are complaining.

PSXT still supports multiple registration codes.

The only change is from inline via atc_id's to offline via text files.

The results of the old inline way via atc_id's is still saved for you in the file MyMultRegcodesFromAtcids.txt. So nothing is lost.

A major advantage of the new offline method is that we can share these files, so not everone has to spend time assigning regcodes. It looks as you have completely missed the work done by vHaaland and Voske for AIG in MSFS. About 400 users now use multiple regcodes fir AIG aircraft without having to spend 1 minute on it.

I am not complaining, and I am not an AIG user.
Simply, so that your software evolves, I inform you of the possible errors that may exist. That's why creator and user are a team. Right now, "MyMultRegcodesFromAtcids.txt" is not doing its job properly because it doesn't record data and doesn't report duplicate data. That's the truth, I did it just to help, not to annoy you or take your time.

I am also using time of my life to write to you so that the software evolves.

Quote

By the way you are in the top league of people I spend time on responding to questions ...

Thank you. But I'm not looking for a relationship...it's just a contribution from a user.😎

[kiek 1,238]

15 hours ago, abranpuko said:

 Another example: on the "Airlinedata.txt" that PSXT has...you can read this.

FDA;E170;Embraer170 FSL;JA01FJ,JA02FJ,JA04FJ
FDA;E75L;AIGAIM_RFSL_EMB-175_NWv3;JA05FJ,JA09FJ,JA09FJ,JA10FJ,JA11FJ,JA12FJ,JA13FJ,JA14FJ,JA15FJ,JA16FJ
FDA;E75S;AIGAIM_RFSL_EMB-175v3;JA03FJ,JA05FJ,JA06FJ,JA07FJ,JA08FJ

as you can see, JA05FJ and JA09FJ are repeated.

That's the result of  scanning all your  valid iveries.

Checking regcode clashes takes place later, that's why duplicate use is not filtered out yet in AirlineData.txt

 

Note that it is technically speaking  impossible to map a regcode to more than one livery title, so PSXT will always choose one.

It will/should report the clash in the info\OfflineRegcodes.txt file. If that is not the case, then there is a bug. Maybe you can give a complete example?

 

Edited July 7, 2022 by kiek

[abranpuko 369]

1 hour ago, kiek said:

That's the result of  scanning all your  valid iveries.

Checking regcode clashes takes place later, that's why duplicate use is not filtered out yet in AirlineData.txt

 

Note that it is technically speaking  impossible to map a regcode to more than one livery title, so PSXT will always choose one.

It will/should report the clash in the info\OfflineRegcodes.txt file. If that is not the case, then there is a bug. Maybe you can give a complete example?

 

Thank you very much. Of course, I'll do a full library and id change process and check them to see what changes occur. And I will notify you.
Thank you very much for the support

[abranpuko 369]

Well,  To carry out the test, I have decided to add a new livery, in this case from EL AL, the 789, and, therefore, a modification of the "atc-id" line.

1) On aircraft-cfg, i had this [fltsim.7]:

[fltsim.7]
title=El Al 787-9 1
model=ELAL\4X-EDE
texture=ELAL\4X-EDE
atc_parking_codes=ELY
atc_parking_types=GATE
icao_airline="ELY"
ui_type=B789
atc_id=4X-EDA,4X-EDB,4X-EDC,4X-EDD,4X-EDE,4X-EDF,4X-EDH,4X-EDI,4X-EDJ,4X-EDK,4X-EDL,4X-EDM
isAirTraffic=1
isUserSelectable=0

2) and now add this:

[fltsim.8]
title=El Al 787-9 2
model=ELAL\4X-EDF
texture=ELAL\4X-EDF
atc_parking_codes=ELY
atc_parking_types=GATE
icao_airline="ELY"
ui_type=B789
atc_id=4X-EDF
isAirTraffic=1
isUserSelectable=0

As you see, l introduce the new retro library: 4X-EDF

(Of course, i know its an special "id" but, for this test, im going to treat it like a normal added livery.

3) following your recommendation, I create a .txt called: "Mytraffic-Abraham.txt" and paste this:

El Al 787-9 1;4X-EDA,4X-EDB,4X-EDC,4X-EDD,4X-EDE,4X-EDH,4X-EDI,4X-EDJ,4X-EDK,4X-EDL,4X-EDM
El Al 787-9 2;4X-EDF

4) When i start PSXT, i discover that the ancient "El Al 787-9 1" (with: atc_id=4X-EDA,4X-EDB,4X-EDC,4X-EDD,4X-EDE,4X-EDF,4X-EDH,4X-EDI,4X-EDJ,4X-EDK,4X-EDL,4X-EDM is not deleted from "MyMultRegcodesFromAtcids.txt".

5) So now, i have two different EL AL liveries: the one from "Mytraffic-Abraham.txt" and the other from the past on "MyMultRegcodesFromAtcids.txt"

6) So, So obviously I proceed to open "MyMultRegcodesFromAtcids.txt" and delete the ancient EL AL.

7) After doing that, all is good. But, at the same time, i go to PSXT_MSFS / info /AirlineData.ext, and discover this:

ELY;B789;AIGAIM_UTT_B787-9_RR;4X-EDF

😎 There is nothing about EL AL on "OfflineRegcodes.txt"

So, 4X-EDF is added, but not the other 11 liverys

9) In summary:

- PSXT works well as always except from now on I know I'll have to go into "MyMultRegcodesFromAtcids.txt" and delete the old livery, and put this one in. Or simply delete it because I have already created a new ".txt" (Mytraffic-Abraham.txt)

- I dont know if it is a bug, but "AirlineData.ext," doesnt save the new changes, as i showed you.

- It would be great to at least have the liveries arranged alphabetically in "MyMultRegcodesFromAtcids.txt" by the time many new liveries have to be added. 

---------------------------------------------------------------------------

Well, I hope I have been able to take the proper steps to do this check. And have contributed to help.
Thanks Kiek for the help and tell me what I've done wrong.
A hug!

[kiek 1,238]

5 hours ago, abranpuko said:

3) following your recommendation, I create a .txt called: "Mytraffic-Abraham.txt" and paste this:

El Al 787-9 1;4X-EDA,4X-EDB,4X-EDC,4X-EDD,4X-EDE,4X-EDH,4X-EDI,4X-EDJ,4X-EDK,4X-EDL,4X-EDM
El Al 787-9 2;4X-EDF

That's not good. The line with ElAl787-9 1 is already in your "history", the file "MyMultRegcodesFromAtcids.txt"

You only need to the define the new livery ElAl787-9 2  (you are talking about a library, but I guess you mean livery)

If you put your new file, below the other file (by giving it such a name that it is lower in alphabeticcal order, in your example that's ok), the regcode for the new livery will replace the old one in your history.

However, you could also insert the new livery in your history file after EL787-9 1, then the regcode will be set to the new livery and not to the older one. That's a lot easier and safer.

 

EDIT: I have not studies the rest of your example, you better re-start with this change first.

Edited July 7, 2022 by kiek

[abranpuko 369]

1 hour ago, kiek said:

That's not good. The line with ElAl787-9 1 is already in your "history", the file "MyMultRegcodesFromAtcids.txt"

You only need to the define the new livery ElAl787-9 2  (you are talking about a library, but I guess you mean livery)

If you put your new file, below the other file (by giving it such a name that it is lower in alphabeticcal order, in your example that's ok), the regcode for the new livery will replace the old one in your history.

However, you could also insert the new livery in your history file after EL787-9 1, then the regcode will be set to the new livery and not to the older one. That's a lot easier and safer.

 

EDIT: I have not studies the rest of your example, you better re-start with this change first.

In agreement. So from now on, I will not create a new "txt" file for the new liveries, but I will always add them in "MyMultRegcodesFromAtcids.txt" in the way you tell me

Thanks again.)