PSX.NET.MSFS.WASM Version 10 - The Next Generation MSFS Scenery Link For PSX

[Holger Wende]

Hi Bode,

Thanks for the link but my networked PSX instances work perfectly fine across 2 machines. I can even swap PSX server and client between the 2 machines, this works like a charm.
Only for debugging the MSFS freeze issue I started only one main server instance of PSX.

But the suggestion of FlyItLikeYouStoleIt to run PSX, PSX.NET.MSFS.Router, PSX.NET.MSFS.Client and MSFS all on the same machine does not freeze MSFS. But I wanted to have MSFS and PSX on separate machines intentionally.

Now I wonder why running PSX main server and PSX.NET.MSFS.Router on a dedicated PSX machine and PSX.NET.MSFS.Client together with MSFS on the other MSFS machine freezes MSFS immediately when the PSX.NET.MSFS.Client MSFS Link Connected indicator goes green.

This is not about the MSFS crash detection, it is disabled as recommended by Gary. I just guess it is something with the networked traffic.

It remains weird to me.

Anyways thanks for your help.

[Gary Oliver]

All sounds very weird... I run router on PSX server and all my MSFS clients on other machines and no problem.

Just to confirm... PSX Server which runs boost server set to 60/3 on the FPS settings?

Regional settings? Do we have a comma and decimal problem I dont know about ?

[Holger Wende]

Hi Gary,

When you talk about Router I assume you mean your PSX.NET.MSFS.Router, not Hoppies PSX Router?

Machine A runs PSX main server plus boost server, frame rate 60/3 and it runs PSX.NET.MSFS.Router.
Machine B runs MSFS and PSX.NET.MSFS.Client.
This scenario freezes MSFS.

If I run everything on only one machine there is no problem.

I did not check comma or decimal point settings. I will inspect and the settings on the 2 machines.

Do I need to install Simconnect or anything else to run PSX.NET?

[Jeroen Hoppenbrouwers]

Double check windows firewall on both machines.

[Holger Wende]

Firewall, that was it, well spotted by awesome Jeroen! 

The setup tools seem to install 2 executables each for the Router and the Client, i.e. in total 4 PSX.NET.*.exe files.

Code Select Expand

%LocalAppData%/Apps/2.0/*/*/psx....exe_ac490f5894c4d900_000a.0001_none_f5e296b908c042b0/PSX.NET.MSFS.Client.exe
%LocalAppData%/Apps/2.0/*/*/psx....exe_cb33b5c341bbd42d_000a.0001_none_7a6b04a1a2e9e2ac/PSX.NET.MSFS.Router.exe
%LocalAppData%/Apps/2.0/*/*/psx...tion_ac490f5894c4d900_000a.0001_5d816f60f14b9191/PSX.NET.MSFS.Client.exe
%LocalAppData%/Apps/2.0/*/*/psx...tion_cb33b5c341bbd42d_000a.0001_f59839d2009b57f9/PSX.NET.MSFS.Router.exe

However the firewall had one entry for the second Router executable only but not the first one and no entry of the Client executabes.
For now I also added the 2 Client executables plus the missing Router entry. Will have to verify whether the Client entries are really needed.

Additional observation:

MSFS does not (yet) show rudder, aileron and elevator movements nor do speed brakes deploy.
But to me this is just cosmetics, I do not recall whether this was mentioned before already.

Thanks to all!

Best regards, Holger

Edit:
Animated rudder, aileron and elevator are already on Garys to-do list 

[Torben]

For now I also added the 2 Client executables plus the missing Router entry.

Could you explain how this can be done?

[Holger Wende]

It may depend on the internet security/anti-virus protection package installed on your system(s).
I have a German Windows 10 installation with Windows Defender Firewall.
Hopefully my English translations helps to follow the correct English entries. For other internet security packages the process should be similar.

Before you start verify the psx.net *.exe files exist under the mentioned paths as listed in my previous post. You may need to search a bit using a file browser due to the installation specific subfolders "%LocalAppData%/Apps/2.0/*/*".

Steps:
1. Open windows settings from the windows start menue
2. Search for "firewall", select "Firewall and network protection"
3. Follow a link named "Enable app access through firewall"
4. Scroll through the list of apps and search for "psx.net..." related entries, uppercase or lowercase. I had one entry "psx.net.msfs.router.exe", all lowercase.
5. If there is any entry click it, then click "Details", then make a note of the path to the app. No need to add this app a 2nd time
6. Repeat the same for all "psx.net..." apps listed, upper- or lowercase.

