PSXseecontraffic may cause Aivlasoft EFB to crash

[Bardia 11]

Hi Nico

Terribly sorry to be bothering you again but today I launched PSX at UK2000 Luton together with Aivlasoft EFB but after a few second EFB crashed leaving no trace in the Windows error log but here is the PSX log file:

 

Wed Jan 24 21:02:53 2018 (utc)
version 9.17
PSXseeconTraffic (64 bit)
for any user aircraft in Prepar3D v4
21:02:53 Start reading and processing parameters from PSXseeconTraffic.cfg

********* Parameters **********
ALWAYS_ON_TOP=0
HELICOPTERS=0
LIGHT_AIRCRAFT=0
LIMITED_VERTICAL_RANGE=0
AUTO_MODE=1
COLLISION_DET_AIR=0
COLLISION_DET_GND=1
LOG_MATCHING=0
LOG_PARKING=0
LOG_TAKEOFF=0
LOG_LANDING=0
VERSION_CHECKED_AT=Fri Jan 19 
VMRGENERATOR=
FLIGHTPLANSFOLDER=flightplans
LATERAL_RANGE=40
AUTO_GND=15
AUTO_BELOW_ALT_IN_RANGE=20
AUTO_BELOW_ALT_OUT_OF_RANGE=30
AUTO_ALT=10000
AUTO_RANGE=15
AUTO_ABOVE_ALT=40
AUTO_VERTICAL_RANGE_GND=5000
AUTO_VERTICAL_BELOW_ALT_IN_RANGE=7500
AUTO_VERTICAL_BELOW_ALT_OUT_OF_RANGE=10000
AUTO_VERTICAL_ABOVE_ALT=15000
LIMIT_VERTICAL_RANGE=10000
FLOOR_ALTITUDE=0
ONLY_INJECT_WHEN_USER_AIRBORNE=0
FLOOR_ALTITUDE_ACTIVE=0
PARK_STATIC=1
VERSION_CHECK=1
*********************************

Version check ...

Looks like an updated verson is available.
VERSION_CHECKED_AT=Wed Jan 24 
There are 4211 airports in the internal database
21:02:55 Start reading and processing AI_liveries.txt ...

********* AI_liveries.txt summary *********
731 liveries read from file AI_liveries.txt
57 Registration codes for a livery
no generic Boeing liveries
no generic Airbus liveries
no generic Embraer liveries
no generic Bombardier liveries
no generic ATR liveries
no generic Private liveries
203 unique airlines
41 unique aircraft types
Default livery set for aircraft category Heavy, type A306, num liveries: 5
Default livery set for aircraft category Middle, type A318, num liveries: 5
Default livery set for aircraft category Light, type DHC6, num liveries: 8
No default livery found for aircraft category Helicopter
****************************************

21:02:55 Initializing PSX server at port 10747
21:02:55 Waiting for FlightSimulator to connect ...
21:02:55 Waiting for RealTraffic to connect ...
21:02:56 RealTraffic connected
21:02:58 Waiting for FlightSimulator to connect ...
21:03:02 Waiting for FlightSimulator to connect ...
21:03:05 Waiting for FlightSimulator to connect ...
21:03:08 Waiting for FlightSimulator to connect ...
21:03:12 Waiting for FlightSimulator to connect ...
21:03:15 Waiting for FlightSimulator to connect ...
21:03:19 Waiting for FlightSimulator to connect ...
21:03:22 Waiting for FlightSimulator to connect ...
21:03:26 Waiting for FlightSimulator to connect ...
21:03:29 Waiting for FlightSimulator to connect ...
21:03:32 Waiting for FlightSimulator to connect ...
21:03:36 Waiting for FlightSimulator to connect ...
21:03:39 Waiting for FlightSimulator to connect ...
21:03:43 Waiting for FlightSimulator to connect ...
21:03:46 Waiting for FlightSimulator to connect ...
21:03:50 Waiting for FlightSimulator to connect ...
21:03:53 Waiting for FlightSimulator to connect ...
21:03:56 Waiting for FlightSimulator to connect ...
21:04:00 Waiting for FlightSimulator to connect ...
21:04:03 Waiting for FlightSimulator to connect ...
21:04:07 Waiting for FlightSimulator to connect ...
21:04:10 Waiting for FlightSimulator to connect ...
21:04:13 Waiting for FlightSimulator to connect ...
21:04:17 Waiting for FlightSimulator to connect ...
21:04:20 Waiting for FlightSimulator to connect ...
21:04:24 Waiting for FlightSimulator to connect ...
21:04:27 Waiting for FlightSimulator to connect ...
21:04:31 Waiting for FlightSimulator to connect ...
21:04:34 Waiting for FlightSimulator to connect ...
21:04:37 Waiting for FlightSimulator to connect ...
21:04:41 Waiting for FlightSimulator to connect ...
21:04:44 Waiting for FlightSimulator to connect ...
21:04:48 Waiting for FlightSimulator to connect ...
21:04:51 Waiting for FlightSimulator to connect ...
21:04:55 Waiting for FlightSimulator to connect ...
21:04:58 Waiting for FlightSimulator to connect ...
21:05:01 Waiting for FlightSimulator to connect ...
21:05:05 Waiting for FlightSimulator to connect ...
21:05:08 Waiting for FlightSimulator to connect ...
21:05:12 Waiting for FlightSimulator to connect ...
21:05:15 Waiting for FlightSimulator to connect ...
21:05:19 Waiting for FlightSimulator to connect ...
21:05:22 Waiting for FlightSimulator to connect ...
21:05:25 Waiting for FlightSimulator to connect ...
21:05:29 Waiting for FlightSimulator to connect ...
21:05:32 Waiting for FlightSimulator to connect ...
21:05:36 Waiting for FlightSimulator to connect ...
21:05:39 Waiting for FlightSimulator to connect ...
21:05:43 Waiting for FlightSimulator to connect ...
21:05:46 Waiting for FlightSimulator to connect ...
21:05:49 Waiting for FlightSimulator to connect ...
21:05:53 Waiting for FlightSimulator to connect ...
21:05:58 Lockheed Martin® Prepar3D® v4 connected
21:10:35 User aircraft title: PMDG 777-300ER Brussels Airlines
21:10:35 User aircraft model: B77W,  category: H
21:10:36 User aircraft position: latitude, longitude  51.871995,-0.383255
21:10:36 User aircraft at 51.871995,-0.383255, close to or at airport EGGW, dist 0.5 Nm
PERCENTAGE_PARKED=35
NUM_PARK_POSITIONS=30
21:10:36 35 % parked set for EGGW
21:10:36 EGGW has 29 parking positions
21:10:36 10 aircraft to be parked
AIRPORT_ALTITUDE_FEET=526
21:10:36 Connecting QNH Reader to UDP port 49004 ...
21:10:36 QNH Reader connected
21:10:37 Connecting Traffic Reader to UDP port 49003 ...
21:10:37 Traffic Reader connected
third party aircraft detected with callsign OO-YAF
21:10:38 Parked at r73:  no parked aircraft found
21:10:38 QNH: 1005 {"ICAO": "EGGW","QNH": 1005, "METAR": "EGGW 242050Z AUTO 21012KT 9999 FEW010 06/05 Q1005", "NAME": "London Luton Airport", "IATA": "LTN","DISTNM": 0.6}
Warning: Simconnect call to create AI ac in sim failed (?) rtid: 4661104, liv: Wizzair 'New Livery' Airbus A321-200 'Sharklets'
Warning: Simconnect call to create AI ac in sim failed (?) rtid: 4223687, liv: FAIB Airbus A321-200S CFM FFT Frontier Airlines NC "Max the Lynx"  N706FR
21:12:40 User closed PSXseeconTraffic, wait till all processes have stopped ...

