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

[Icarus747]

Sorry we seem to have lost the useful diagram which showed this.


The Router can run on any PC on the network, I run this on the same PC as PSX.  The Client then runs on any PC which runs MSFS.

If all on one PC, run both the router and client on the same PC making sure you put 127.0.0.1 as the IP address of the router in the client config file in the my documents\psx.net folder.

The first thread of this post has an install section if that helps but in summary if you run as I described above.

Run the Client installer on the PC you want to run MSFS
Run the Router installer on the PC you run PSX
Run both programs and close them
In the My Documents\PSX.NET folder you will have a client or router config file.
Update the Client XML file to point to the Router IP Address
The Router config just needs to point to 127.0.0.1 and 10747 if using standard PSX ports and running on the same PC as the PSX server.
Run MSFS and select any of the PSX.NET aircraft liveries.
You are looking for numbers counting up on the router and a green 'userobject' and 'msfs' button on the client.
The SimObjects button will stay red unless you want to be syncing traffic between two MSFS instances (for example on a 3 PC, 3 projector setup)

Does it matter that I am using STEAM to run MSFS 2020?

[Gary Oliver]

Does it matter that I am using STEAM to run MSFS 2020?

I run the steam version on my development pc and store version on my sim, so no

[Icarus747]

Sorry we seem to have lost the useful diagram which showed this.


The Router can run on any PC on the network, I run this on the same PC as PSX.  The Client then runs on any PC which runs MSFS.

If all on one PC, run both the router and client on the same PC making sure you put 127.0.0.1 as the IP address of the router in the client config file in the my documents\psx.net folder.

The first thread of this post has an install section if that helps but in summary if you run as I described above.

Run the Client installer on the PC you want to run MSFS
Run the Router installer on the PC you run PSX
Run both programs and close them
In the My Documents\PSX.NET folder you will have a client or router config file.
Update the Client XML file to point to the Router IP Address
The Router config just needs to point to 127.0.0.1 and 10747 if using standard PSX ports and running on the same PC as the PSX server.
Run MSFS and select any of the PSX.NET aircraft liveries.
You are looking for numbers counting up on the router and a green 'userobject' and 'msfs' button on the client.
The SimObjects button will stay red unless you want to be syncing traffic between two MSFS instances (for example on a 3 PC, 3 projector setup)

Okay, so thus far I have a green light on only MSFS LINK CONNECTED, RED on UserObject, and SimObject Link Disabled is  GRAY.  This is on the machine running ONLY MSFS.  Also, no PSX aircraft show up in the MSFS Aircraft menu.

On the PSX Machine data seems to be moving from boost and main.  (Numbers changing)  That was on IP 127.0.0.1, and I ALSO tried the PSX machine's IP, 192.168.1.115.  Both seem to work.  Neither seem to help with getting the MSFS machine to connect to psx.  Alo 60/3 was set on in PSX.

NOW WHAT?

[Icarus747]

IT WORKS!  Long story on how. I'll explain eventually, but just didn't want anyone spending any more time on it.  thanks for your help!

[osss]

Hello!

It works except there is no aircraft in external view. What could be the problem?
MSFS2020, PSX.NET and livery selected. Everything connected and moves smoothly and in sync.
Can see landing and taxi lights in the dark, but no 3D model of the 747 in the external view.


Update:

In hangar view during livery change the aircraft seen for a moment then disappears.
Here is screen capture


https://i.imgur.com/d5L7vrn.mp4

[JulietAlphaSierra]

When using VATSIM, the radar shows the aircraft 1000 feet bellow from where it actually is (Flying at FL400, shown at FL390). This comes from using live weather in MSFS, which I don't want to turn off because it provides a nice visual. Can this WASM module provide weather visual in MSFS to show the weather that PSX is showing?

[Will]

It works except there is no aircraft in external view. What could be the problem?
MSFS2020, PSX.NET and livery selected. Everything connected and moves smoothly and in sync.
Can see landing and taxi lights in the dark, but no 3D model of the 747 in the external view.

I was having something like this happen with MSFS 2024, and the solution for me was to connect the Router and the Client, and then load the situ Basic 001, and then load whatever situ you want after that.

Not sure this is relevant to you with MSFS 2020, but you might want to give it a try.

[Gary Oliver]

When using VATSIM, the radar shows the aircraft 1000 feet bellow from where it actually is (Flying at FL400, shown at FL390). This comes from using live weather in MSFS, which I don't want to turn off because it provides a nice visual. Can this WASM module provide weather visual in MSFS to show the weather that PSX is showing?