If you need to add psx.net... apps then proceed as follows:
7. Click the "Change settings" box on the upper part of the page, will prompt for the admin password.
8. Click the "Enable other app" at the bottom of the page
9. In the new window click "search" and browse to the path of the missing app *.exe file, then click "Add".
10. Repeat this until you have both 2 PSX.NET.MSFS.Router* entries and both PSX.NET.MSFS.Client entries. I am not sure whether the Client entries are required.
11. Finally click "Ok" and close the opened windows.

I rebooted my machine afterwards just be sure it's all saved.

Hope this helps.
Good luck
Holger

[Holger Wende]

Now I am a lost

I wanted to find out whether the Client entries are really needed.
So I removed both Client entries in the firewall settings, then MSFS froze again.
Then I added the 2 Client entries again, now MSFS still freezes as soon as the MSFS Link connects.

And most frustrating:
MSFS also freezes when I run MSFS, PSX and PSX.NET all on the same machine which worked before.
I did not install any updates, I only removed and added the client firewall entries again.
And of course I updated the PSX.NET.*.xml files to use 127.0.0.1.
PSX frame rate still at 60/3.

Now I wonder whether the successful runs were just a temporary hickup?

All ideas welcome
I reviewed my region settings before looking into the firewall stuff already, but I have no system to compare with. But the region setting are at least consistent with the German expectations.

BTW, WidePSX still works for me but is has some other limitations 

[Holger Wende]

MSFS FREEZE PROBLEM RESOLVED:

My assumption is the "MSFS freeze" problem is not related to firewall settings but how MSFS is started.

Obviously I overlooked Garys suggestion to start the MSFS situation at any custom location in mid air rather than on the ground.
When I started MSFS I always started in the runway and I never saw the aircraft falling through the ground, probably just because my PSX standard situation starts with in "motion freeze".

Now I removed the 3 additional firewall entries (one entry existed already) and I start MSFS in mid air and all is ready for a long New Years flight

All the best for the next year to you all!

Regards, Holger

Edit 2024-01-12
When I set the MSFS mid-air departure location too close (e.g. within <2 naut. miles) to the PSX aircraft location then MSFS still seems to freeze, at least every now and then at some locations, e.g. EDDM.
When I set the MSFS mid-air departure location far enough away (e.g. 10+ miles) from the PSX aircraft location then MSFS does not seem to freeze

The whole "freeze" issue may also depend of the airport (MSFS scenery) used.
E.g. I saw the freezes more frequently when starting at EDDM.
But starting at an ENGM runway or gate I had the freezes rarely.

[Torben]

at my system exactly the same, starting the MSFS connection with aircraft on ground will freeze MSFS, starting the MSFS connection with aircraft in air will work

[Bluestar]

I start MSFS every time on the ground at the location (Gate) I intend to start my flight from.  There has been no problems for me. 

My flights almost always start where they ended.  At the end of each flight I normally save the PSX flight.  While MSFS is loading I start PSX on both my PCs and load the situation file for the flight from the last flight.  When MSFS has stopped loading I move the aircraft in MSFS to the Gate/location that matches the location of PSX.  After starting WASM I do notice the MSFS aircraft will do some settling.  I then start Vatsim. 

My setup is very similar to this link I posted earlier. 

https://aerowinx.com/board/index.php/topic,7280.msg78311.html#msg78311

I run Aerowinx, Vatsim and Navigraph on my network. 

[GodAtum]

Hi all and happy New Year! I heard GSX might be working with WASM? Do the doors in MSFS open and does pushback work?

[Holger Wende]

...When MSFS has stopped loading I move the aircraft in MSFS to the Gate/location that matches the location of PSX...

Hi Bode,
Do you taxi the MSFS aircraft to the gate, or do you move it using slew mode or something else?

I am asking because I again see the MSFS freeze problem from time to time although I start MSFS in mid air in a custom location "close" to the PSX location. I even tried to raise the PSX aircraft altitude approx 1000ft above the ground to eliminate any "on the ground" issue.
The issue seems to be independent of the network because frequently I see the freeze problem even if PSX and MSFS are running on the same machine.

Seems the problem is comimng and going unpredictably.
And I observe the same behaviour with the PSXMSFS tool.
Only WidePSX is reliably connecting PSX and MSFS.

I was unable to identify the real root cause yet

