schepma

Confused - suddenly frequent CTD with Real Traffic

Recommended Posts

Hi Nico,

as the title suggests,I'm a little bit confused. I have been using your excellent program for a quite a while now and never had any problems with it. I'm running P3D 4.5 together with the FLAi package.

But a few days ago, I noticed a CTD shortly after takeoff. At that time I had no idea what caused it. So I restarted the flight and it happened again, this time it occured while still standing at the gate. So I started troubleshooting. In addition to PSXT I have Active Sky and Aivlasoft EFB v2 running in the background. The installation of EFB v2 was a change in setup, so next time I didn't use it. But again, the CTD occured after a couple of minutes running Active Sky and PSXT. Then I stopped using Active Sky. And voilà, I was able to complete the flight. So I thought that I nailed down the issue. But the joy didn't last very long - on the return flight the crash occured again.

So I decided to stop using PSXT and turned Active Sky back on. No CTDs on many consecutive flights. Then I also turned EFB back on and again, no problems.

But as soon as I start PSXT, it is only a matter of time until a CTD occurs. This is really making me confused - I don't think that your software can be blamed for this because it is an external process running outside P3D (and it never crashed when P3D crashed).

I can only think of 2 reasons:

1) there might be a faulty aircraft in the FlAi package causing P3D to crash 
2) a Simconnect problem (maybe the parallel use of Active Sky and PSXT is flooding the Simconnect pipe? - but it never happened before)

Do you have any further ideas? The CTDs occured with versions 15.10 and 15.14, FlAi was updated to build 18, if I recall correctly.  Is there a way to scan the FlAi library for faulty aircraft or liveries?

Best regards,
Dirk

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi Dirk,

Post your Log.txt please. I think a livery could not have been  created, but you can find that info in the Log.

Did you have had a look at it?

Nico

Share this post


Link to post
Share on other sites
Posted (edited)

Hallo Nico,

This is also happening to me.  II am using FLAi, ASN and P3DV4.5.  I did  a couple of flight from EDDF to EDDB and in midflight a CTD.  On another flight from EDDF to EDDB I turned on PSXT mid way and then the flight continued without a hitch. Later I parked the plane on EDDF and then after some 15 minutes a CTD.  It looks to me that one of the AI planes is causing trouble.  I will post a log next time it happens.

Best regards,

--pim

Edited by pvrijald

Share this post


Link to post
Share on other sites
Posted (edited)

I checked the log files but there is no hint at all (I can post it if you want). There was only one livery which couldn’t be created (a CFG 767 with the reg. D-ABUK) and that occurred 10 minutes before the CTD. No other fault messages except that the connection to P3D was lost.

In the Windows 10 logs, a NTDLL error was recorded. 

I‘ll now update my NVIDIA drivers and reduce some settings first and then try it again. 

I still suspect a particular aircraft in the FLAi package, though. Perhaps it was created but incompatible? This would also explain Pim‘s observation as we were both flying in roughly the same region (the CTDs happened when I was flying from EDDK to EDDP and EDDG - EDDN). 

Best regards,

Dirk

Edited by schepma

Share this post


Link to post
Share on other sites
Posted (edited)

Remove the livery that could not be created from your Simulator, please.

Question for clarification: you are talking about a Simulator CTD, are not you?

Edited by kiek

Share this post


Link to post
Share on other sites

i have the same problem that P3D v4 is shutting down after 15 - 30 minutes on the ground.

how to remove the livery that can not be created ?

thanks,

Share this post


Link to post
Share on other sites
21 minutes ago, axel737 said:

how to remove the livery that can not be created ?

Delete the [fltsim.x] section with the livery title from the aircraft.cfg file for the aircraft type of the livery. 

Share this post


Link to post
Share on other sites

I have the same problem, and noticed on taxy out that one FLAi aircraft was black, but i didn't think to identify it. P3Dv4 crashed shotly after, second time of doing it.

Share this post


Link to post
Share on other sites
Posted (edited)
6 hours ago, axel737 said:

ok, is that in the traffic folder in psxseecon ?

No, in your FlightSimulator where the FLAi package is installed.....................

 and don't forget to renumber the [fltsim.x] sections so that they are consecutive (no holes). Their are tools for that to.

