PSX.NET.MSFS.WASM - Smooth PSX to MSFS Scenery Link

[macroflight]

Hello Gary,
I was highly interested you use your solution, to have the Aerowinx 744 cockpit displayed in MSFS.

So, nowhere a cockpit display of the 744 is presented.

PSX.NET.MSFS will not give you Aerowinx/PSX instruments in the MSFS cockpit, it will actually not give you a virtual cockpit at all, just a basic external model.

I use a large display with as much of the PSX cockpit as I can fit while having everything a reasonable size, and a separate display for a fullscreen MSFS:


I've also tried having MSFS on the top half of the screen and the most useful PSX instruments in a window covering the bottom half.

https://aerowinx.com/html/users.html has some examples of what you can do with PSX that I found useful as inspiration.

[Eric Volmer]

Thank you very much for your reply!
I obviously did misunderstand the concept of Gary's solution.
Everything is now clear to me.
Also, thanks for the fotograph of your equipment setup, I really appreciated.
Best regards,
Eric

[Aleks]

MSFS freeze is back (NOT PSX). PSX was freezing, most likely due to PSX CDU Remote. However, I am experiencing MSFS freeze/crash, which never ocured before when not using "PSX" WASM aircraft. Could it be since I am now using PSX Traffic DLL for vPilot?

Tried updating and rolling back video driver, just to check, but same result.

It happens randomly. Sometimes within 5 min, or like now after an hour.

[Gary Oliver]

I found how to fix the weird 'not in the aircraft but flying around it' problem...



MSFS > General Options > Accessibility > Skip Pre Flight Cinematics = Yes

[Aleks]

Tried now full flights with MSFS addons - PMDG, MD82, FBW A32x. No MSFS crash while flying on Vatsim.
If I try with PSX WASM aircraft it now usually crash on every flight.
Might be something at my place, but I start to suspect PSX WASM module as cause.

Any other reports of MSFS crash, using PSX WASM aircraft?

[Gary Oliver]

Had it running for 12 hours yesterday on VATSIM, zero crashes.

The day before 8 hours, no issues here.

[macroflight]

I've had exactly one MSFS crash in the last 2 weeks in maybe 30h of using PSX.NET.MSFS.WASM), and that was when I was stressing everything as much as possible, and it happened when I was switching back and forth between different MSFS graphics settings, so I won't try to blame that on WASM.

- MSFS and PSX on a single PC, MSFS SU10
- MSFS locked to 30 (sometimes 60) fps using vsync using MSFS (not nvidia control panel)
- Not using the CDU IOS app
- Not using PSX.NET
- Using Gatefinder, PSXSound, BACARS

[Aleks]

Is the aircraft link from 1st page still the one to use?

I will try to install everything from start.

[Aleks]

I might have found the cause for MSFS crashes. And, as expected, it is on my PC.
I think it had to do with the settings on the Radeon Software, under Tuning tab.

I am running an AMD 6800XT and have enabled tuning. It was always rock solid, until I started to run MSFS in parallel with PSX. It seems that running MSFS with Java program, would cause temp spike on the GPU, which would lead to driver crash, thus crashing the MSFS as well.

By ramping up the fan setting, and not allowing the GPU junction and Core temp to go above 60C, I managed to carry out three flights with PSX on Vatsim without crashing.

This post is for those that might experience MSFS crash and search this forum

Gary, thank you for your patience and great work.

[CHEDHKG]

Hi guys,

Is it just on my set-up or do you also see the runway upside down in PSX when connecting the attached situ file on MSFS+PSX.NET ?

LFPG situ file

-Stephan

PS: Congrats Gary for this module, works nicely !

[B747-400]

Hi

what's the present status?

After some days with another bridge, I re connected with PSX.NET again.
First, router and client did some updates to client 1.2 and router 1.1.
No info in the version history!

Client and router connected. What means the gray "SimObject Link Disabled"?

Despite the facts that both are "connected", MSFS remains over water - no positioning at the desired airport. This worked so far before the update ...

Do we have to upgrade WASM as well?

Cheers
Hans

[Gary Oliver]

Yep WASM module update required.

Ignore SimObject Link... that's for traffic sync between MSFS instances.

Decimal seperator still a problem, version updates due to two weeks before WF so updating loads of stuff to support my sim.

Updates to follow when I get time, but for now sorry, WF takes priority.

[macroflight]

Is it just on my set-up or do you also see the runway upside down in PSX when connecting the attached situ file on MSFS+PSX.NET ?

When loading that situ, my aircraft appears quite high (30m?) above the runway, then drops down and bounces a bit before settling into a stable position. But it does not flip over.

To some extent that always happen, but LFPG 27R takeoff (I get the same behaviour if I just load any situ and then use the Position tab: "Move Aircraft" to "27R Takeoff") is unusually "bad" in this respect. Maybe there's a bigger difference between the PSX runway threshold elevation and the MSFS one?

I suggest checking that you're using the latest WASM module (from the first post in this thread). Note: the WASM plane does not auto-update like the router and client does. With older versions of the WASM plane it would sometimes flip over for me.

[CHEDHKG]

Thanks macroflight,

But I guess I already have the latest WASM modules installed (just did a fresh install today).

And to be more specific, the plane does not flip, but in PSX it appears the I am under the runway, as if the plane was buried in the ground with the runway a few feet above

[Gary Oliver]

Please note that the update I just had to push requires a new WASM aircraft to be installed or you will just sit bobbing in the sea.  Please download from the link.

I wanted to avoid pushing breaking changes but its 1 week til world flight and we need to get our sim working properly.

[Aleks]

Bobbing in water, with updated PSX WASM aircraft (zipped file size  4,954,865 bytes)

Deleted cfg files in documents, let them rebuild, inserted correct IPs. Double checked that regional setting is set for "." decimal separator. Still bobbing in water, and got "FATAL DAMAGE" in PSX when the plane dropped in the sea

[macroflight]

Bobbing in water, with updated PSX WASM aircraft (zipped file size  4,954,865 bytes)

I was also bobbing in the water with the latest router/client + WASM (same size as you) this afternoon. And the client showed a red "UserObject Link Disconnected" Tried deleting the config files - no change. But after a reboot of the computer everything is fine. No clue what the original problem was.

EDIT: It (Null Island + UserObject Link Disconnected) happened again, and I figure out what the problem was: the boost server in PSX had stopped. After starting it again from the instructor Network tab, everything was fine.

[Gary Oliver]

We are seeing it randomly dumping us on Null Island too... currently trying to work out whats going on.

[Mark]

If you find yourself at null island and restarting the router/client didn't fix it, it seems a full restart of MSFS is required (or at least - Esc -> Restart didn't work for me, but I didn't try coming fully out into the main menu).

[CHEDHKG]

We are seeing it randomly dumping us on Null Island too... currently trying to work out whats going on.

Gary,

Not sure if that can help, but in my scenery generator, I had the same issue which took me long time to find out the cause as it happened randomly:

I was using the non thread safe C library function "strtok" to parse a string in two different threads.
99% of the time there was no issue, until both threads called strtok at the same time, leading to some amusing situations...

-S.