Edit 2024-01-12
The distance of the PSX aircraft location to the MSFS departure location may be the key.
At least at some airports (e.g. EDDM) I saw frequent MSFS freezing when the MSFS custom departure location was chosen close to the PSX aircraft position.
See also my reply #168

[CHEDHKG]

Hi Bode,
Do you taxi the MSFS aircraft to the gate, or do you move it using slew mode or something else?

I am asking because I again see the MSFS freeze problem from time to time although I start MSFS in mid air in a custom location "close" to the PSX location. I even tried to raise the PSX aircraft altitude approx 1000ft above the ground to eliminate any "on the ground" issue.
The issue seems to be independent of the network because frequently I see the freeze problem even if PSX and MSFS are running on the same machine.

Seems the problem is comimng and going unpredictably.
And I observe the same behaviour with the PSXMSFS tool.
Only WidePSX is reliably connecting PSX and MSFS.

I was unable to identify the real root cause yet

Hi all,

I am quite surprised by this behavior as I do not encounter it at all on my set-up. I would really try to tackle this problem as it should really be frustrating.

On my set-up:

Computer 1: Win10 + MSFS (default Win10 Firewal + Antivirus both deactivated)
Computer 2: Linux + PSX  (on the same network range as Computer 1, ie: 192.168.1.xxx)

Then:
1/ I start MSFS on a given runway (usually LFPG) with the default 747 powered up and ready for take off.
2/ I start PSX (usually where I left off, ie at a gate)
3/ I start the MSFS scenery link tool (either the one I created, or PSX.NET.MSFS.WASM or WidePSX)

Now, sometimes indeed the aircraft may jump, sink or have erratic movements, but reloading the situ in PSX solves this problem. I have still to find the root cause of this behavior. However, I never ever got a freeze.

-Stephan

[Bluestar]

Hi Bode,
Do you taxi the MSFS aircraft to the gate, or do you move it using slew mode or something else?

I am asking because I again see the MSFS freeze problem from time to time although I start MSFS in mid air in a custom location "close" to the PSX location. I even tried to raise the PSX aircraft altitude approx 1000ft above the ground to eliminate any "on the ground" issue.
The issue seems to be independent of the network because frequently I see the freeze problem even if PSX and MSFS are running on the same machine.

Seems the problem is comimng and going unpredictably.
And I observe the same behaviour with the PSXMSFS tool.
Only WidePSX is reliably connecting PSX and MSFS.

I was unable to identify the real root cause yet

Holger,

When I land I taxi to a specific location on the airport.  Once the aircraft is shut down I save the situation and then shut down MSFS.  An example is a flight into ENGM.  After landing ATC sent me to Gate 52 where I parked.  After shutting down the aircraft I saved the situation as engm.situ. After saving the file I shut down Vatsim and MSFS2020. I then built a new flightplan from ENGM to EDDH using Simbrief.  After saving the flightplan I opened PSX and loaded engm.situ.  Once it was loaded I started MSFS2020.  When the screen came up for a location for MSFS2020 I moved the MSFS aircraft to gate 52 at ENGM.  I started WASM and made sure that MSFS and PSX  were talking to each other and the MSFS aircraft was in the correct location which I verify using my Navigraph charts. 

[PanosI]

10.0.3 available to fix vPilot Rounding errors.  Apologies for the certificate error... my code signing certificate expired so you need to press the install button on startup.

Hi Gary,

thanks for your excellent software.
Where can i find the v 10.0.3 ?
Every time i download the software from the links in first page, i always get the v.10.0.1 of the client and router.

[PanosI]

And some pics from the awesome combo 

[B747-400]

Where can i find the v 10.0.3 ?
Every time i download the software from the links in first page, i always get the v.10.0.1 of the client and router.

Hi PanosI

hmmm, my versions both say 10.1.0 (ten one zero) ...

Btw: great pics 

Cheers
Hans

[PanosI]

Hi PanosI

hmmm, my versions both say 10.1.0 (ten one zero) ...

Btw: great pics 

Cheers
Hans

Hi Hans

You are right.
My eyes played tricks on me. I'm in V 10.1.0 also



Thanks! 

[Roddez]

If you are upgrading your visuals from P3D to MSFS, be sure to stop and close the PSX.NET P3D Router.

If you leave this running, PSX.NET WASM will have 2 green boxes suggesting that it is connected, but the MSFS aircraft will remain frozen.

Cheers,

Rod.