Edited by kiek

Share this post


Link to post
Share on other sites

Hi Nico,

regarding your question: yes, P3D is crashing, PSXT keeps running as if nothing happened. It is very stable, I think.

Maybe it's worth mentioning that the majority of aircraft which couldn't be created are 767-300. And most of them have a specific registration added to the AI_liveries.xml file, e,g,

    <livery airline="CFG" type="B763" folder="1" title="FLAi_B763_CFG-Condor NC D-ABUA" atc_id="D-ABUA" />
    <livery airline="CFG" type="B763" folder="1" title="FLAi_B763_CFG-Condor OC D-ABUK" atc_id="D-ABUK" />
    <livery airline="CFG" type="B763" folder="1" title="FLAi_B763_CFG-Condor Retro D-ABUM" atc_id="D-ABUM" />

Here's the relevant section of the log file:

Spoiler

*************************************** live traffic livery matching summary ***************************************

Tue Aug 20 21:21:34 2019 (utc)
165 liveries needed
67% (111) were completely matched, of which 1% (2) upon registration code (r), of which 100% (2) exact (R)!
16 liveries could not be created:
  CFG B763 "FLAi_B763_AJT-Amerijet N316CM"
  CFG B763 "FLAi_B763_CFG-Condor NC D-ABUA"
  CFG B763 "FLAi_B763_CFG-Condor OC D-ABUK"
  CFG B763 "FLAi_B763_CFG-Condor Retro D-ABUM"
  CFG B763 "FLAi_B763_DAL-Delta NC PW N198DN"
  CFG B763 "FLAi_B763_FDX-Fedex N68079"
  CFG B763 "FLAi_B763_UAL-United SA N653UA"
  CFG B763 "FLAi_B763_X N767S"
  CFG B763 "FLAi_B764_DAL-Delta ST N844MH"
  CFG B763 "FLAi_B764_UAL-United NC N77066"
  CFG B763 "FLAi_B764_UAL-United SA N76055"
  ELY B763 "FLAi_B763_ELY-El Al 4X-EAP"
  KLM E75L "FLAi_RAI_E75L_KLC-Cityhopper PH-EXG"
  KLM E75L "FLAi_RAI_E75L_RPA-Republic UAL N434YX"
  LOT E170 "FLAi_RAI_E75S_LOT LII SP-LII"
  MGL B763 "FLAi_B763_MGL-Miat JU-1021"
 =g= 17 generic liveries generated for unknown airlines
 =s= 10 liveries for airline and similar type generated
 =x= 18 random liveries for type
 =X= 9 random liveries for similar type

The missing liveries were for the following airlines and type codes:
  AAB CL35
  AFR E190
  AUA E195
  AZA E190
  BUC MD82
  CFG B763
  CND B738
  DLH A20N
  DLH CRJ9
  DLH E190
  EZY A20N
  IRA A332
  JAF B737
  KLM E190
  KLM E75L
  LGL CRJ7
  MGL B763
  MSR B789
  OHY A332
  PGT A20N
  SDR A320
  SWR E190
  SXS A320
  TFL A320
  TFL B738
  WUK A321
  WZZ A21N
********************************************************************************************************************

 

I don't know if this can crash P3D to crash, but perhaps it helps to further improve the model matching.

I'll now try to run PSXT with a different set of AI aircraft and see what happens. If there is no CTD in P3D, the fault must be somewhere in the FLAi package. As axel737 pointed out, I never had any problems until I installed the FlAi v18 package.

Best regards,
Dirk

Share this post


Link to post
Share on other sites

correct, also problems with the 767 liveries, as the post above.

but i also use the FlAi v18 since i started using psxseecontraffic and had never problems until now.

to Dirk : what other AI program do you also use ?

Share this post


Link to post
Share on other sites
11 hours ago, axel737 said:

Ok but it worked without problems before, earlier updates

That's no guarantee it will work with future updates. The FLAi package gets updates and the AI_liveries.xml in installed_liveries was updated recently too, so it will make use of more corners of the FLAi package.

Share this post


Link to post
Share on other sites

ok, i can't find to contact the people from FLAI to say that there are errors in their package.

Share this post