******************** live traffic livery matching summary *****************************************
5 liveries needed, 80% were completely matched, of which 0% were matched upon registration code
 =X=   1 random livery for similar type
***************************************************************************************************

21:12:40 QNH Reader has stopped
21:12:40 Traffic Reader has stopped
21:12:42 Flight Simulator disconnected
Wed Jan 24 21:12:42 2018
 

 

 

Now I fully understand the EFB crash might have nothing to do with this but since it is a program that shows position of all injected ai traffic on the airport chart there is the possibility of a connection. I'd be grateful if you could look further into this.

 

Bardia

[kiek 1,215]

Hi Bardia,

I do not own EFB so I cannot test it. 

Some observations from your log:

"Warning: Simconnect call to create AI ac in sim failed (?) rtid: 4661104, liv: Wizzair 'New Livery' Airbus A321-200 'Sharklets'
Warning: Simconnect call to create AI ac in sim failed (?) rtid: 4223687, liv: FAIB Airbus A321-200S CFM FFT Frontier Airlines NC "Max the Lynx"  N706FR"

About these two warnings. Could you run again without EFB to see whether these warnings disappear or not...?

It takes  three minutes before P3D gets connected. Is it because you have started PSXseeconTraffic and RealTraffic three minutes earlier then P3D or ... ?

It is not possible that PSXseeconTraffic makes EFB to crash directly. However, both programs communicate with P3D via SimConnect. Maybe EFB is not as robust as PSXseeconTraffic with respect to being able to work with Simconnect at the same time as other programs...  Hopefully other EFB users may jump in with their experience.

Note that you can also view all AI aircraft in a map around you in ActiveSky for P3Dv4 (and AS does not crash).

Regards,

Nico

P.S. And please update to version 9.18 first.

[Bardia 11]

Hi Nico 

Thanks for your invaluable help. 

 

I tried again today with the exact same settings (9.18) and EFB didn’t crash. I guess it might have been something with the particular type of traffic at the time of crash. But there is one thing I don’t fully understand. Call me dumb but please can you explain this 3-minute thing a bit further into detail to me? I read your post many times over but didn’t really comprehend what you meant.

 

Many thanks

Bardia 

[kiek 1,215]

Hi Bardia,

From the log I saw that it took 3 minutes before PSXseeconTraffic got connected to P4Dv4.

This is normal if you start P3Dv4 later then PSXseeconTraffic and RealTraffic, but if P3Dv4 is already up and  running, while you start PSXseeconTraffic and RealTrafic, it should connect within a few seconds.

Just wondering what your start-up procedure was...?

Regards,

Nico

[Bardia 11]

Hi Nico

Thanks now I understand. Yes I start PSXseecontraffic and RealTraffic before P3D that's why there is a 3 minute gap.

Regards

Bardia

[ZKOKQ 984]

On 1/26/2018 at 8:37 AM, Bardia said:

Hi Nico

Thanks now I understand. Yes I start PSXseecontraffic and RealTraffic before P3D that's why there is a 3 minute gap.

Regards

Bardia

I would suggest starting PSXseeconTraffic after P3D is fully loaded. Also Avilasoft EFB, some times you can flood simconnect, and it is best to start after P3D is loaded, to reduce the load on simconnect. The plumbing has a very narrow pipe, so softly softly is the best approach.

[Bardia 11]

On 27/01/2018 at 0:48 PM, ZKOKQ said:

I would suggest starting PSXseeconTraffic after P3D is fully loaded. Also Avilasoft EFB, some times you can flood simconnect, and it is best to start after P3D is loaded, to reduce the load on simconnect. The plumbing has a very narrow pipe, so softly softly is the best approach.

Very good advice, will do. 

Bardia