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

J D ADAM

Hi Gary/Mark

Would you consider reviewing External Sim (after Vatsim and World Flight) to allow the program to work in conjunction with  GSX. Another words sending "engines are shut down and park brake is set" to P3d.
Just adds a little more immersion  to our flying.
Thank you in anticipation.

Derek Adam
NZAA

kong sun choi

Hi, Mark
I have same problem .
I use 3 computer multi play.
1 prepar3d server, 2 aerowinx 747 client and the other is instructor computer and prepar3D atc map use.

I check this situation as I attached a image.

can you help me how to show on PSX 744 on multi play radal?

instructor station and other prepar3d atc map can not show aerowinx 744 AI and show AI information.

all computer's firewall is off.

Thank you.



kong sun choi

Hi,

please help me and check this point.

the source below is part of polsky 747 aircraft.cfg file of P3D Airplane file.
ExternalSimID = {3E6B47E7-C706-4A10-BC88-6E7C199ED5A6}
Category = ExternalSim
Setting two eliminates the multiplay radar and works well with Aerowinx.
Clear ExternalSimID = {3E6B47E7-C706-4A10-BC88-6E7C199ED5A6}

If  change Category = airplane, it will come out of multiplay radar normally.
It is not possible to link with Aerowinx.

I want to multi play link and show PSX 747 AI for other player's ATC map and addon Instructor monitor.


[fltsim.0]
title=Boeing 747-400 British Airways
sim=Project Opensky Boeing 747 Series
model=744x
panel=
sound=
texture=BAW
//ExternalSimID ={3E6B47E7-C706-4A10-BC88-6E7C199ED5A6}
//ExternalSimModule = PSX.NET.P3D.ExternalSim.dll
atc_id=N400GE
atc_airline=BOEING
atc_flight_number=043
atc_heavy=1
atc_parking_types=GATE, RAMP
atc_parking_code=BAW


ui_manufacturer=Boeing
ui_type=747-400V4
ui_typerole=Commercial Airliner
ui_createdby=Project Opensky
ui_variation=Boeing DreamLiner

visual_damage=1
description=Project Opensky \nBoeing 747-400\nVersion 2006.9.6-FSX\n\nEngine Type RR RB-211-524HT\n\n747-400 Commercial Version \n\nModel Designer\n   Chang Yeon, Vincent Cho  \n\nFlight Dynamics Designers\n   Warren C. Daniel\n   Brandon D. Henry\n\n   Test Pilots\n   Project Opensky Members\n\nMaximun Range: 7305 nm\n\nFor proper operation: See B747 manual at: \n  www.projectopensky.com


[General]
performance=Passengers\n3-class conf: 524 \n2-class conf: 416 \n1-class conf: N\/A\n\nCargo\nTotal lower hold volume:\n   5,497 ft3 (155.6 m3)  \n\nDimensions\nSpan 211 ft 5 in (213 ft -- fueled)\nLength 231 ft 10 in\nHeight 63 ft 5 in\n\nEngines: GE CF6-80C2B1\nTO Thrust: 54,750 lb x 4\n\nMax Fuel Cap.: 57,065 US Gal.\nMaxTOW: 877,000 lbs\nMLW: 630,000 lbs\nMax Payload: 148,716 lbs\nOEW: 394,660 lbs\n\nMax Range: 7305 mi   \nTypical Cruise Speed \n   @ FL350: M.85

atc_type=BOEING AIRCRAFT
atc_model=B744
editable=0
//Category= ExternalSim
Category= airplane

The source above is part of aircraft.cfg file of P3D Airplane file.
ExternalSimID = {3E6B47E7-C706-4A10-BC88-6E7C199ED5A6}
Category = ExternalSim
Setting two eliminates the multiplay radar and works well with Aerowinx.
Clear ExternalSimID = {3E6B47E7-C706-4A10-BC88-6E7C199ED5A6}

If you change Category = airplane, it will come out of multiplay radar normally.
It is not possible to link with Aerowinx.

check this please












matchball

Is there currently any free way to insert aloft wind data (etc) to the PSX? I have access to Active Sky and PFPX should they be required.

matchball

#684
Anyone able to help with this? I have tried turning firewall off. Tried using the mmc actions for firewall...

