PSX.NET.MSFS2024.WASM - MSFS2024 Scenery Link for PSX - Version 20.1.0

[Gary Oliver]

Router is the same as before

You just need to put the wasm module in your community folder and run the new 2024 client.

Cheers
G

[Mawea]

Hi Gary,
thank you very much for your great work and your effort. Today I made the change over to 2024 and I really like it!

Cheers Jay

[Bluestar]

Router is the same as before

You just need to put the wasm module in your community folder and run the new 2024 client.

Cheers
G

Gary,

I got everything working on WASM for 2024.  Thanks for the help. 

The only remaining issue for me is the Vatsim aircraft are not displaying at the correct altitude on my ND.  For the most part those aircraft show to be 1,000 feet lower than what is showing on vatsim.radar.

Thanks for all the help you give us. 

[Gary Oliver]

The only remaining issue for me is the Vatsim aircraft are not displaying at the correct altitude on my ND.  For the most part those aircraft show to be 1,000 feet lower than what is showing on vatsim.radar.

Ah I knew there was a project I wanted to do on a rainy day - this is on my todo list and probably needs an update to the TCAS program and the router. I'll try and get on to this in the next couple of weeks.

Cheers
G

[Gary Oliver]

V20.0.2 is now available for those trying the SU1 beta which now supports the time sync again.

[spickle]

Hi Gary,

Great stuff with the quick 2024 update! I'm slowly making the transition from 2020.

A more general question - is there any method to pushback with GSX while using the WASM module? I know you included a GSX profile, but I can't figure out how to push back and have GSX moving both PSX and MSFS at the same time.

No worries if there's no way - but I do like the GSX pushbacks that are customized to airports. One less thing to worry about while starting engines!

[Gary Oliver]

Hi,

The GSX integration really was just for the fancy graphics in external view so you can see the baggage loaders pull up to the plane etc.

I was planning in the soon released EFB to have the ability to draw a custom pushback line.

Cheers
G

[andrej]

Looking forward to the EFT Gary! Just wondering, will this also work for MSFS2020? I am waiting for PMDG to upgrade their B77W and will see how MSFS2024 develops.

I purchased GSX and noticed that my pre-flight takes significantly longer. :-) But main benefit is to have a VDGS or a marshaller. I like PSX.NET's push-back facility. Manual work, but one can really push back as needed (just use outside views).

Thanks!

[Will]

I ran into an issue tonight. Everything was working well this afternoon, but tonight, running the Client leads to connectivity issues.

Here's what I do (this is my typical workflow, which was fine yesterday and earlier today):

(PSX.NET.MSFS.router is already running)

1. Start SPAD.next
2. Start Navigraph Charts
3. Start RealTraffic
4. Start MSFS 2024, version 1.2.11.0, not the beta (MSFS AutoFPS automatically starts with it)
5. Start PSX
6. Start PSX.NET.MSFS.Client V20.0.1
7. Start PSXTraffic

Everything is normal through step 5. At the end of step 5, PSX is running, and all the pother programs are running as well. I can see the 747 at the airport in MSFS where I started the flight using the World Map. It's the white WASM aircraft. Simlink is getting good lat/long data. No visible abnormalities anywhere.

Then when I start the client (Step 6), three things happen: the WASM aircraft disappears, Simlink no longer receives data, and the MSFS aircraft is maybe 500' above the airport in PSX. This means the moving map on Navigraph Charts has no pink pointer for the MSFS location anymore. And with Simlink inoperative, PSXTraffic never connects. And it's unflyable anyway because the MSFS sight picture is 500 feet above the elevation of the aircraft in PSX.

What I've done to troubleshoot:

- Deleted and reinstalled the WASM aircraft into the 2024 Community folder
- Reversed the steps I took on my system since this afternoon: uninstalled ActiveSky, and deleted a scheduler task that ran a batch file that reloaded the default StreamDeck profile on waking from sleep (of note, none of the above programs in steps 1-7 has pushed an update since this afternoon, not that I was notified of anyway)
- Reinstalled PSX.NET.MSFS.Client V20.0.2
- Simplified the loading, by skipping steps 1-3 and 7 above; meaning starting without all those other apps

Those steps haven't fixed the problem.

Any thoughts?

[Gary Oliver]

Psx server set to 60/3 on the frame rate?

[Will]

Yes, the PSX boost server is at 60/3.

[Will]

I reinstalled the WASM aircraft and that helped--running the client no longer positions the camera 500 feet above the aircraft. But the aircraft itself is not visible in External View.

[Will]

Well, the problem is back.

Interestingly I'm seeing that other people (not PSX users) are seeing something similar. This is from an Avsim post:

"Over the past three days I have a continuous issue.  When I leave a flight I cannot get back to the main menu.  MSFS zooms up to an aerial view and then freezes up.  Little spinning circle just stops.  I have removed addons and still am experiencing the issue.  Yesterday I did a complete reinstall of 2024 and that appeared to resolve the issue.  But today it is back."

This is like what I'm seeing. Connecting the client causes MSFS to jump up to 500 feet and then MSFS becomes stuck... it can't exit the flight back to the main menu. I can pan the camera around, but I can't to go the main menu.

PSX and MSFS are connected; if I taxi PSX, the scenery moves in MSFS.

