News:

Precision Simulator update 10.173 (24 February 2024) is now available.
Navburo update 13 (23 November 2022) is now available.
NG FMC and More is released.

Main Menu

PSX.NET P3D ExternalSim

Started by Mark, Fri, 17 Jun 2016 14:05

Greg Hateley

Hi Mark,
Sorry to be the odd man out here, but after installing v2.4 into p3d v3, I get a crash to desktop.
I can get p3d to boot again by setting the add-ons.cfg to disable the externalsim (Active=false)
Looking the the windows application log it appears to be a fault in the p3d api.dll causing the crash.
In the mean time, could you advise where is the externalsim.dll add-on so I can remove it for now.

Greg

Mark

Quote from: Greg Hateley on Tue, 24 Oct 2017 15:01
Sorry to be the odd man out here, but after installing v2.4 into p3d v3, I get a crash to desktop.
I can get p3d to boot again by setting the add-ons.cfg to disable the externalsim (Active=false)
Looking the the windows application log it appears to be a fault in the p3d api.dll causing the crash.
In the mean time, could you advise where is the externalsim.dll add-on so I can remove it for now.

Are you on v3.4.22.19868?
I tend to develop against the highest v3 and v4 available at time of release as it's easy to upgrade just the Prepar3D Client (it's only about 200MB).

Just remove ExternalSim using the Programs and Features interface in your Control Panel.

cavaricooper

#482
Mark-