Link to post
Share on other sites

i set the sim at EGLL and after 2 minutes P3d v4 shuts down, here is the log :

hu Aug 22 09:05:57 2019 (utc)
version 15.15
PSXT (32 bit)
for Prepar3D v3/v4 or FSX

***************************** parameters *****************************
MAIN_WINDOW_X=1031
MAIN_WINDOW_Y=45
PARK_GROUNDSPEED=20
VERSION_CHECKED_AT=Thu Aug 22
PROGRAM_VERSION=15.15
INSTALL_PATH=C:\PSXseeconTraffic
ALWAYS_ON_TOP=true
MINIMIZE_WHEN_GREEN=false
LIVE=true
SYNC_FPS=false
RANDOM=true
HEAVY_MIDDLE_AIRCRAFT=true
LIGHT_AIRCRAFT=false
HELICOPTERS=false
INCLUDE_UFOS=false
INCLUDE_NOTYPES=false
AUTO_MODE=false
GROUND_TRAFFIC=true
LIVE_IF_USER_AIRBORNE=false
COLLISION_USER_GND=true
COLLISION_LIVE_PARKED_GND=false
LOG_MATCHING=false
LOG_PARK=false
LOG_XML=false
UPS=25
NON_REAL_REMOVAL_THRESHOLD=30
LATERAL_RANGE=40
FLOOR_ALTITUDE=-1000
LIVERIES_FOLDER=installation_liveries
AIRPORTS_FOLDER=C:\ParkPosGenerator\airports
FLIGHTPLANSFOLDER=
BLOCK_CALLSIGN=
**********************************************************************

Searching for AILGenerator at this PC
Reading airport's data from "C:\ParkPosGenerator\airports"
Reading airport's data from "parked_updates"
10043 airports found
Waiting for data provider to connect to PSXT ...
Waiting for Flight Simulator ...
Lockheed Martin Prepar3D v4 connected
Data provider connected

Aircraft type information read from "data\types.xml"
*** author:   PSXseeconTraffic
*** version:  12.11
*** date:     Sat Dec  1

Wingspan information read from "data\wingspan.xml"
*** author:   PSXseeconTraffic
*** version:  13.0
*** date:     Sat Dec  1
    max possible half wingspan: 35.9

*************************************** liveries summary ***************************************
1868 liveries read from file "installation_liveries\AI_liveries.xml"
*** author:   AILGenerator
*** version:  4.11
*** date:     Mon Aug  5
93 registration codes
generic Boeing liveries for 25 types: B703 B712 B721 B722 B732 B733 B734 B735 B736 B737 B738
   B739 B741 B742 B743 B744 B748 B752 B753 B762 B763 B764 B772 B773 B789
generic Airbus liveries for 16 types: A21N A306 A30B A310 A318 A319 A320 A321 A332 A333 A342
   A343 A345 A346 A359 A388
generic Embraer liveries for 5 types: E120 E135 E145 E170 E190
generic Bombardier liveries for 2 types: GL5T GLEX
generic ATR liveries for 5 types: AT43 AT44 AT45 AT72 AT75
generic Private liveries for 25 types: A139 BE10 BE20 C130 C172 C208 C402 C414 C421 C750 DHC6
   GLEX GLF2 H25B LJ23 LJ24 LJ25 LJ31 LJ35 P28A PA31 SF34 SH33 SR22 SW4
390 unique airlines
120 unique aircraft types
Default livery set for aircraft category Heavy, type B763, # liveries: 59
Default livery set for aircraft category Middle, type A320, # liveries: 311
Default livery set for aircraft category Light, type PC12, # liveries: 6
Default livery set for aircraft category Heli, type A139, # liveries: 7
************************************************************************************************

User aircraft title: Prosim_AR_737_800_PRO_2018_Ryanair
User aircraft model: B738
User aircraft half wing span: 17.8 meter
Connecting QNHReader to UDP port 49004 ...
QNHReader connected
Connecting TrafficReader to UDP port 49003 ...
TrafficReader connected
QNH: 1025
User aircraft at the ground, at airport EGLL (LHR), groundspeed: 0
The parking airport is: EGLL (LHR)