Two days ago I flew using PSX.NET a flight of roughly 8 hours. Everything worked flawlessly. However yesterday I ran into issues. The P3D would not link to PSX. After several restarts, firewall tuning, I got the p3d to sync. All went fine until I was about to land and opene P3D. Water everywhere... Looking at the data from P3D, the airplane had synced everything correctly (at least from what I saw) except the logitude data. Aka the plain flew in bullet straight line though replicated speed and altitude changes correctly.

Track time   Latitude   Longitude   Altitude   Ground Speed   Leg
2019-11-18 14:35:58   -33.022031   -70.810417   11930 ft   377 kts   
2019-11-18 14:39:03   -32.839612   -71.123945   18023 ft   426 kts   SCEL-MYNN
2019-11-18 14:42:08   -32.482596   -71.198495   22839 ft   459 kts   SCEL-MYNN
2019-11-18 14:45:13   -32.078212   -71.200506   26474 ft   484 kts   SCEL-MYNN
2019-11-18 14:48:18   -31.659931   -71.200506   29904 ft   486 kts   SCEL-MYNN
2019-11-18 14:51:23   -31.247342   -71.200506   32005 ft   480 kts   SCEL-MYNN
2019-11-18 14:54:28   -30.837119   -71.200506   32004 ft   479 kts   SCEL-MYNN
2019-11-18 14:57:33   -30.428386   -71.200506   32005 ft   478 kts   SCEL-MYNN
2019-11-18 15:00:38   -30.019258   -71.200506   32005 ft   479 kts   SCEL-MYNN
2019-11-18 15:03:43   -29.611318   -71.200506   32005 ft   478 kts   SCEL-MYNN
2019-11-18 15:06:48   -29.203458   -71.200506   32004 ft   478 kts   SCEL-MYNN
2019-11-18 15:09:53   -28.797174   -71.200506   32005 ft   476 kts   SCEL-MYNN
2019-11-18 15:12:58   -28.391362   -71.200506   32031 ft   472 kts   SCEL-MYNN
2019-11-18 15:16:03   -27.987188   -71.200506   32031 ft   477 kts   SCEL-MYNN
2019-11-18 15:19:08   -27.582543   -71.200506   32032 ft   471 kts   SCEL-MYNN
2019-11-18 15:22:13   -27.17973     -71.200506   32032 ft   476 kts   SCEL-MYNN
2019-11-18 15:25:18   -26.775162   -71.200506   32032 ft   472 kts   SCEL-MYNN
2019-11-18 15:28:23   -26.371258   -71.200506   32032 ft   476 kts   SCEL-MYNN
2019-11-18 15:31:28   -25.967396   -71.200506   32033 ft   471 kts   SCEL-MYNN
2019-11-18 15:34:33   -25.565508   -71.200506   32006 ft   469 kts   SCEL-MYNN
2019-11-18 15:37:38   -25.16557     -71.200506   32006 ft   469 kts   SCEL-MYNN
2019-11-18 15:40:43   -24.76389       -71.200506   32004 ft   471 kts   SCEL-MYNN
2019-11-18 15:43:48   -24.361104   -71.200506   32005 ft   471 kts   SCEL-MYNN
2019-11-18 15:46:53   -23.957165   -71.200506   32005 ft   472 kts   SCEL-MYNN
2019-11-18 15:49:58   -23.552468   -71.200506   32005 ft   470 kts   SCEL-MYNN
2019-11-18 15:53:03   -23.147652   -71.200506   32005 ft   473 kts   SCEL-MYNN
2019-11-18 15:56:08   -22.745651   -71.200506   32006 ft   469 kts   SCEL-MYNN
2019-11-18 15:59:13   -22.34443      -71.200506   32005 ft   468 kts   SCEL-MYNN
2019-11-18 16:02:18   -21.943101   -71.200506   32005 ft   469 kts   SCEL-MYNN
2019-11-18 16:05:23   -21.54152           -71.200506   32005 ft   469 kts   SCEL-MYNN
2019-11-18 16:08:28   -21.141103   -71.200506   32005 ft   468 kts   SCEL-MYNN
2019-11-18 16:11:33   -20.740203   -71.200506   31978 ft   468 kts   SCEL-MYNN
2019-11-18 16:14:38   -20.335174   -71.200506   31978 ft   480 kts   SCEL-MYNN
2019-11-18 16:17:43   -19.925728   -71.200506   31978 ft   479 kts   SCEL-MYNN
2019-11-18 16:20:48   -19.513763   -71.200506   31977 ft   479 kts   SCEL-MYNN
2019-11-18 16:23:53   -19.110623   -71.200506   31977 ft   476 kts   SCEL-MYNN
2019-11-18 16:26:58   -18.70703           -71.200506   31977 ft   477 kts   SCEL-MYNN
2019-11-18 16:30:03   -18.303131   -71.200506   31978 ft   488 kts   SCEL-MYNN
2019-11-18 16:33:08   -17.890429   -71.200506   32004 ft   490 kts   SCEL-MYNN
2019-11-18 16:36:13   -17.477749   -71.200506   32077 ft   496 kts   SCEL-MYNN
2019-11-18 16:39:18   -17.056767   -71.200506   32178 ft   498 kts   SCEL-MYNN
2019-11-18 16:42:23   -16.642757   -71.200506   32279 ft   497 kts   SCEL-MYNN
2019-11-18 16:45:28   -16.217905   -71.200506   32334 ft   508 kts   SCEL-MYNN
2019-11-18 16:48:33   -15.812119   -71.200506   34304 ft   488 kts   SCEL-MYNN
2019-11-18 16:51:38   -15.399124   -71.200506   34497 ft   489 kts   SCEL-MYNN
2019-11-18 16:54:43   -14.989071   -71.200506   34499 ft   488 kts   SCEL-MYNN
2019-11-18 16:57:48   -14.578673   -71.200506   34498 ft   489 kts   SCEL-MYNN
2019-11-18 17:00:53   -14.167959   -71.200506   34499 ft   489 kts   SCEL-MYNN
2019-11-18 17:03:58   -13.755936   -71.200506   34499 ft   493 kts   SCEL-MYNN
2019-11-18 17:07:03   -13.342975   -71.200506   34499 ft   490 kts   SCEL-MYNN
2019-11-18 17:10:08   -12.931971   -71.200506   34499 ft   490 kts   SCEL-MYNN
2019-11-18 17:13:13   -12.521463   -71.200506   34500 ft   490 kts   SCEL-MYNN
2019-11-18 17:16:18   -12.109476   -71.200506   34499 ft   491 kts   SCEL-MYNN
2019-11-18 17:19:23   -11.697448   -71.200506   34499 ft   491 kts   SCEL-MYNN
2019-11-18 17:22:28   -11.284461   -71.200506   34499 ft   493 kts   SCEL-MYNN
2019-11-18 17:25:33   -10.870542   -71.200506   34498 ft   493 kts   SCEL-MYNN
2019-11-18 17:28:38   -10.45593           -71.200506   34499 ft   495 kts   SCEL-MYNN
2019-11-18 17:31:43   -10.037038   -71.200506   34435 ft   502 kts   SCEL-MYNN
2019-11-18 17:34:48   -9.614626   -71.200506   34339 ft   504 kts   SCEL-MYNN
2019-11-18 17:37:53   -9.19088   -71.200506   34280 ft   501 kts   SCEL-MYNN
2019-11-18 17:40:58   -8.770651   -71.200506   34347 ft   499 kts   SCEL-MYNN
2019-11-18 17:44:03   -8.350833   -71.200506   34248 ft   502 kts   SCEL-MYNN
2019-11-18 17:47:08   -7.930453   -71.200506   34147 ft   502 kts   SCEL-MYNN
2019-11-18 17:50:13   -7.50852   -71.200506   34046 ft   504 kts   SCEL-MYNN
2019-11-18 17:53:18   -7.081036   -71.200506   33946 ft   514 kts   SCEL-MYNN
2019-11-18 17:56:23   -6.643008   -71.200506   33877 ft   523 kts   SCEL-MYNN
2019-11-18 17:59:28   -6.208198   -71.200506   33877 ft   517 kts   SCEL-MYNN
2019-11-18 18:02:33   -5.768067   -71.200506   33876 ft   524 kts   SCEL-MYNN
2019-11-18 18:05:38   -5.330951   -71.200506   33877 ft   521 kts   SCEL-MYNN
2019-11-18 18:08:43   -4.891131   -71.200506   33865 ft   505 kts   SCEL-MYNN
2019-11-18 18:11:47   -4.481168   -71.200506   33851 ft   492 kts   SCEL-MYNN
2019-11-18 18:14:48   -4.064304   -71.200506   33849 ft   505 kts   SCEL-MYNN
2019-11-18 18:17:53   -3.651988   -71.200506   33849 ft   493 kts   SCEL-MYNN
2019-11-18 18:20:57   -3.216157   -71.200506   33893 ft   518 kts   SCEL-MYNN
2019-11-18 18:24:03   -2.774707   -71.200506   33893 ft   519 kts   SCEL-MYNN
2019-11-18 18:27:07   -2.333402   -71.200506   33895 ft   504 kts   SCEL-MYNN
2019-11-18 18:30:12   -1.916246   -71.200506   33930 ft   490 kts   SCEL-MYNN
2019-11-18 18:33:13   -1.510294   -71.200506   33931 ft   491 kts   SCEL-MYNN
2019-11-18 18:36:17   -1.093141   -71.200506   33931 ft   491 kts   SCEL-MYNN
2019-11-18 18:39:22   -0.67479   -71.200506   33932 ft   493 kts   SCEL-MYNN
2019-11-18 18:42:27   -0.255962   -71.200506   33931 ft   493 kts   SCEL-MYNN
2019-11-18 18:45:32   0.16394   -71.200506   33931 ft   494 kts   SCEL-MYNN
2019-11-18 18:48:37   0.585953   -71.200506   34006 ft   496 kts   SCEL-MYNN
2019-11-18 18:51:43   1.008876   -71.200506   34107 ft   497 kts   SCEL-MYNN
2019-11-18 18:54:47   1.432756   -71.200506   34208 ft   499 kts   SCEL-MYNN
2019-11-18 18:57:52   1.85739   -71.200506   34296 ft   501 kts   SCEL-MYNN
2019-11-18 19:00:57   2.281828   -71.200506   34298 ft   500 kts   SCEL-MYNN
2019-11-18 19:04:03   2.707531   -71.200506   34296 ft   500 kts   SCEL-MYNN
2019-11-18 19:07:07   3.133804   -71.200506   34298 ft   502 kts   SCEL-MYNN
2019-11-18 19:10:12   3.560472   -71.200506   34298 ft   502 kts   SCEL-MYNN
2019-11-18 19:13:17   3.988766   -71.200506   34298 ft   504 kts   SCEL-MYNN
2019-11-18 19:16:22   4.420183   -71.200506   34277 ft   503 kts   SCEL-MYNN
2019-11-18 19:19:27   4.847951   -71.200506   34279 ft   504 kts   SCEL-MYNN
2019-11-18 19:22:32   5.286177   -71.200506   34241 ft   531 kts   SCEL-MYNN
2019-11-18 19:25:37   5.620723   -71.200506   34245 ft   528 kts   SCEL-MYNN
2019-11-18 19:28:42   6.070943   -71.200506   36241 ft   532 kts   SCEL-MYNN
2019-11-18 19:31:47   6.509632   -71.200506   36159 ft   509 kts   SCEL-MYNN
2019-11-18 19:34:52   6.949202   -71.200506   36058 ft   515 kts   SCEL-MYNN
2019-11-18 19:37:57   7.39116   -71.200506   35958 ft   517 kts   SCEL-MYNN
2019-11-18 19:41:02   7.834645   -71.200506   35868 ft   519 kts   SCEL-MYNN
2019-11-18 19:44:07   8.277352   -71.200506   35859 ft   515 kts   SCEL-MYNN
2019-11-18 19:47:12   8.719161   -71.200506   35859 ft   514 kts   SCEL-MYNN
2019-11-18 19:50:17   9.162585   -71.200506   35859 ft   522 kts   SCEL-MYNN
2019-11-18 19:53:22   9.609567   -71.200506   35866 ft   523 kts   SCEL-MYNN
2019-11-18 19:56:27   10.05788   -71.200506   35867 ft   524 kts   SCEL-MYNN
2019-11-18 19:59:32   10.506422   -71.200506   35868 ft   524 kts   SCEL-MYNN
2019-11-18 20:02:37   10.954821   -71.200506   35869 ft   533 kts   SCEL-MYNN
2019-11-18 20:05:42   11.39467           -71.200506   35868 ft   529 kts   SCEL-MYNN
2019-11-18 20:08:47   11.835907   -71.200506   35869 ft   532 kts   SCEL-MYNN
2019-11-18 20:11:52   12.276478   -71.200506   35869 ft   531 kts   SCEL-MYNN
2019-11-18 20:14:57   12.71809           -71.200506   35868 ft   532 kts   SCEL-MYNN
2019-11-18 20:18:02   13.15748       -71.200506   35903 ft   531 kts   SCEL-MYNN
2019-11-18 20:21:07   13.596989   -71.200506   35902 ft   530 kts   SCEL-MYNN
2019-11-18 20:24:12   14.036651   -71.200506   35859 ft   531 kts   SCEL-MYNN
2019-11-18 20:27:17   14.476799   -71.200506   35876 ft   533 kts   SCEL-MYNN
2019-11-18 20:30:22   14.917322   -71.200506   35876 ft   532 kts   SCEL-MYNN
2019-11-18 20:33:27   15.357531   -71.200506   35877 ft   530 kts   SCEL-MYNN
2019-11-18 20:36:32   15.797531   -71.200506   35877 ft   531 kts   SCEL-MYNN
2019-11-18 20:39:37   16.237068   -71.200506   35876 ft   529 kts   SCEL-MYNN
2019-11-18 20:42:42   16.67598          -71.200506   35877 ft   530 kts   SCEL-MYNN
2019-11-18 20:45:47   17.114525   -71.200506   35877 ft   528 kts   SCEL-MYNN
2019-11-18 20:48:52   17.552345   -71.200506   35876 ft   529 kts   SCEL-MYNN
2019-11-18 20:51:57   17.989942   -71.200506   35877 ft   528 kts   SCEL-MYNN
2019-11-18 20:55:02   18.432775   -71.200506   35898 ft   533 kts   SCEL-MYNN
2019-11-18 20:58:07   18.878514   -71.200506   35905 ft   532 kts   SCEL-MYNN
2019-11-18 21:01:12   19.322235   -71.200506   35931 ft   526 kts   SCEL-MYNN
2019-11-18 21:04:17   19.764202   -71.200506   34006 ft   509 kts   SCEL-MYNN
2019-11-18 21:07:22   20.187793   -71.200506   35932 ft   528 kts   SCEL-MYNN
2019-11-18 21:10:27   20.629461   -71.200506   35932 ft   531 kts   SCEL-MYNN
2019-11-18 21:13:32   21.083754   -71.200506   35932 ft   531 kts   SCEL-MYNN
2019-11-18 21:16:37   21.537968   -71.200506   35932 ft   531 kts   SCEL-MYNN
2019-11-18 21:19:42   21.987142   -71.200506   35932 ft   518 kts   SCEL-MYNN
2019-11-18 21:22:47   22.432309   -71.200506   35940 ft   519 kts   SCEL-MYNN
2019-11-18 21:25:52   22.867946   -71.200506   32650 ft   474 kts   SCEL-MYNN
2019-11-18 21:28:57   23.264013   -71.200506   27070 ft   442 kts   SCEL-MYNN
2019-11-18 21:32:02   23.617901   -71.200506   21920 ft   380 kts   SCEL-MYNN
2019-11-18 21:35:07   23.941547   -71.200506   16895 ft   359 kts   SCEL-MYNN
2019-11-18 21:38:12   24.235935   -71.200506   12218 ft   340 kts   SCEL-MYNN
2019-11-18 21:41:17   24.499305   -71.200506   9036 ft   276 kts   SCEL-MYNN
2019-11-18 21:44:22   24.728771   -71.200506   5750 ft   263 kts   SCEL-MYNN

