Not seeing "REAL" traffic

hoser70
Posts: 169
Joined: Tue Jul 30, 2013 1:48 pm

Not seeing "REAL" traffic

Post by hoser70 »

all of a sudden I am not seeing any "REAL" traffic. Sitting here at KPRB with another pilot who I can't see. Happened landing at SNA a few days ago as well. What could I be doing wrong?
Thanks,
Lance

NDB Air
hoser70
Posts: 169
Joined: Tue Jul 30, 2013 1:48 pm

Re: Not seeing "REAL" traffic

Post by hoser70 »

Follow-up... Switched to FSX from P3Dv2.2 and saw the real traffic just fine. I wonder if this is a P3D issue with PE?
Thanks,
Lance

NDB Air
Keith Smith
Posts: 9939
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ
Contact:

Re: Not seeing "REAL" traffic

Post by Keith Smith »

You probably don't have the same aircraft installed for P3D that you do for FSX. Check the \program files (x86)\PilotEdge\aircraft\pe.smx file. Do you have all those planes installed? If not, PE is trying to create instances of planes that you don't have, resulting in invisible planes.

To fix it, either install the FSX stock aircraft, or modify the pe.smx file to accurately reflect what you actually have installed.
hoser70
Posts: 169
Joined: Tue Jul 30, 2013 1:48 pm

Re: Not seeing "REAL" traffic

Post by hoser70 »

Keith Smith wrote:You probably don't have the same aircraft installed for P3D that you do for FSX. Check the \program files (x86)\PilotEdge\aircraft\pe.smx file. Do you have all those planes installed? If not, PE is trying to create instances of planes that you don't have, resulting in invisible planes.

To fix it, either install the FSX stock aircraft, or modify the pe.smx file to accurately reflect what you actually have installed.
Thanks Keith. I'll have a looksee....
Thanks,
Lance

NDB Air
twharrell
Posts: 297
Joined: Mon Jul 08, 2013 12:02 pm

Re: Not seeing "REAL" traffic

Post by twharrell »

Same problem here, except I did modify my pe.smx file to include aircraft I do have, yet my airports and skies are empty. It's lonely out there.

Todd
Regards,

Todd
Keith Smith
Posts: 9939
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ
Contact:

Re: Not seeing "REAL" traffic

Post by Keith Smith »

Can you post the pe.smx file you edited and the 'title' lines from the aircraft.cfg files of one or more of the aircraft?
twharrell
Posts: 297
Joined: Mon Jul 08, 2013 12:02 pm

Re: Not seeing "REAL" traffic

Post by twharrell »

Here's my pe.smx file:

; Standard FS aircraft
;
Beech+Baron+58+Paint1 BE58
FTX+Beechcraft+King+Air+B200+N200EZ BE20
//Beech+King+Air+350+Paint1 BE20
FTX+Cessna+172+Skyhawk+N640SP C172
//Cessna+Skyhawk+172SP+Paint1 C172
Learjet+45 LJ45
Mooney+Bravo M20T
Piper+Cub J3
Piper+Cherokee+180 P28A
AIA+Boeing+737-800w+United+2010 B738
//Boeing+747-400+Paint1 B744
WoA_AIA_B744_PW_UAL-United+Airlines_NC B744
//Cessna+Grand+Caravan C208
FTX+Cessna+208B+N903PD C208
de+Havilland+Dash+8-100 DH8B
Douglas+DC-3 DC3
Alabeo+Extra+300s+White E300
//McDonnell-Douglas/Boeing+MD-83 MD83
WoA_AIA_MD_8X_SD_AAL-American Airlines_N214AA MD83
;
AIG+CRJ-700+United+Express+NC+(SkyWest)+N719SK+STD CRJ7
FTX+Cessna+Citation+II+N177RJ C550
FTX+Gulfstream+G-IV+N17JK GLF4
AI_Mustang+Generic+1 C510
FTX+Beechjet+400A+N106QS BE40
Regards,

Todd
Keith Smith
Posts: 9939
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ
Contact:

Re: Not seeing "REAL" traffic

Post by Keith Smith »

Change the // to ;

// aren't considered comments in that file.

Also, you'll need to update the registry to tell PE what to use as the default aircraft if it's anything other than the Cessna+Skyhawk+172SP+Paint1 model.
twharrell
Posts: 297
Joined: Mon Jul 08, 2013 12:02 pm

Re: Not seeing "REAL" traffic

Post by twharrell »

The // are there to disable those entries, as those aircraft aren't available in P3Dv2.
Regards,

Todd
Keith Smith
Posts: 9939
Joined: Sat Oct 09, 2010 8:38 pm
Location: Pompton Plains, NJ
Contact:

Re: Not seeing "REAL" traffic

Post by Keith Smith »

And what I'm saying is that // aren't considered comments. So you're telling it that the B744 is the //Boeing+747-400+Paint1 aircraft title. Replace the // with ;
Post Reply