Not connecting to MSFS

[unc1rlm 31]

Hi kiek..I have v21.4 32 bit. I have msfs running but psx stays red and waiting for MSFS....where can I look. Have fsuipc and real traffic  connects  as spotter but not PSX to sim.

 

Thanks,

BobM.

[kiek 1,212]

3 hours ago, unc1rlm said:

..where can I look. Have fsuipc and real traffic  connects  as spotter but not PSX to sim.

Look in the Manual. FSUIPC has nothing to do with PSXT_MSFS. You need a SimConnect client maybe?

[unc1rlm 31]

I have the sdk installed in MSFS dev mode....61259.0 simconnect ...exceptions for Malwarebytes for psxt folder..no firewall on and it still won't connect..red as a beet?

 

Thanks,

BobM.

Real traffic is busy 1564/6868 in spotter but nothing for psxt.

[kiek 1,212]

1 run msfs, go to a gate with your user aircraft 

2. Start psxt_msfs

3. Start real traffic

Post the Log.txt 

[unc1rlm 31]

Wed Feb  3 20:12:33 2021 (utc) PSXT_MSFS version 21.4 for MSFS

********************************** parameters **********************************
from C:\Users\unc1r\AppData\Roaming\PSXT_MSFS\parameters.xml
ADD_ORIG_DEST=false
RANDOM=true
ALWAYS_GND_TRAFFIC=false
LIVE_IF_USER_AIRBORNE=false
MAIN_WINDOW_X=400
MAIN_WINDOW_Y=20
PARK_GROUNDSPEED=20
FLOOR_ALTITUDE=-1000
REMOVE_FALSE_THRESHOLD=50
VERSION_CHECKED_AT=Feb  3, 2021
PROGRAM_VERSION=21.4
INSTALL_PATH=C:\PSXT_MSFS
ALWAYS_ON_TOP=true
LIGHT_AIRCRAFT=true
HELICOPTERS=true
INCLUDE_NOTYPES=true
AUTO_MODE=false
PARK_SIMILARS=true
COLLISION_LIVE_PARKED_GND=true
COLLISION_USER_GND=true
LATERAL_RANGE=40
BLOCK_CALLSIGN=
LIVERIES_FOLDER=C:\AILG_MSFS\liveries
AIRPORTS_FOLDER=
FLIGHTPLANSFOLDER=
********************************************************************************

C:\Users\unc1r\AppData\Roaming\PSXT_MSFS\avg_heights.txt not found

Aircraft type information read from data\types.xml
author: PSXseeconTraffic, version: 20.2, date: Jan 14, 2021

Similar aircraft types read from data\types.xml
author: PSXseeconTraffic, version: 20.2, date: Jan 14, 2021

Wingspan information read from data\wingspan.xml
author: PSXseeconTraffic + Nico, version: 20.2, date: Feb 1, 2021

***************************************** liveries summary *****************************************
1169 liveries read from file C:\AILG_MSFS\liveries\AI_liveries.xml
author: AILG_MSFS, version: 1.4, date: Feb  3, 2021

0 registration codes found in the liveries of the user
generic liveries for 34 types: A306 A319 A320 A321 A332 A333 A359 AT72 B703 B737 B738 
   B739 B741 B742 B743 B744 B748 B752 B763 B772 B773 B77L B77W B788 CONC CRJ7 CRJ9 DC10 DH8D 
   E135 E190 E75L MD11 T154 
11 unique airlines, 37 unique aircraft types
Default livery set for aircraft category Heavy, type B744, # liveries: 185
Default livery set for aircraft category Middle, type B738, # liveries: 494
Default livery set for aircraft category Light, type CONC, # liveries: 4
No default livery found for aircraft category Heli
Include Helicopters deselected while there are no Helicopter liveries

0 registration codes + Airline + Type added from data\regcodes.xml
author: AILGenerator+Nico, version: 5.1, date: Oct 20, 2020

****************************************************************************************************

21548 airports found in data\airports.xml
author: ParkPosGenerator + Nico, version: 19.4, date: Jan 10, 2021

Waiting for Microsoft Flight Simulator 2020 ...
 

[kiek 1,212]

What MSFS type do you have? Store, or ...

[unc1rlm 31]

Store  installed on separate ssd not in c;/user...etc

Edited February 4, 2021 by unc1rlm

[kiek 1,212]

Looks like a SimConnect issue to me.. 

[motishow 122]

3 hours ago, kiek said:

Looks like a SimConnect issue to me.. 

maybe a bad installation of SDK?

[kiek 1,212]

20 minutes ago, motishow said:

maybe a bad installation of SDK?

No, the SDK is not needed for PSXT_MSFS. 

I suspect your SimConnect client.

 

Edited February 4, 2021 by kiek

[unc1rlm 31]

I finally found it and it was a simconnect.cfg in my documents. Good for now.

BobM.

Edited February 5, 2021 by unc1rlm

[kiek 1,212]

3 hours ago, unc1rlm said:

I finally found it and it was a simconnect.cfg in my documents. Good for now.

BobM.

Okay, good to hear you solved it.