Out of business information read from "data\outofbusiness.xml"
*** author:   Nico
*** version:  1.0
*** date:     June 23, 2019

Parkpos file "parked_updates\EGLL.xml" for Heathrow
*** author:   Nico
*** version:  1.0
*** date:     June 23, 2019
    supplier:
    189 parking positions, of which
    8 real live parking positions (4%), with
    8 real live options, and
    16 defined hours
    last update Wed Aug 21

95 positions to be filled (50%)
"FLAi_RAI_E75S_BEE-Flybe G-FBJH" could not be created
"FLAi_B763_DAL-Delta ST N175DZ" could not be created
"FLAi_B763_UAL-United N670UA" could not be created
"FLAi_B763_DAL-Delta NC GE N1610D" could not be created

Share this post


Link to post
Share on other sites

Looks like PSX is telling P3D to inject something that is not there.

 

Share this post


Link to post
Share on other sites
Posted (edited)

@axel737 Did you try this tip from the FAQ:

"Even if AILGenerator does not show any errors there still can be problems with your AI aircraft. For P3D users I recommend to add the following key to the [MAIN] section of the file C:\Users\<your name>\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.cfg: ContentErrorReporting=1
Start P3D, wait till it has completed the start-up, then exit P3D. The file with content errors will be written to your Documents\Prepar3D v4 Files folder. Fix each error related to AI."

Edited by kiek

Share this post


Link to post
Share on other sites
Posted (edited)

Well, I spent a considerable amount of time testing in the past days.

The good news is that PSXT has nothing to do with the CTDs (actually, I never suspected this).😀

When I use AIG-AI instead of FLAi, P3D and PSXT are running smooth and continously for hours. When I switch back to FlAi, it is only a matter of time (sometimes 1 minute, sometimes 10 minutes) until P3D crashes. All tests were performed at EDDF.

The tricky part is to find the cause. though. There is no content error in the P3D logfile and no error message in the log of PSXT as well.

The model matching errors related to the 767 are not a problem, they just couldn't be created. That's nothing worse, it'll not crash the sim. However, some indications are pointing to the A320neo aircraft. I noticed after several crashes that one of last liveries created by PSXT was a A320neo aircraft (the logfile stopped after this because the sim crashed). I checked the corresponding airplane directory in the FlAi folder, but couldn't find any obvious mistake, though. Another developer (LORBY_SI) also reported CTD issues with the A320 models in a different forum:

https://prepar3d.com/forum/viewtopic.php?f=6310&amp;t=133221

I know that these observations are rather vague and no proof. But for now, I'll stick with the AIG package which appears to have resolved the problem for me. Unfortunately, the model matching requires some optimization.

I'm considering to replace the A320neo model in FLAi and re-compile the FLAi package with the AILG generator to confirm that this is really the issue.

Just wanted to report back.

Best regards,
Dirk

 


 

Edited by schepma

Share this post


Link to post
Share on other sites
Posted (edited)

Thank you for your test work! 

There is also a nice program called AI-Aircraft Editor that can check liveries upon errors. 

Edited by kiek

Share this post


Link to post
Share on other sites

the AI generator, must this run at the same time as real traffic and psxseecontraffic ?

 

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, axel737 said:

the AI generator, must this run at the same time as real traffic and psxseecontraffic ?

No, it can run stand alone. No need to run P3D, PSXT and RT.

 

Edited by kiek

Share this post


Link to post
Share on other sites

still having problems, it's now after 3 - 4 hours :

here is the log from tha AI generator, it there anything else i still can do about this ?

Mon Aug 26 09:45:57 2019 (utc)
version 5.0
AILG (64 bit)

***************************** parameters *****************************
MAIN_WINDOW_X=390
MAIN_WINDOW_Y=96
VERSION_CHECKED_AT=Sun Aug 25
PROGRAM_VERSION=5.0
INSTALL_PATH=C:\AILGenerator
INCLUDE_VAS=false
INCLUDE_GXX=true
INCLUDE_ZXX=true
REPAIR_FORMAT=true
OUTPUT_FOLDER=liveries
folder0=C:\Program Files\Lockheed Martin\Prepar3D V4
folder1=
folder2=
folder3=
folder4=
folder5=
folder6=
folder7=
folder8=
folder9=
**********************************************************************

