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

[asboyd]

Maybe Microsoft based 2024 on an earlier version of 2020 code and they need to reapply the fix they performed on 2020... This seems to be a common theme in software development when moving from one complete version to another based on the same language, why reinvent the whole wheel..

Cheers,
AlexB

[JulietAlphaSierra]

Maybe Microsoft based 2024 on an earlier version of 2020 code and they need to reapply the fix they performed on 2020... This seems to be a common theme in software development when moving from one complete version to another based on the same language, why reinvent the whole wheel..

Cheers,
AlexB

This is an issue I am having with MSFS 2020

[asboyd]

Hi Jas,
Gary mentioned something that had been fixed in 2020 may have been broken in 2024...

Cheers,
AlexB

[JulietAlphaSierra]

Hi Jas,
Gary mentioned something that had been fixed in 2020 may have been broken in 2024...

Cheers,
AlexB

Ah, ok. Thanks for clarifying!

[Gary Oliver]

Following some investigation this afternoon I agree there is an issue with altitude on VATSIM with the WASM module.  Working on a fix.

[Hardy Heinlin]

Just curious. May I repeat my question? :-) Does the OAT influence the baro altitude in the MSFS/Vatsim system?

[Gary Oliver]

Unfortunately not Hardy, it's something to do with the MSFS atmospheric model I think

[Hardy Heinlin]

Yes, the atmospheric model :-) That's what I mean. In relation to geometric altitudes, flight levels don't only change with local pressure but also with local temperatures. Warm air makes the flight level intervals greater.

[andrej]

Gary,
I am online again, and I can confirm that there is no issue with ATC altitude. There seems to be a difference of 500ft on TCAS. But that is not an issue to anyone.

Traffic:


Altitude:




What I noticed is that the flight itself is not as smooth as it used to be, but rather it is jumpy. This occurred after a last few MSFS2020 updates. It is manageable if you look forward.

EDIT: Off topic - BAV question. Is there any chance to connect PSX to Merlin? 

[JulietAlphaSierra]

Just because you aren't having an issue with the WASM module doesn't mean there isn't an issue in the first place, as Gary said, there is a problem and there is a fix coming. What version of PSX.NET.WASM are you using if you don't mind me asking?

[JulietAlphaSierra]

This is also an issue only when Live Weather in MSFS is active

[Gary Oliver]

EDIT: Off topic - BAV question. Is there any chance to connect PSX to Merlin? 

I know the WASM Module has a section of code with the comment of "added to make Merlin work" so I thought running Merlin with PSX.NET worked at some point.  Do we need Ian to update it with the newer model naming convention?

Regarding the live weather issue, MSFS inbuilt live weather does something really weird to the atmosphere model which means no matter what variables for surface pressure we use are nonsense.

Interestingly running activesky live weather works perfectly with my new (unreleased) approach.

The current WASM module that you are all running has a 'bodge' in it to try and align the altitude at Flight Levels but doesn't seem to work very well any more.

Still working on it....

[andrej]

Hello Gary,
no worries about the rest. I tried to connect to Merlin today, and get a following error message:


I have the same model selected in MSFS and PSX (G-CIVB). PSX.NET and PSX BACARS are working fine.

@Joseph,
I use MSFS 2020 and always live weather (hence responding to this threat - Version 10). I was checking it as I have not flown in some time and things (with MSFS updates) can get messed up.

Best,
Andrej

[Bluestar]

.....Interestingly running activesky live weather works perfectly with my new (unreleased) approach.

Gary,

If Activesky for MSFS is a better option I would be glad to upgrade my system.  Those Activesky folks have been great supports of the flightsim community since they fixed the wind problem in FSX for free.

[Gary Oliver]

Morning,

I am probably about a week off getting the fix out the door for MSFS Live Weather following another weekend of testing (aka flying round and round in holds with people on MSFS trying to hit each other whilst adjusting code).

FL's are fixed and I am just trying to get the below transition level stuff figured out and finish off an update to the TCAS code.

My approach with activesky required WASM code changes anyway, so I abandoned that in favour of solving the difficult problem which caters for all users. 

Cheers
G

[Ton van Bochove]

After a re-install ( made a mess of my PSX install after some problems with hardware) of PSX.NET.MSFS2020.WASM I have problems with finding the right IP's for the router setup.

My setup is

Laptop with PSX (A) router installed

Desktop with MSFS (B) client installed.

The client on B tells me that the MSFS link is OK but Userobject is disconnected (red)

The router setup has a default 127.0.0.1 IP for PSX BOOST and PSX SERVER.

To connect A to B I think I only have to alter one or both IP in the router setup. Can somebody give me a clue what to where I have to alter to get the Userobject green again.

Tia Ton

[Jeroen Hoppenbrouwers]

127.0.0.1 is a special address that points at "this PC". So your router, running on PC A, will connect to PC A, which runs PSX as well (right?) so this is ok.

You will need to figure out the IP address of PC A, so that the MSFS client (on B) can find A and connect to the router.

One way of doing this: in a CMD window, type:

C:\ ipconfig

The address you're looking for most likely looks like 192.168.x.y or 10.x.y.z


Hoppie

[Ton van Bochove]

127.0.0.1 is a special address that points at "this PC". So your router, running on PC A, will connect to PC A, which runs PSX as well (right?) so this is ok.

You will need to figure out the IP address of PC A, so that the MSFS client (on B) can find A and connect to the router.

One way of doing this: in a CMD window, type:

C:\ ipconfig

The address you're looking for most likely looks like 192.168.x.y or 10.x.y.z


Hoppie

Hoi Jeroen, Thanks for the quick answer. Now I know that the client on B is configured correctly, I used the correct IP for A (192.168.x,y.and 10.x.y.x.) but both IP's don't do the job. It cannot be a network problem because I have a PSX instance on B which "talkes" to the instance on A so I assume there is no problem. Funny that it worked for two years and now it can't be connected. Any other clues?

Ton

[Jeroen Hoppenbrouwers]

Windows Firewalls ...

Is the PSX-on-B also aimed at the same IP address as you think A has? Just cross-checking.

[Ton van Bochove]

Both PSX and the client have the same IP of A