petdocvmd

I have the Lat/Lon = 0,0 issue on startup.  My setup:

Win 10
PSX 10.93 running as Server/Boost Server and client
Prepar3D v4.5.13
Posky 747 from p15 link
PSX.NET ExternalSim 2.5 installed as per instructions in the zip.

All are on the same PC.  PSX runs fine, and I've driven X-Plane 11 with XView on this same PC.  In P3D, however, I start surrounded by ocean :-(

The aircraft.cfg file appears to have been correctly configured:

[fltsim.0]
ExternalSimID={3E6B47E7-C706-4A10-BC88-6E7C199ED5A6}
[General]
Category=ExternalSim


I scoured the posts for this issue, but can't see an obvious solution.  Are there any known add-on conflicts?  P3D setting changes I need to do that I might have missed?

Thanks!

Scott
Scott L. Fausel, VMD

JohnH

Hi Scott,

Every now and then I get this situation. To correct it I simply stop P3D ExternalSim Router then restart it. This always seem to correct the issue.

John

petdocvmd

Quote from: JohnH on Thu, 16 Jan 2020 17:39
Hi Scott,

Every now and then I get this situation. To correct it I simply stop P3D ExternalSim Router then restart it. This always seem to correct the issue.

John

Do I need the Router if everything is on the same PC?  It didn't sound like it from the directions, so I did not configure or start it...

