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

[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.