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

[GodAtum]

If you fly offline then RealTraffic will inject live traffic into PSX and PSXTraffic will transfer that to MSFS. RealTraffic is a subscription though. I am not aware of anything that will pull traffic from MSFS and inject it into PsX, though that would be useful.

Ah OK, I fly offline using FSHud which injects AI traffic into MSFS and controls them itself, which is really enjoyable.

[Nick7515]

Gary,

Ok..  so I have followed the instructions on how to download these items and did.

 
Downloads
If not previously installed Download .NET6 Runtime
1) Client Setup from Here
2) Router Setup from Here
3) MSFS Aircraft from Here

I then followed all the other instructions as best I understand them.  The PSX.NET.MSFS.WASM_V10 file is in my Community folder. 

I updated the IP addresses in both the Router and Client folder to my gateway IP.  think it was 4 total between Client and Router.  All changed from the default to my gateway IP.

So what now?  What is the order in which to start a session?  PSX first?  Then MSFS2020?  then Client then Router? I am not sure..

Where will I see this?
"When opening MSFS select the PSX.NET.WASM aircraft from the aircraft menu.  You will find many liveries under the liveries section."

Is this once I launch MSFS and then go to "Change Aircraft" in the hangar?

PS...  I am getting "Couldnt Find WASM Module in Community Folder"  Also, I seem to be doing one thing right though...  I have the "MSFS Link Connected" link in Green but the UserObject link is Red and the SimObject Link grey.

Damn getting excited about all this working....  still not there yet though.

Nick. 

[voipmeister]

So what now?  What is the order in which to start a session?  PSX first?  Then MSFS2020?  then Client then Router? I am not sure..

Nick, I start PSX, the client, the router and MSFS all together.

MSFS will take the some time to load, ofcourse. Make sure that the boost server is started in PSX. I select the right location (e.g. departure airport) PSX first.

Is this once I launch MSFS and then go to "Change Aircraft" in the hangar? 

Yes. In MSFS, when it has loaded, you need to select the WASM 747 plane and the desired livery.

You proceed then by selecting any place on the globe and start the flight in MSFS. The location will be updated automatically if all the settings are right.

It's unclear to me whether you run everything from one PC, are you?

[Nick7515]

Nick, I start PSX, the client, the router and MSFS all together.

MSFS will take the some time to load, ofcourse. Make sure that the boost server is started in PSX. I select the right location (e.g. departure airport) PSX first.

Yes. In MSFS, when it has loaded, you need to select the WASM 747 plane and the desired livery.

You proceed then by selecting any place on the globe and start the flight in MSFS. The location will be updated automatically if all the settings are right.

It's unclear to me whether you run everything from one PC, are you?

I am running all this from one computer.  a 12th Geni9-12900K 3200mhz with 32 GB RAM.  ALso, two video cards.. 3080TI for my 43"4K gaming Monitor and a GT730 running 4 26" touchscreens for PSX.  Its quite the setup.

[Nick7515]

<-----------You guys know how to add a picture under the name?

Never mind...  figured it out! 

 

[voipmeister]

Well I was communicating with someone in this forum and I lost that stream?

I think you started here: https://aerowinx.com/board/index.php/topic,6128.0.html

But we can continue here.

I updated the IP addresses in both the Router and Client folder to my gateway IP.  think it was 4 total between Client and Router.  All changed from the default to my gateway IP.

I'm not sure what you mean by this - I think you shouldn't change anything if you're running everything on the same system. Can't verify my system right now as it's too late for me now here, I can check tomorrow if others haven't chimed in yet. We will get your system sorted though

[Gary Oliver]

Don't set anything to your gateway IP, if on one PC leave as 127.0.0.1, if not put the IP of the PC's.

The error about the community folder is worrying - are you sure you put the WASM aircraft in there it its own folder.

[voipmeister]

<-----------You guys know how to add a picture under the name?

Yes, go here: https://aerowinx.com/board/index.php?action=profile and select Forum Profile > Forum Profile. You can upload an avatar there. Mind the size though.

[Nick7515]

Gary..

yes I am on one PC only.  there are 4 IP's total, 2 in the Client and 2 in the Router.  Are you saying all 4 should not be changed, and return them back to 127.0.0.1?