Scott
Scott L. Fausel, VMD

JohnH

yes you do, this is from the instructions,,

Note: This is normally the same PC running your PSX boost instance (recommended). 
See section Example system diagrams in this document for ideas.

Run PSX.NET.P3D.ExternalSim.Router.Installer.msi
PSX.NET.P3D.ExternalSim.Configuration.Installer.msi (if not already installed)

There will now be a 'PSX.NET' folder on the Start Menu containing a 'P3D.ExternalSim.Router' shortcut for running the router application.

This is also important,,

Order of starting applications:
1. PSX boost instance.

If you're running a PSX boost instance, ensure there is a working connection to your main simulator instance.

2. ExternalSim Router.

Ensure that the 'Boost' and 'PSX' numbers in the 'PSX Received Counts' section is increasing (wait 20 seconds after router started before checking).  If not, check your <PsxBoostIP>, <PsxServerIP> and <PsxServerPort> settings are correct and restart router.

3. P3D instance(s) running PSX.NET P3D ExternalSim.

Data flows in 2 directions. Both directions need to be allowed through any firewall(s). Router to Client: If the P3D aircraft isn't moving when PSX moves, this connection has been blocked by a firewall. Client to Router: If your P3D instance has established a successful connection then you will see it appear as a client in the router console output. If not, this connection has been blocked by a firewall.