OUTPUT_FOLDER=liveries
VERSION_CHECKED_AT=Mon Aug 26

Number of concurrent threads supported by your cpu: 20

2422 ICAO Aircraft type information read from "data\aircraft.xml"
*** author:   AILGenerator + Nico
*** version:  3.2
*** date:     Aug 21, 2019
6083 ICAO Airline codes read from "data\airlines.xml"
*** author:   AILGenerator+Nico
*** version:  3.3
*** date:     Aug 12, 2019


"liveries\AI_liveries.xml" removed
"info\AirlineData.txt" removed
"info\AircraftCfgWithNoFltsimSection.txt" removed
"info\EmptyRegistrations.txt" removed
"errors\InvalidAirlineCodes.txt" removed
"errors\InvalidAircraftCodes.txt" removed
"errors\InvalidAircraftCfgFiles.txt" removed
"errors\IncompleFltsimSections.txt" removed
folder "errors" removed

Searching in C:\Program Files\Lockheed Martin\Prepar3D V4
There are spaces around title: "F-35A Lightning II  "
removed spaces around: "F-35A Lightning II  " --> "F-35A Lightning II"
F-WWEZ, FLAi_OSP_ATR72_200_ZZZZ -> title=FLAi_OSP_ATR72_200_ZZZZ F-WWEZ
C-FSIL, FLAi_AIA_B38M_ACA-Air Canada -> title=FLAi_AIA_B38M_ACA-Air Canada C-FSIL
C-FNWD, FLAi_AIA_B38M_WJA-Westjet -> title=FLAi_AIA_B38M_WJA-Westjet C-FNWD
C-FRAX, FLAi_AIA_B38M_WJA-Westjet OC -> title=FLAi_AIA_B38M_WJA-Westjet OC C-FRAX
N8709Q, FLAi_AIA_B38M_SWA-Southwest -> title=FLAi_AIA_B38M_SWA-Southwest N8709Q
N8715Q, FLAi_AIA_B38M_SWA-Southwest ETOPS -> title=FLAi_AIA_B38M_SWA-Southwest ETOPS N8715Q
N303RG, FLAi_AIA_B38M_AAL-American -> title=FLAi_AIA_B38M_AAL-American N303RG
N47505, FLAi_AIA_B39M_UAL-United -> title=FLAi_AIA_B39M_UAL-United N47505
HP-9901CMP, FLAi_AIA_B39M_CMP-Copa -> title=FLAi_AIA_B39M_CMP-Copa HP-9901CMP
HS-LSH, FLAi_AIA_B39M_TLM-Thai Lion -> title=FLAi_AIA_B39M_TLM-Thai Lion HS-LSH
N739EX, FLAi_AIA_B39M_LNI-Lion -> title=FLAi_AIA_B39M_LNI-Lion N739EX
N7560V, FLAi_B732_X -> title=FLAi_B732_X N7560V
N767BA, FLAi_FAIB_B762_X -> title=FLAi_FAIB_B762_X N767BA
A9C-DHK, FLAi_B762_DHK-DHL International -> title=FLAi_B762_DHK-DHL International A9C-DHK
A9C-CJT, FLAi_B762_CJT-Cargojet -> title=FLAi_B762_CJT-Cargojet A9C-CJT
N602KW, FLAi_B762_EAL-Eastern -> title=FLAi_B762_EAL-Eastern N602KW
N767S, FLAi_B763_X -> title=FLAi_B763_X N767S
N76400, FLAi_B764_X -> title=FLAi_B764_X N76400
N398AN, FLAi_B763_AAL-American NC -> title=FLAi_B763_AAL-American NC N398AN
N835MH, FLAi_B764_DAL-Delta NC -> title=FLAi_B764_DAL-Delta NC N835MH
N377AN, FLAi_B763_AAL-American OC -> title=FLAi_B763_AAL-American OC N377AN
N845MH, FLAi_B764_DAL-Delta BCRF -> title=FLAi_B764_DAL-Delta BCRF N845MH
N343AN, FLAi_B763_AAL-American OW -> title=FLAi_B763_AAL-American OW N343AN
N844MH, FLAi_B764_DAL-Delta ST -> title=FLAi_B764_DAL-Delta ST N844MH
OE-LAT, FLAi_B763_AUA-Austrian NC -> title=FLAi_B763_AUA-Austrian NC OE-LAT
N77066, FLAi_B764_UAL-United NC -> title=FLAi_B764_UAL-United NC N77066
OE-LAW, FLAi_B763_AUA-Austrian MA -> title=FLAi_B763_AUA-Austrian MA OE-LAW
N76055, FLAi_B764_UAL-United SA -> title=FLAi_B764_UAL-United SA N76055
N1610D, FLAi_B763_DAL-Delta NC GE -> title=FLAi_B763_DAL-Delta NC GE N1610D
N198DN, FLAi_B763_DAL-Delta NC PW -> title=FLAi_B763_DAL-Delta NC PW N198DN
N175DZ, FLAi_B763_DAL-Delta ST -> title=FLAi_B763_DAL-Delta ST N175DZ
4X-EAP, FLAi_B763_ELY-El Al -> title=FLAi_B763_ELY-El Al 4X-EAP
N68079, FLAi_B763_FDX-Fedex -> title=FLAi_B763_FDX-Fedex N68079
JU-1021, FLAi_B763_MGL-Miat -> title=FLAi_B763_MGL-Miat JU-1021
N670UA, FLAi_B763_UAL-United -> title=FLAi_B763_UAL-United N670UA
N653UA, FLAi_B763_UAL-United SA -> title=FLAi_B763_UAL-United SA N653UA
N320UP, FLAi_B763_UPS -> title=FLAi_B763_UPS N320UP
D-ABUA, FLAi_B763_CFG-Condor NC -> title=FLAi_B763_CFG-Condor NC D-ABUA
D-ABUK, FLAi_B763_CFG-Condor OC -> title=FLAi_B763_CFG-Condor OC D-ABUK
D-ABUM, FLAi_B763_CFG-Condor Retro -> title=FLAi_B763_CFG-Condor Retro D-ABUM
ET-ALJ, FLAi_B763_ETH-Ethiopian -> title=FLAi_B763_ETH-Ethiopian ET-ALJ
VH-EFR, FLAi_B763_QFA-Qantas -> title=FLAi_B763_QFA-Qantas VH-EFR
UR-GEA, FLAi_B763_AUI-Ukraine -> title=FLAi_B763_AUI-Ukraine UR-GEA
N284DH, FLAi_B763_CKS-Kalitta -> title=FLAi_B763_CKS-Kalitta N284DH
N316CM, FLAi_B763_AJT-Amerijet -> title=FLAi_B763_AJT-Amerijet N316CM
EC-AAA, FLAi_B763_XSN-Air Spain -> title=FLAi_B763_XSN-Air Spain EC-AAA
N706KW, FLAi_B763_EAL-Eastern -> title=FLAi_B763_EAL-Eastern N706KW
There are spaces around title: " FLAi_C-46 COMMANDO  "
removed spaces around: " FLAi_C-46 COMMANDO  " --> "FLAi_C-46 COMMANDO"
exception copy_file: Toegang geweigerd.