The post on Avsim makes me think it's not having anything to do with the router or the client, since the person who posted that isn't using PSX. But maybe there's something in the WASM package? I don't know. Any thoughts would be appreciated.

*** EDIT: ***  I reinstalled the router and now it's working again. Plenty confusing as to what happened between yesterday afternoon and yesterday evening to cause this mess, but as of now, everything's back to working normally.

*** EDIT AGAIN: *** After the one flight where things were fixed, it's now broken again. After a reboot of the computer and a fresh start of all the programs in the order I described above, for three consecutive times now, everything in MSFS 2024 appears normal including the WASM aircraft, until connecting the client. When the client connects:

- It no longer jumps to 500 feet; I'm at the correct elevation
- The WASM 747 aircraft disappears in external view
- MSFS 2024 loads the scenery incompletely. Buildings and live weather are present, trees are missing.
- MSFS can't go back to the main menu. Clicking Esc while MSFS has the focus does not bring up the menu commands that would allow settings to be changed, or a return the main menu. But switching cameras works, as does panning the cameras.

The situation is confusing because it's changing in ways I don't understand. Something happened that fixed the 500 foot problem, and then for one brief flight, everything was working normally. And now it's consistently as described above.

One constant here is that the problems start when the client is run.

[Will]

I'm stuck here. The behavior is still the same: MSFS 2024 and PSX behave normally until both the Router and Client are running. As soon as both the Router and Client are running, MSFS 2024 partially hangs:

- WASM aircraft becomes invisible on external view, but its lights are still there
- MSFS 2024 visuals loads incompletely, e.g. no trees
- MSFS 2024 can pan views using USB controls and can move with PSX, but can't go to the Main Menu with the ESC key (ESC key has no effect, thus MSFS has to be terminated through Task Manager (or by clicking X in the window)
- Navigraph Simlink gets no position data from MSFS, so Navigraph Charts moving map and PSXTraffic don't connect to MSFS

I've tried many things:

- Verified PSX frame rate limit is 60/3
- Reinstalled and repaired the .NET6 Runtime
- Reinstalled Client 20.0.1
- Reinstalled Router
- Reinstalled newer WASM module to PSX.NET.MSFS.WASM_V20\SimObjects\Airplanes\PSX.NET.MSFS.WASM\panel
- Edited IP addresses in Router.xml and Client.xml from 127.0.0.1 (default) to 192.168.1.253 (as shown in Command Prompt>ipconfig and confirmed in PSX>Instructor>Preferences>Basics)
- Multiple restarts and reboots along the way
- Reinstalled MSFS 2024(!)

I'm happy to entertain ideas of seances, exorcisms, and esoteric healing rituals, because this is all just baffling.

[Will]

Are my issues related to Simlink and the MSFS 2024 pause feature?

Others have reported that pausing MSFS 2024 stops Simlink. I don't know if that's the root of my problem here, but Simlink is stopping when I connect the Client and Router.

[Gary Oliver]

Will,

Can you send me your router and client config files and a screenshot of your router?

Also pop into the Simfest discord and we can chat in real time tomorrow evening (macroflight is also very helpful!)


https://discord.gg/JYnkCXMf

[Will]

Will do! I'll send them tonight. Thanks for your help. I don't think I have your email though.

[Gary Oliver]

Feel free to paste screenshots here

[Will]

Will do. Thanks again.

[Will]

Thanks again, Gary, for any help you can give. Here is a screenshot of the Router:



And here is the Router config file:

Settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SettingsVersion>2</SettingsVersion>
<PsxBoostIP>127.0.0.1</PsxBoostIP>
<PsxServerIP>127.0.0.1</PsxServerIP>
<PsxServerPort>10747</PsxServerPort>
<RouterPubBind>tcp://*:10760</RouterPubBind>
<FeedbackSubBind>tcp://*:10761</FeedbackSubBind>
<FeedbackPubBind/>
<MinWeightModelOffsetM>4.7</MinWeightModelOffsetM>
<PrimaryMsfsMachineName>SaintEx</PrimaryMsfsMachineName>
<DisableRadioInjection>false</DisableRadioInjection>
<DisableTransponderInjection>false</DisableTransponderInjection>
<HeadingOffset>0</HeadingOffset>
<PitchOffset>0</PitchOffset>
</Settings>

And here is the Client config file:

<Settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SettingsVersion>8</SettingsVersion>
<UserObjectRouterIP>127.0.0.1</UserObjectRouterIP>
<SetZoom>false</SetZoom>
<ZoomPercent>52</ZoomPercent>
<SimObjectRouterMode>None</SimObjectRouterMode>
<SimObjectRouterIP>127.0.0.1</SimObjectRouterIP>
<ActivateMSFSAndMinimiseOnStartup>false</ActivateMSFSAndMinimiseOnStartup>
<DisableRadioInjection>false</DisableRadioInjection>
<IgnorePitchOffset>false</IgnorePitchOffset>
<GSXPath/>
<IgnoreMouseMoves>false</IgnoreMouseMoves>
<AutomatedLoadIntoFlight>false</AutomatedLoadIntoFlight>
</Settings>

Let me know if you need anything else, or if there's anything else I could try. I've thought about joining the MSFS beta and using the newest version of the client, but I haven't done that.  Still on V20.0.1 of the Client.