John
 

petdocvmd

Thanks - I clearly misread...will install the router module and re-test.

Appreciate the help!

Scott
Scott L. Fausel, VMD

petdocvmd

Well, I installed PSX.NET ExternalSim Router, but I cannot run the app.  When I attempt to start it, a command prompt box opens and I get a fleeting glimpse of an "unhandled exception error" before the box closes. I tried uninstalling and re-installing, as well as restarting the PC, to no avail.  Nor did running it as an admin work.  Help!

Thanks,

Scott
Scott L. Fausel, VMD

Jeroen Hoppenbrouwers

Instead of starting it by double-click, try starting a CMD box first and then navigating (cd) to the folder and manually typing the name to start it. This should allow you to actually read the panic message.


Hoppie

petdocvmd

Quote from: Jeroen Hoppenbrouwers on Fri, 17 Jan 2020 09:05
Instead of starting it by double-click, try starting a CMD box first and then navigating (cd) to the folder and manually typing the name to start it. This should allow you to actually read the panic message.

Unfortunately, this did not work.  The program opened in a *second* window, and snapped shut quickly.  By running it a few times, I caught glimpses of the words "parameter" and "height" amongst the gobbledy-gook.

I did another uninstall, aided by manually removing vestigial folders in Program Files (x86) and the user roaming  section, then reinstalled.  Still no go.  I tried installing it on my Win 10 laptop (same update level) and it opened perfectly.