: "C:\Program Files\Lockheed Martin\Prepar3D V4\SimObjects\Airplanes\FLAi_A140\Aircraft.cfg", "C:\Program Files\Lockheed Martin\Prepar3D V4\SimObjects\Airplanes\FLAi_A140\Aircraft0.cfg" in searching in folder "C:\Program Files\Lockheed Martin\Prepar3D V4"
=> 2 liveries found.

Total valid found: 2

"errors\InvalidAirlineCodes.txt" written
Invalid airline codes: 71
"errors\InvalidAircraftCodes.txt" written
Invalid type codes: 2
Fixed type codes: 0
Empty aircraft.cfg: 11
"info\AircraftCfgWithNoFltsimSection.txt" written
Invalid aircraft.cfg: 27
"errors\InvalidAircraftCfgFiles.txt" written
"errors\IncompleFltsimSections.txt" written
% without registration code: 100
Skipped on priority: 0
Skipped on registration code: 0
2 liveries written to "liveries\AI_liveries.xml"
Unique airlines: 2
Unique types   : 1
49 title shave changed, re-start your Simulator!
"info\EmptyRegistrations.txt" written
"info\AirlineData.txt" written


"liveries\AI_liveries.xml" removed
"info\AirlineData.txt" removed
"info\AircraftCfgWithNoFltsimSection.txt" removed
"info\EmptyRegistrations.txt" removed
"errors\InvalidAirlineCodes.txt" removed
"errors\InvalidAircraftCodes.txt" removed
"errors\InvalidAircraftCfgFiles.txt" removed
"errors\IncompleFltsimSections.txt" removed
folder "errors" removed