As far as the WASM folder question:
Mine looks like this:  C:\Users\Nicholas\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\PSX.NET.WASM
In the Client software, I am able to see 2 of the 3 green boxes now.  "UserObject Link Connected and the MSFS Link Connected.  The SimObject Link is still saying Disabled.

So precisely what should be done here.  When I am in MSFS folders and Community folder is there on my screen.  The first time I did that the folder was blank.  Now, what exactly am I to drop into the community folder?  When you say, WASM aircraft in its folder should be there.... I don't see a WASM aircraft folder in the PSX.NET.MSFS.WASM_V10.  I see a series of folders and files. I don't see an WASM aircraft folder?  Is it a sub folder?  The only thing I see is when I open SimObjects folder there is an airplanes folder.  Is this the folder I am to move into the MSFS community?

If it is....I tried it and it didn't work... or at least when I launch the Router connect, I still get "couldn't find WASM module in MSFS Community" 

MSFS 2020 was downloaded from Steam.
Nick

[PSX747atlas]

PSX.NET.MSFS.WASM_V10 is the folder you should have in the community folder, within it should have 3 folders and 5 other files inc readme, you dont do anything to them. msfs should see the wasm aircraft and the liveries.  and yes i belive all your psx installs on the same pc should be on local host 127.0.0.1 and ensure port 10747 is selected.  also ensure no virus software or port blocker is blocking your ports.

also make sure only one PSX instance is set as server, other 3 should be client i believe, Gary or others will confirm.

[Jeroen Hoppenbrouwers]

127.0.0.1 == "localhost" == "connect to the same PC as you yourself run on".  It looks like a network connection to everybody, but in fact it does not leave the PC. Yet both client and server don't notice it's local.

Only if your program needs to connect to another PC in your network, you use something like "192.168.x.y" or "10.x.y.z" to direct the program to that other PC.

There are vanishing few cases that you want to connect anything directly to your router/gateway.


Hoppie

[Nick7515]

So going to try again today to see if I can get this thing running.

This is what my file stream looks like.

 C:\Users\Nicholas\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\PSX.NET.MSFS.WASM_V10

Does that look correct?  Is the file in the right place?

I am still getting the message:
"Couldn't find the WASM Module installed in MSFS Community Folder"

Another thing, when the Client software is running, along with the Router software, PSX, and MSFS, I have two of the three green link connections lit up.  The one that isn't green is the SimObject Link.  It says disabled. When this is all working properly, should all three be green?

Also, when this is all working correctly, what can I expect as for as sim operation?  Will the aircraft in the MSFS mimic PSX?  Meaning, if I push LNAV and VNAV, or Turn the Flight Directors off in PSX, will it do the same thing on the aircraft in MSFS?

Nick

[macroflight]

C:\Users\Nicholas\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\PSX.NET.MSFS.WASM_V10

It looks like the correct directory, at least if you're using the Steam version of MSFS. I assume you have at least some other MSFS packages (scenery, etc.) installed in the same folder. If those other packages work in MSFS, it's definitely the correct folder. If you're in doubt, a google search for "where is my MSFS Community folder" might help.

But if you get the message "Couldn't find the WASM Module installed in MSFS Community Folder" when you start PSX.NET.MSFS.WASM.Client, then something is wrong. Maybe you have the directory "PSX.NET.MSFS.WASM_V10" in the Community folder, but the contents of "PSX.NET.MSFS.WASM_V10" are incorrect? Or are you not using the Steam version of MSFS?

I took some screenshots of my setup that you can find here: https://imgur.com/a/psx-net-msfs-wasm-things-SDrZdYA - read the captions (one of them explains why the grey SimObject button is not a problem).

What you can expect:

- No virtual cockpit

- PSX will essentially push a camera through the MSFS world. You can look in any direction you want, but as there is no virtual cockpit (no window frames, glareshield, etc.) it might feel less immersive than you hoped for.

- A simple external model. Yes, you can look at your B744 from the outside, but you can't see it when you look from the inside out.