I want to get this solved correctly, but perhaps a workaround would be to run the Router component on my laptop and point it to the desktop PC running PSX, while pointing P3DExternalSim over to the laptop Router?

I just don't understand why the router won't even open on my pretty typical Win 10 box  :'(

Scott
Scott L. Fausel, VMD

Adrian FW

Hi Scott,

I have almost exactly the same single PC WIN10 configuration as you though I also run a second PC with the FO view.  I too had the same problem on initial setup.  First the quick view of the PSX.NET Router window and then the Lat/Long 0,0 Ocean view.  I fixed it after a while and I'm sorry to say I can't remember the fix.  Nevertheless here is how I start and connect PSX and P3D.  Firewall is off on both PC's.

1) Start PSX on PC1 with the Main Server running
2) Start PSX as client on PC2 (FO Setup)
3) Start P3D (I remember initially having to ensure Slew Mode and Pause on Task Switch is unchecked)
4) Start ActiveSky
4) Start PSX Boost Server on PC1
5) Start PSX.NET Router

Adrian

JohnH

#694
QuoteUnfortunately, this did not work.  The program opened in a *second* window, and snapped shut quickly.  By running it a few times, I caught glimpses of the words "parameter" and "height" amongst the gobbledy-gook.

I did another uninstall, aided by manually removing vestigial folders in Program Files (x86) and the user roaming  section, then reinstalled.  Still no go.  I tried installing it on my Win 10 laptop (same update level) and it opened
perfectly.