Searching in C:\Program Files\Lockheed Martin\Prepar3D V4
There are spaces around title: "F-35A Lightning II  "
removed spaces around: "F-35A Lightning II  " --> "F-35A Lightning II"
F-WWEZ, FLAi_OSP_ATR72_200_ZZZZ -> title=FLAi_OSP_ATR72_200_ZZZZ F-WWEZ
C-FSIL, FLAi_AIA_B38M_ACA-Air Canada -> title=FLAi_AIA_B38M_ACA-Air Canada C-FSIL
C-FNWD, FLAi_AIA_B38M_WJA-Westjet -> title=FLAi_AIA_B38M_WJA-Westjet C-FNWD
C-FRAX, FLAi_AIA_B38M_WJA-Westjet OC -> title=FLAi_AIA_B38M_WJA-Westjet OC C-FRAX
N8709Q, FLAi_AIA_B38M_SWA-Southwest -> title=FLAi_AIA_B38M_SWA-Southwest N8709Q
N8715Q, FLAi_AIA_B38M_SWA-Southwest ETOPS -> title=FLAi_AIA_B38M_SWA-Southwest ETOPS N8715Q
N303RG, FLAi_AIA_B38M_AAL-American -> title=FLAi_AIA_B38M_AAL-American N303RG
N47505, FLAi_AIA_B39M_UAL-United -> title=FLAi_AIA_B39M_UAL-United N47505
HP-9901CMP, FLAi_AIA_B39M_CMP-Copa -> title=FLAi_AIA_B39M_CMP-Copa HP-9901CMP
HS-LSH, FLAi_AIA_B39M_TLM-Thai Lion -> title=FLAi_AIA_B39M_TLM-Thai Lion HS-LSH
N739EX, FLAi_AIA_B39M_LNI-Lion -> title=FLAi_AIA_B39M_LNI-Lion N739EX
N7560V, FLAi_B732_X -> title=FLAi_B732_X N7560V
N767BA, FLAi_FAIB_B762_X -> title=FLAi_FAIB_B762_X N767BA
A9C-DHK, FLAi_B762_DHK-DHL International -> title=FLAi_B762_DHK-DHL International A9C-DHK
A9C-CJT, FLAi_B762_CJT-Cargojet -> title=FLAi_B762_CJT-Cargojet A9C-CJT
N602KW, FLAi_B762_EAL-Eastern -> title=FLAi_B762_EAL-Eastern N602KW
N767S, FLAi_B763_X -> title=FLAi_B763_X N767S
N398AN, FLAi_B763_AAL-American NC -> title=FLAi_B763_AAL-American NC N398AN
N377AN, FLAi_B763_AAL-American OC -> title=FLAi_B763_AAL-American OC N377AN
N343AN, FLAi_B763_AAL-American OW -> title=FLAi_B763_AAL-American OW N343AN
OE-LAT, FLAi_B763_AUA-Austrian NC -> title=FLAi_B763_AUA-Austrian NC OE-LAT
OE-LAW, FLAi_B763_AUA-Austrian MA -> title=FLAi_B763_AUA-Austrian MA OE-LAW
N76400, FLAi_B764_X -> title=FLAi_B764_X N76400
N1610D, FLAi_B763_DAL-Delta NC GE -> title=FLAi_B763_DAL-Delta NC GE N1610D
N835MH, FLAi_B764_DAL-Delta NC -> title=FLAi_B764_DAL-Delta NC N835MH
N198DN, FLAi_B763_DAL-Delta NC PW -> title=FLAi_B763_DAL-Delta NC PW N198DN
N845MH, FLAi_B764_DAL-Delta BCRF -> title=FLAi_B764_DAL-Delta BCRF N845MH
N175DZ, FLAi_B763_DAL-Delta ST -> title=FLAi_B763_DAL-Delta ST N175DZ
N844MH, FLAi_B764_DAL-Delta ST -> title=FLAi_B764_DAL-Delta ST N844MH
4X-EAP, FLAi_B763_ELY-El Al -> title=FLAi_B763_ELY-El Al 4X-EAP
N77066, FLAi_B764_UAL-United NC -> title=FLAi_B764_UAL-United NC N77066
N68079, FLAi_B763_FDX-Fedex -> title=FLAi_B763_FDX-Fedex N68079
JU-1021, FLAi_B763_MGL-Miat -> title=FLAi_B763_MGL-Miat JU-1021
N76055, FLAi_B764_UAL-United SA -> title=FLAi_B764_UAL-United SA N76055
N670UA, FLAi_B763_UAL-United -> title=FLAi_B763_UAL-United N670UA
N653UA, FLAi_B763_UAL-United SA -> title=FLAi_B763_UAL-United SA N653UA
N320UP, FLAi_B763_UPS -> title=FLAi_B763_UPS N320UP
D-ABUA, FLAi_B763_CFG-Condor NC -> title=FLAi_B763_CFG-Condor NC D-ABUA
D-ABUK, FLAi_B763_CFG-Condor OC -> title=FLAi_B763_CFG-Condor OC D-ABUK
D-ABUM, FLAi_B763_CFG-Condor Retro -> title=FLAi_B763_CFG-Condor Retro D-ABUM
ET-ALJ, FLAi_B763_ETH-Ethiopian -> title=FLAi_B763_ETH-Ethiopian ET-ALJ
VH-EFR, FLAi_B763_QFA-Qantas -> title=FLAi_B763_QFA-Qantas VH-EFR
UR-GEA, FLAi_B763_AUI-Ukraine -> title=FLAi_B763_AUI-Ukraine UR-GEA
N284DH, FLAi_B763_CKS-Kalitta -> title=FLAi_B763_CKS-Kalitta N284DH
N316CM, FLAi_B763_AJT-Amerijet -> title=FLAi_B763_AJT-Amerijet N316CM
EC-AAA, FLAi_B763_XSN-Air Spain -> title=FLAi_B763_XSN-Air Spain EC-AAA
N706KW, FLAi_B763_EAL-Eastern -> title=FLAi_B763_EAL-Eastern N706KW
exception copy_file: Toegang geweigerd.

