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

[Hardy Heinlin]

What about initial heading? I.e. facing complex scenery data versus facing easy-to-load scenery data at initial repositioning? Maybe MSFS needs a second to prepare some scenery cache or something. The basic PSX takeoff situ starts at a small airport on an island. How complex is the Aomori scenery?

[Will]

The "good" Aomori situ, the "bad" Deli Serdang situ, and Basic 001 all start with the aircraft facing minimal scenery (mostly just trees). And Aomori is a small airport.

My guess is that some piece of data describing the current PSX state is passed along in a way that MSFS can't interpret during the connection phase. Could be anything, maybe MSFS can only handle altitudes in tenths of feet, while PSX sends altitudes in hundredths of feet. Heading is also a good guess; just because my in-flight situ worked correctly isn't proof that the fact it was in-flight was the reason. Maybe MSFS expects headings in a different format than PSX sends, with commonality (and a successful load) whenever the heading ends up in whole degrees. Or something like that. Of course, if that were the cause, then I'd expect the problem to be experienced by more users.

It bears repeating that this is only an issue on the initial connection; once the connection is made, the connection never drops, no matter how long I fly and no matter what I do with PSX (repositioning, loading "good" and "bad" situs, etc.).

Let me also add that I changed lots of things at once: I got a new computer.

The OLD computer had MSFS 2020, Windows 10, a slower GPU, and an older CPU. The new machine has a very fast CPU, a very fast GPU, Windows 11, and MSFS 2024. Maybe it's a timing issue? Or a settings issue in Windows 11? That could explain why I'm seeing it and others aren't.

[Jeroen Hoppenbrouwers]

You almost want to write a PSX simulator to be able to quickly set the emitted variables to known values and reduce the number of butterflies.

Or the equivalent in this case ... a MSFS driver (injector) that is not even listening to PSX but just emits known values from a known set, that can be modified at will.

[Will]

I'm with you Jeroen, I think a PSX simulator would be a great debugging tool here.

[Gary Oliver]

Motion blur turned off in MSFS ?

[Mawea]

Hi Gary,
today I cleared the <PrimaryMsfsMachineName> line in the Router cfg file. Missed the post on page 4. No more jittering in turns and no issues during ms24 start.
I was also able to load and spawn in the LICJ 214 parking spot without issues, had them before hovering >500ft above GND. Thanks again for your work!
Best regards
Jay

[JulietAlphaSierra]

How much data does this link require?

[Will]

I had motion blur set to Ultra. I turned it OFF, and the "bad" situ (Deli Serdang) still locks MSFS, no WASM aircraft, no trees.

As usual, loading a "good" situ fixes the problem.

Funny thing though, I can't tell much of a difference with motion blur turned off.

[Gary Oliver]

Added V20.0.3 of the MSFS Client as I found that the timesync from PSX interferes with the live weather and makes it stutter, disappear or not match on multi PC setups.

If you find the same you can now edit the .xml file and change the following line

<DisableTimeSync>true</DisableTimeSync>

WASM Module changes for VATSIM Altitude are being tested tonight in the sim and by macroflight - we will be looking to release tomorrow if no issues.

[Gary Oliver]

All,

An updated WASM Module is available to mostly fix the VATSIM Altitude problem.

Download it Here

Then copy to Packages\Community\PSX.NET.MSFS.WASM_V20\SimObjects\Airplanes\PSX.NET.MSFS.WASM\panel

Please report back any issues.  We are 99% sure of fixing things up in the flight levels but not so sure under the transition level.  Also TCAS is still an issue but working on that seperately.

Thanks to Macroflight and Andrej for their help.

Cheers
G

[FlyItLikeYouStoleIt]

Added V20.0.3 of the MSFS Client as I found that the timesync from PSX interferes with the live weather and makes it stutter, disappear or not match on multi PC setups.

If you find the same you can now edit the .xml file and change the following line

<DisableTimeSync>true</DisableTimeSync>

WASM Module changes for VATSIM Altitude are being tested tonight in the sim and by macroflight - we will be looking to release tomorrow if no issues.

Where is 20.0.3 to be found? Not currently on page 1 of this thread.

[Gary Oliver]

oh!

It didn't save my update - I'll add it when I get home tonight.

Cheers
G

[Will]

Strange situation today. Taking off from RJSA, my PSX aircraft performed normally but the WASM aircraft lost the altitude connection about 5 minutes after takeoff and sank to the ground at about 10000 feet per minute. It was reproducible; I could reload a situ on the ground, and then reload my in-flight situ and always, the PSX aircraft would be at (e.g.) FL320, but the camera in MSFS would sink rapidly down to sea level. PSX=FL 320, MSFS=FL 000.