The WASM link adjusts our inputted altitude in MSFS to match that of MSFS, P3D and X-Plane users on VATSIM.  Is ATC saying that your altitude is showing incorrectly?  This should already be catered for and fixed.

The TCAS returns currently are incorrect on your ND from the PSX.NET.VPilot Module.  It's on my list of things to fix.  I'll do another check of our altitude injection though.

[JulietAlphaSierra]

The WASM link adjusts our inputted altitude in MSFS to match that of MSFS, P3D and X-Plane users on VATSIM.  Is ATC saying that your altitude is showing incorrectly?  This should already be catered for and fixed.

The TCAS returns currently are incorrect on your ND from the PSX.NET.VPilot Module.  It's on my list of things to fix.  I'll do another check of our altitude injection though.

I was flying into YSSY the other night and the controller told me to maintain FL350, which he thought was my cruising altitude, for which I had to clarify that I was at FL360. And on my latest flight into Hong Kong, I passed over an aircraft that on MSFS was only a few hundred feet below me (maybe 200-300') when PSX saw no issue, and on my end I was at 380, and the other aircraft was at 370. From the point of view from MSFS and there for VATSIM, we were both at 370. This seems to be a conflict between PSX and MSFS as the pressure of each respective sim is different, and for the time being I am using WidePSX to get rid of this issue as that injector has a workaround that works amazingly well. Really hope this is looked into more and fixed, I can provide some more information if necessary via tests so don't hesitate to reach out.
-Joey

[Gary Oliver]

I'll have another look at the issue then - this was fixed in a version a while back, I wonder what has changed.

Come to think of it we did have a controller into PSP the other day mention our altitude reporting seemed off.

@JP - If you are still around can you share what magic you do in your WidePSX fix?  Maybe we could just do the same.

Cheers
G

[Gary Oliver]

Joey,

What client version and MSFS version are you using?

2024, 2024 SU1 beta version or 2020?

[Hardy Heinlin]

Does MSFS and Vatsim etc. simulate temperature dependent altitude indications? This effect is simulated in PSX and can be deactivated on Instructor > Situation > Aerodynamics with the "OAT error" checkbox.

[andrej]

Gary,
you fixed this issue in the past. I know that PSX is now calibrated for MSFS2020.
I had not issues from VATSIM controllers for over 1 year. :-)

Cheers,

[Gary Oliver]

Andrej,

I too thought it was fixed... Something must have changed in MSFS2024.

Cheers
G

[JulietAlphaSierra]

I believe I am using vpilot version 3.0.1, and MSFS 2020, I am RVSM unable on the network currently because the radar shows me 700-800 feet below my actual altitude

[JulietAlphaSierra]

I'll have another look at the issue then - this was fixed in a version a while back, I wonder what has changed.

Come to think of it we did have a controller into PSP the other day mention our altitude reporting seemed off.

@JP - If you are still around can you share what magic you do in your WidePSX fix?  Maybe we could just do the same.

Cheers
G

There is a fix for WidePSX included as a default setting, and this is the description for such setting:

"Use VATSIM Altitude Fix (MSFS Only) NEW: MSFS and PSX atmosphere models are different.
This is causing discrepancies between the MSFS and PSX pressure altitudes. This checkbox
is only relevant when using MSFS as Scenery Generator. When this checkbox is selected,
WidePSX will apply a workaround to get the right pressure altitude sent to VATSIM and then
the ATC will see you at the correct pressure altitude. This workaround is active above the
transition level which is selected in the FMC's DESC/FORECAST page. You will notice a visual
artifact in MSFS when passing the transition level. This is due to the algorithm applying the
altitude offset for the first time. It will only happen once during climb, and one more time
during descent when passing again through the transition level, when the algorithm will
disable the altitude offset."

Unfortunatly, it seems like Jean hasn't been active for a while, so he might not be providing support/insight anymore.
Hope this helps!

-With regards, Joey

[Gary Oliver]

Sounds very similar to what we did in the WASM previously to fix the issue.

Can you confirm the date/time stamp on the WASM module in your community\psx.net aircraft\simobjects\psx.net plane\panel folder and the version showed on both the router and the client when you run them?

I'll have some time later in the week to have a look.

[JulietAlphaSierra]

The timestamp on the Panel folder says 1/27/25 at 9:49 PM PST, Router is 10.3.0, and Client is 10.1.1

[Gary Oliver]

what about the two wasm files within it?

[JulietAlphaSierra]

what about the two wasm files within it?

Both had their dates as 2/19/25 around 4-5 PST if memory serves, I did replace those files because I was tweaking the files to get a new livery, so I just downloaded some new stuff just to be on the safe side