- As you're basically just flying a camera around in MSFS, there is nothing to do in terms of syncing LNAV buttons and the like. Basically the only things synced between the PSX and MSFS planes are a few things that affect the external model: gear position, flap position and some exterior lights.

I hope this doesn't scare you off. If you want to combine PSX and MSFS, this is absolutely the best option. I've started using using PSX.NET.MSFS.WASM on a single-PC PSX+MSFS setup since a few days after the first release, and never looked back.

People seems to have slightly different ways to start things, this is the order I use:

1: start PSX and Router. Move PSX to your starting position (e.g using PSX.NET.GateFinder - amazing little utility)
2: start/connect your other PSX clients (e.g BACARS, iPad app, PSXSounds, PSXViobrate, ...)
3: start MSFS
4: when the MSFS start screen shows, start Client
5: make sure you choose the PSX B744 plane, no other MSFS plane will work for this
6: click Fly

[PSX747atlas]

check if you have a community folder in the local not roaming appdata. 

C:\Users\smurf\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

that is my msfs install but not steam version, may be this is reason you get the cant find wasm.

[Bluestar]

This is where my community folder is located.  I have MSFS2020 on my D drive.  My MSFS2020 was purchased from the Microsoft Store.  This address is different from what I've seen on line.  One other thing I did was create a desktop folder to load all the sceneries, etc. into.   

D:\WpSystem\S-1-5-21-2632763079-1937765180-3250831825-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

[Nick7515]

OMG!!  I got it to work.

I was able to locate the correct location of my community folder in Steam, wasn't anywhere even close to where we all thought it should be.  If you go into Developer mode in MSFS, and go through the menu, you can find it there.  It takes you right to it in file manager.  Anyway, I moved the WASM file into it and It worked.  Big accomplishment and I thank you all for your help.  Still some bugs to work on and trying to figure out some things as far as weather generation and placing the airplane at the cargo gates which aren't in the PSX software.  I noticed I don't have a lot of rudder authority when on the ground (using rudders)... as in, I cant drive the plane off the runway... I imagine there is a way to do that on the keyboard.  I am looking into buying a tiller anyway. 

Overall, a big day for me.
I wont be working on the sim for the next couple weeks... work calls unfortunately, but cant wait to get back and start to use this thing.  I am sure I will have more questions then.

Again, thank all of you who helped.
Nick. 

[macroflight]

Weather: if you want accurate real-world weather for your location, turn on PSX's "Set zones by flight track and download METARs". PSX will then use downloaded METAR data to give you realistic weather near airports. If you have the "Aerowinx - NG FMC and More" product, you can also add a wind+OAT corridor (paste your Simbrief flightplan winds into the Corridor tab(*)) along your planned route to give you realistic winds and temperature enroute. You can currently not get the PSX weather radar to show MSFS clouds.

Tiller: the K and L keys on your keyboard controls tiller below 50 kts, see the PSX manual page 31). There is also an option in the PSX USB setting to have a combined aileron and tiller axis (manual page 99, tiller below 40 kts, aileron above 40 kts) if you don't have a dedicated tiller axis. I used a cheap joystick as tiller earlier, it worked well and felt more realistic than having it on the aileron axis.

Placing the airplane at a specific gate: PSX.NET.Gatefinder is another very useful piece of software by Gary. It works by extracting the coordinates for all gate in all your MSFS airports into a CSV file. You can then use a small GUI to position your aircraft at any of these gates. Another option is to use PSX to move to the airport and then use the controls on the Situation > Aerodynamics tab to "drive" the aircraft on the ground to the correct position.

(*) This and more can be automated by using the Simfest planning portal + BACARS to create your Simbrief flightplan and then load it into PSX using the #3 CDU.

[Icarus747]

A little help her PLEASE:

I am running PSX on one computer.  MSFS 2020 ONLY on another.  Both on the same network.  (Other computers as well for multiple PSX displays.  I used VisualPSX for years but tried to get fancy with WIDEPSX and it never worked.  So it's on to this program.

Questions:  Given my setup above, which is the client and which is the router?  Trying to figure out which files go on which computer.  The aircraft part I can do.

[Gary Oliver]

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)

[Icarus747]

Thank you for you thorough response Gary.  I'm trying it all right now and will post back.