I want to get this solved correctly, but perhaps a workaround would be to run the Router component on my laptop and point it to the desktop PC running PSX, while pointing P3DExternalSim over to the laptop Router?

I just don't understand why the router won't even open on my pretty typical Win 10 box  :'(

Scott

What is weird is it does not seem to be a connection issue as you can't even run the router? Just a wild guess but do you have .NET framework installed on the desktop computer?

John



Hoppie fixed a missing Open Quote mark

petdocvmd

#695
Quote from: JohnH on Fri, 17 Jan 2020 20:52
What is weird is it does not seem to be a connection issue as you can't even run the router? Just a wild guess but do you have .NET framework installed on the desktop computer?

John


Yep, I verified I have .net fw v 4.8.  FWIW, Bacars works perfectly.

Still troubleshooting...

Scott
Scott L. Fausel, VMD

petdocvmd

I have it working, though I'm not quite sure exactly what was wrong.  Here is what I did, in case someone down the road encounters a similar problem.

I suspected my issue had to do with my HDTV third monitor, if only because of the "parameter" and "height" text I saw briefly when the app crashed.  Prior to reinstalling PSX.NET P3D ExternalSim again, I unchecked the "Make this my main monitor" box for the HDTV (setting it to my 27" monitor), changed it's zoom setting from 150% to 100%, and then inactivated it.  I then reinstalled PSX.NET and ran the configurator.  I started PSX and found that my display changes caused its windows to become oversized, and its zoom settings to be too great. Oddly, my USB preferences were also scrambled - both axes and buttons.  I restored the HDTV, closed and re-opened PSX, but no change.   I reconfigured and saved everything, then fired up PSX.NET P3D ExternalSim Router....and it opened!  P3D opened, and loading the PSX 737 worked perfectly - I was able to fly the tutorial flight without a hitch.

After all that, I was disappointed to find that my frame rates were poor in P3D - about 12-20, and improved only marginally with significant reduction in P3D display options.  I was getting 20-30 with my PMDG 737NGXu, and 35-60 in X-Plane 11 with PSX and Xview.  So it looks like PSX/P3D combo will have to wait for my new simming PC ;-)

Scott
Scott L. Fausel, VMD

Martin Baker

I'm using ExternalSim to connect PSX to P3D, using the BOAC model provided. Whenever I switch the beacon to "Both" the P3D model's flaps fully deploy and vice versa. Can anyone tell me what to do to avoid this?

CHEDHKG

Good day gents,

I recently switched from FSX to P3d and therefore trying to have P3D.EternalSim to work on my set up.

I kind of managed to have everything up and running, given my very weird set-up:

Only one computer running Archlinux and one Virtual Machine (VM) on that computer running Win10 via GPU passthrough. The main PSX is on the linux box, while P3D is on the VM.
All seems to be more or less working well, except for some very strange behaviour of P3D.EternalSim.


Every now and then, P3D resets himself (reloading Terrain Data) but then it places the aircraft on the ground and on a very weird map location.
For example, I was making a hold near EHAM (over DENUT fix) and after reloading, P3D set the aircraft close to Alaska, in the middle of the ocean at altitude zero.
I figured out that he kept the last latitude (Around N51 20.3) but the longitude was set to W176 (which funny enough is the complement to 180 of DENUT's latitude at E003 54.3).

In order to get everything back properly, I have to stop the router P3D, and restart both.


I am trying to figure out what can trigger such a behaviour. Seems this happens when P3D tries to update some terrain info (or time synch) but it might happen a few seconds after P3D was launched, or on the contrary after a few minutes or hours.

If someone has any clue on where to look or what I could to to debug further, it would be much appreciated !

-Stephan


JohnH

Hi Stephan,

Check your firewall setting in Windows 10. Go to settings, update and security, windows security (on the left side) then Firewall & network protection. I have Domain network 'on', Private network 'off', Public network 'on'. Also it was mentioned in a previous thread to check your P3D traffic settings and turn them off to see if that helps? This can be found in P3D, Options, General, Traffic.

John