The simulation rate in PSX.... is what causes the sudden change to darkness.  During extended flight at x2, there are momentary flashes where I see waves (sort of like when ExternalSim doesn't get connection) and then it goes back to dark sky with stars.  100% repeatable.  As soon as I go back to x1 simulation, allest gut.  This also occurs at x4 sim rate, which is the fastest I have ever used.  I will investigate further....

I copied the following over my [LIGHTS] section in the .cfg....

[LIGHTS]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing 6=taxi, 7=recognition, 8=wing, 9=logo                   
light.0 = 1,   61.500,    0.600,   19.100, Opensky_beacon ,
light.1 = 1,   13.500,    0.600,   -7.080, Opensky_beacon ,
light.2 = 3, -122.850,    0.383,   11.750, Opensky_nav_yellow ,
light.3 = 3, -122.850,   -0.383,   11.750, Opensky_nav_yellow ,
light.4 = 2, -123.850,    0.000,   11.045, fx_strobeh ,
light.5 = 3,  -13.850,    0.000,   14.850, fx_vclighth ,
light.6 = 9, -208.500,   -4.500,   43.750, Opensky_wing_light , // <-----3 previously
light.7 = 9, -208.500,    4.500,   43.750, Opensky_wing_light , // <-----3 previously
light.8 = 5,  -79.700,  -29.200,   -2.000, Opensky_nacelle_refl ,
light.9 = 5,  -79.700,   29.200,   -2.000, Opensky_nacelle_refl ,
light.10= 5,  -46.500,  -11.700,    0.000, Opensky_nacelle_refl ,
light.11= 5,  -46.500,   11.700,    0.000, Opensky_nacelle_refl ,
light.12= 5,  -40.500,  -13.700,    1.900, Opensky_nacelle_refl ,
light.13= 5,  -40.500,   13.700,    1.900, Opensky_nacelle_refl ,
light.14= 5,  -14.333,    0.000,   -2.000, Opensky_nacelle_refl ,
light.15= 3,  -18.300,   -6.500,    6.000, Opensky_nacelle_refl ,
light.16= 3,  -52.610,   -4.500,    6.000, Opensky_nacelle_refl ,
light.17= 3, -144.510,    0.000,   -3.000, Opensky_wing_light ,


and place it here in case some others find it helpful...  THANKS TO THE ORIGINAL POSTER (JP, not I).  This FIXES the rear strobe position, however, due to a POSKY limitation, the strobes and nav lights are still tied in together.  The logo is inop.

None of this light stuff is particularly troublesome, as I seldom peek outside.  Taxi and Landing Lights work well.

I remain obliged- C
Carl Avari-Cooper, KTPA

Kockie69

#483
When I run the configuration ExternalSimID={3E6B47E7-C706-4A10-BC88-6E7C199ED5A6} change is made to the aircraft.cfg file. But no dll added to the folder and no reference from the file to the dll anymore. I can manually update the cfg but I don't have the x64.dll to copy into the folder. Am I missing something? Is this correct?

The result is that the router is not connected to any clients, in my case P3dv4.

Kr Robert

Mark

Quote from: Kockie69 on Wed, 25 Oct 2017 06:02
Is this correct?

It is correct. Now use the configuration app to edit the XML files.

Mark

#485
Quote from: cavaricooper on Tue, 24 Oct 2017 19:14
the strobes and nav lights are still tied in together.

Have you tried changing the light type in aircraft.cfg?

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing 6=taxi, 7=recognition, 8=wing, 9=logo   

The current mapping of Simconnect light to PSX flightdeck switch is:


Simconnect light  = PSX flightdeck switch

LIGHT BEACON      = BeaconLower AND BeaconUpper
LIGHT STROBE      = Strobe
LIGHT NAV         = NavL AND NavR
LIGHT CABIN       = Logo
LIGHT LANDING     = (InboardLandingL AND InboardLandingR) OR (OutboardLandingL AND OutboardLandingR)
LIGHT TAXI        = Taxi
LIGHT RECOGNITION = Logo
LIGHT WING        = Wing
LIGHT LOGO        = Logo
LIGHT PANEL       = Logo

Available PSX light switches from Qs443(ExtLts):
OutboardLandingL
OutboardLandingR
InboardLandingL
InboardLandingR
RunwayTurnoffL
RunwayTurnoffR
Taxi
BeaconUpper
BeaconLower
NavL
NavR
Strobe
Wing
Logo


I would consider making changes to this in future if a convincing case was made. Things like LIGHT PANEL and LIGHT CABIN could come from different PSX variables.

cavaricooper

@Mark, will attempt to refine at my end.

@Gary- If you have a spiffy new G-BNLG ready for WorldFlight, incorporating all of Mark's wizardry, would you do the village idiot a favor and drop a linky? Happy to make a donation again this year.

Ta- C
Carl Avari-Cooper, KTPA

Gary Oliver

Quote from: cavaricooper on Wed, 25 Oct 2017 15:01
@Mark, will attempt to refine at my end.

@Gary- If you have a spiffy new G-BNLG ready for WorldFlight, incorporating all of Mark's wizardry, would you do the village idiot a favor and drop a linky? Happy to make a donation again this year.

Ta- C

On the case...

Kockie69

Mark,

I run everything locally, so I made no changes to the xml's. The router is still not connecting to the client.

PSX.NET.P3D.ExternalSim.Router 2.4.0
Started at: 25/10/2017 18:55:49 (UTC)
Currently:  25/10/2017 18:59:42 (UTC)

---PSX Received Counts---------------------------
Boost:                    16161
PSX:                      87
---Published Counts------------------------------
FlightModel:              16160
TimeModel:                1
GearModel:                113
FlapModel:                113
LightingModel:            113
SpoilerModel:             112
ControlSurfaceModel:      112
TransponderModel:         113
BatteryModel:             113
ParkingBrakeModel:        113
RadioModel:               113
EngineModel:              111
---P3D Data-------------------------------------
FeedbackModel:            0
Ground Elevation(m):      NaN
---Misc-----------------------------------------
PSX elevation updates:    0
PSX time:                 25/10/2017 18:59:40
Primary P3D Machine Name:
Last 'load1'              25/10/2017 18:55:54 (UTC)

---Clients--------------------------------------
No clients.

It all worked fine with previous version of ExternalSim.

Any help appreciated.

Kr Robert

JohnH

Quote from: Kockie69 on Wed, 25 Oct 2017 20:00
Mark,

I run everything locally, so I made no changes to the xml's. The router is still not connecting to the client.

PSX.NET.P3D.ExternalSim.Router 2.4.0
Started at: 25/10/2017 18:55:49 (UTC)
Currently:  25/10/2017 18:59:42 (UTC)

---PSX Received Counts---------------------------
Boost:                    16161
PSX:                      87
---Published Counts------------------------------
FlightModel:              16160
TimeModel:                1
GearModel:                113
FlapModel:                113
LightingModel:            113
SpoilerModel:             112
ControlSurfaceModel:      112
TransponderModel:         113
BatteryModel:             113
ParkingBrakeModel:        113
RadioModel:               113
EngineModel:              111
---P3D Data-------------------------------------
FeedbackModel:            0
Ground Elevation(m):      NaN
---Misc-----------------------------------------
PSX elevation updates:    0
PSX time:                 25/10/2017 18:59:40
Primary P3D Machine Name:
Last 'load1'              25/10/2017 18:55:54 (UTC)

---Clients--------------------------------------
No clients.

It all worked fine with previous version of ExternalSim.

Any help appreciated.

Kr Robert

Which 747 model are you using in P3D?, do you have more than one livery installed in the 747 model?

John

Frans Spruit

Hi John,

I have the same problem as Robert I use the Posky: PSX_747

Frans Spruit

JohnH

Quote from: Frans Spruit on Wed, 25 Oct 2017 21:16
Hi John,

I have the same problem as Robert I use the Posky: PSX_747

Frans Spruit

open the aircraft.cfg file in the Posky: PSX_747 folder, do you see the entry, ExternalSimID={3E6B47E7-C706-4A10-BC88-6E7C199ED5A6} in the [fltsim.0] section?

Frans Spruit

Hi John,

[fltsim.0]
title=Boeing 747-400 British Airways
sim=Project Opensky Boeing 747 Series
model=
panel=
sound=
texture=BAW
checklists=
ExternalSimID={3E6B47E7-C706-4A10-BC88-6E7C199ED5A6}








Frans Spruit


Open ExternalSim XML(P3D V4)

<?xml version="1.0"?>
<Settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <SettingsVersion>1</SettingsVersion>
  <RouterSubAddress>tcp://localhost:10760</RouterSubAddress>
  <FeedbackPubAddress>tcp://localhost:10761</FeedbackPubAddress>
  <DebugPubBind />
  <DebugLogToFile>false</DebugLogToFile>
</Settings>


Open ExternalSim Router XML

<?xml version="1.0"?>
<Settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <SettingsVersion>1</SettingsVersion>
  <PsxBoostIP>127.0.0.1</PsxBoostIP>
  <PsxServerIP>127.0.0.1</PsxServerIP>
  <PsxServerPort>10747</PsxServerPort>
  <RouterPubBind>tcp://*:10760</RouterPubBind>
  <FeedbackSubBind>tcp://*:10761</FeedbackSubBind>
  <TimeSync>true</TimeSync>
  <MinWeightModelOffsetM>4.4</MinWeightModelOffsetM>
  <PrimaryP3DMachineName />
</Settings>

Britjet

I think you have to put an IP in place of the asterisks in the External Router xml.
Peter

Mark

Hi all,

I use Slack for work and a few other common interest groups - it's a real time chat with rich media features (image/video/audio/note) sharing.

If anyone wishes to discuss their ExternalSim issues in a more real-time fashion, click here to sign up.

Otherwise please continue to use this thread.

simbro

I'm also experiencing the same problem as Robert and Frans.

Both XMLs are setup according to the docs and as shown in this thread,.
The aircraft.cfg file also contains the required 'ExternalSimID' entry.

However, P3D (v4.0) is not connecting to the router.  (no client is listed there)

Just a thought... I'm using a german version of Win7. Could this be an issue?
v2.31 worked perfectly so probably not!

regards, Simon



cavaricooper

Mark-

Have you received any other reports of the TIME MODEL not climbing at the same rate as the others? Mine seems perpetually stuck at 1 or sometimes 2.... and the only way to "sync" time with P3d is to restart ExternalSim....

Best- C
Carl Avari-Cooper, KTPA

simbro

I've finally got it working after updating P3D to v4.1 (from v4.0)

Uninstalling the v4.0 Client and installing the v4.1 Client solved the problem instantly...  No need to reinstall/modify ExternalSim or anything else - it worked 'out of the box'!

Could it be that P3D v4.1 is a requirement for ExternalSim 2.4.0 ?

regards, Simon

Mark

#499
Quote from: simbro on Fri, 27 Oct 2017 06:26
Could it be that P3D v4.1 is a requirement for ExternalSim 2.4.0 ?

Sounds like you've found the cause, thank you.

I'm always on the latest relevant version (and the corresponding SDK) so that's 4.1.7.22841 and 3.4.22.19868 currently. I'll keep these versions for longer - I don't think any new 4.x updates will add anything that I need in the SDK.