: "C:\Program Files\Lockheed Martin\Prepar3D V4\SimObjects\Airplanes\FLAi_A140\Aircraft.cfg", "C:\Program Files\Lockheed Martin\Prepar3D V4\SimObjects\Airplanes\FLAi_A140\Aircraft0.cfg" in searching in folder "C:\Program Files\Lockheed Martin\Prepar3D V4"
=> 2 liveries found.

Total valid found: 2

There are spaces around title: " FLAi_C-46 COMMANDO  "
removed spaces around: " FLAi_C-46 COMMANDO  " --> "FLAi_C-46 COMMANDO"
"errors\InvalidAirlineCodes.txt" written
Invalid airline codes: 71
"errors\InvalidAircraftCodes.txt" written
Invalid type codes: 2
Fixed type codes: 0
Empty aircraft.cfg: 11
"info\AircraftCfgWithNoFltsimSection.txt" written
Invalid aircraft.cfg: 27
"errors\InvalidAircraftCfgFiles.txt" written
"errors\IncompleFltsimSections.txt" written
% without registration code: 100
Skipped on priority: 0
Skipped on registration code: 0
2 liveries written to "liveries\AI_liveries.xml"
Unique airlines: 2
Unique types   : 1
49 title shave changed, re-start your Simulator!
"info\EmptyRegistrations.txt" written
"info\AirlineData.txt" written

09:46:59 User closed AILGenerator
MAIN_WINDOW_X=390
MAIN_WINDOW_Y=96
Mon Aug 26 09:46:59 2019

Share this post


Link to post
Share on other sites

2 liveries written to "liveries\AI_liveries.xml"

That does not look good, does it?

I'll come back to you later...

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now