Restarting the Router and the Client didn't help, but rebooting the computer and then reloading all the software fixed the issue. Currently all is good. I re-flew exactly the same flight from the runway and everything is normal.

Just mentioning in case this is of interest.

[Jeroen Hoppenbrouwers]

"and then reloading all the software"

re-installing or re-starting?

[CarlBB]

Newbie to MS2024 - Firstly I've installed the PSX.NET stuff and this works; I can see the MSFS outside world of PSX - thank you for this software! But onto refining the views is leaving me scratching my aging head...
I understand that the camera file goes here
C:\Users\xxxx\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community\PSX.NET.MSFS.WASM_V20\SimObjects\Airplanes\PSX.NET.MSFS.WASM\cameras.cfg

But how does one load that in MSFS, is this a custom camera within MSFS or something else? So for my reassurance where can I see the title names of the cameras within MSFS?

I've read in another thread about modifying views and this is clearly something I need to look into as with the default view (whereever that is loaded from) the zoom is too low as on short final it looks like I am too far from the runway and going at like 300 knots!)

I am very comfortable in modifying these text files if neccessary (coming from x-plane I can work wonders with an x-camera csv file!). Just feel I am missing something obvious to others so any pointers would be appreciated.

Thanks!

[Gary Oliver]

Master post updated with 20.0.3 - Also all aircraft links now contain the updated WASM Module which is still available separately for those who want to do an in place upgrade.

[Gary Oliver]

Newbie to MS2024 - Firstly I've installed the PSX.NET stuff and this works; I can see the MSFS outside world of PSX - thank you for this software! But onto refining the views is leaving me scratching my aging head...
I understand that the camera file goes here
C:\Users\xxxx\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community\PSX.NET.MSFS.WASM_V20\SimObjects\Airplanes\PSX.NET.MSFS.WASM\cameras.cfg

But how does one load that in MSFS, is this a custom camera within MSFS or something else? So for my reassurance where can I see the title names of the cameras within MSFS?

I've read in another thread about modifying views and this is clearly something I need to look into as with the default view (whereever that is loaded from) the zoom is too low as on short final it looks like I am too far from the runway and going at like 300 knots!)

I am very comfortable in modifying these text files if neccessary (coming from x-plane I can work wonders with an x-camera csv file!). Just feel I am missing something obvious to others so any pointers would be appreciated.

Thanks!

Carl - Have you played around with this setting in the client config file in documents\PSX.NET ?

  <SetZoom>true</SetZoom>
  <ZoomPercent>52</ZoomPercent>

I found MSFS ignores zoom settings in the cfg files so the PSX.NET Client will force it for you
Cheers
G

[CarlBB]

Carl - Have you played around with this setting in the client config file in documents\PSX.NET ?

  <SetZoom>true</SetZoom>
  <ZoomPercent>52</ZoomPercent>

I found MSFS ignores zoom settings in the cfg files so the PSX.NET Client will force it for you
Cheers
G

Thanks Gary, I will try this after updating to 2.03.

Is the link for the WASM aircraft broken? I get a message saying deleted.

Regards

Carl

[Will]

re-installing or re-starting?

Just restarting.

[CarlBB]

Carl - Have you played around with this setting in the client config file in documents\PSX.NET ?

  <SetZoom>true</SetZoom>
  <ZoomPercent>52</ZoomPercent>

I found MSFS ignores zoom settings in the cfg files so the PSX.NET Client will force it for you
Cheers
G

Thanks but unfortunately changing the zoom in the client config file hasn't worked for me.

I am running a single screen setup, PSX on the lower part of the screen and msfs on the upper part like what Carl (there's 2 Carls!) did  on post 44.

https://aerowinx.com/board/index.php/topic,7076.40.html

I can confirm there was a visual difference to msfs when I change the values

<SetZoom>true</SetZoom>
 
<ZoomPercent>52</ZoomPercent


but the position of the visuals don't align with my setup - e.g. runway is on the bottom hidden behind the PSX window.

Some screenshots in this pdf doc at this link
https://1drv.ms/f/c/85051a53e2deb82f/EgAK9XZ_sutJhbNjmu6se68BiaUVbk-4k65yEB_xA1JHLQ?e=7Wgdzn

If I stop here on this intro, adding I  also tried changing some view options in msfs I am lost with what I should change. I'm ok with changing psx layouts.

Any pointers appreciated.


Carl