News:

Precision Simulator update 10.172 (20 October 2023) is now available.
Navburo update 13 (23 November 2022) is now available.
NG FMC and More is released.

Main Menu

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

Started by Gary Oliver, Sun, 18 Sep 2022 23:49

Gary Oliver

All,

The release version 2.0 is now ready. You should receive an auto update on startup.

We had this version running for 7 days and 4 hours on 3 MSFS instances during World Flight without a restart or crash on any instances, so has been thoroughly tested.

This version auto updates the WASM module when the client updates.  Please let me know if you get any errors however I have tested on Windows Store and Steam versions of MSFS.

Any issues post here or grab me on the Simfest Discord @ https://discord.gg/DBu8EnWBKx

Release Version 2.0
-Setup everything to make vPilot Altitude correct on VATSIM with a future release of vPilot (thanks Ross!).
-Pulling RAD ALT R CB will allow you to fly under bridges in MSFS without Fatale Damage.
-Updates for SU10.
-Completed SimObject router implementation.
 (Ask for details if you want to sync MSFS traffic between multiple instances (I think I am the only one in the world using this?)

SIMU-3G7

Thanks,

Working like a charm. 8)

Gilles-Gabriel
Up There With The Best Of The Best...

JRBarrett

I tried the new version yesterday. The client and router auto-updated on first run as expected. I ran into a strange problem I have never seen before. I did a 3-hour flight from KLAX to KHSV. During taxi to the departure runway, on two occasions there was a sudden burst of buzzing, cracking static from the speaker, and the PSX frame rate dropped to almost zero, with an accompanying freeze/stutter in both PSX and MSFS. This lasted about 2 or 3 seconds, then recovered.

During the flight, this continued to happen at random times - maybe every 10 minutes or so. I went into the settings menu and changed the PSX frame rate to 60/3 to lessen the load on the boost server, but it made no difference.

I was not connected to Vatsim. I can't rule out that the stutter/freeze was occurring on the MSFS side, and reflecting back to PSX, but I have done many flights with the older version of the client and WASM module, and have never seen this problem before.

I did a subsequent flight just with MSFS alone, using the PMDG 737, and there were no pauses or stutters.

Since the freeze/stutter was accompanied by noise from the PSX sound system, one thing I will try on my next flight is to change the MSFS settings to mute MSFS sounds when its window does not have focus, just in case there was a conflict between the two sim's sound engines.

I run PSX and MSFS on a single computer, with MSFS on the primary (4K) monitor and PSX on the secondary monitor.

macroflight

Quote from: Gary Oliver on Sun, 15 Jan 2023 15:13The release version 2.0 is now ready. You should receive an auto update on startup.

Thanks Gary!

I tried this on two flights yesterday. The only problem was that I didn't read the full "Altitude correct on VATSIM" sentence and got busted by ATC for flying 1000 ft too high. :) Oh well, back to Live Weather=off again until the next vPilot release.

Autoupdate worked perfectly.

(Not using Simrouter and only one MSFS instance, so have not tested those features)

JRBarrett

I have performed three additional flights with no reoccurrence of the stuttering and sound distortion mentioned in my previous post. Not sure what the cause was.

joergalv

Gary,

wondering if it's possible to 'merge' your wonderful WASM-Module with another MSFS-native model,
and what steps I'd need to do to make this work?
I tried by pushing files and directories around, but had no success with this 'not so smart' trial & error approach.

Best regards
Joerg

Gary Oliver

Joerg,

The trick is the panel folder... as long as that's the same it should all work.

Cheers
Gary

Captain_Crow

Hi Gary,
I tried to copy the WASM panel folder to the default 747-8, but seems not enough to get the 747-8 work with WASM stuff. the plane does not follow PSX.
Stupid me ?
Best regards
Steff

beat578

I am not sure, but in the old days of FSX, there was something you had to adapt in the aircraft.cfg file, one of the files was linked to the panel, but I can not remember wich one... I try and look it up.

Captain_Crow


joergalv

Gary, thank you!

I've been basically successful merging the Salty 747 with PSX.NET.MSFS.WASM.
There are issues (expected!) with animations (flaps, gear) I don't care about. Salty instruments in the VC don't work or give weird indications (also expected, and also ignored).
All I was aiming for, was to have my outside view 'framed' by the virtual cockpit. I got this.
I'm just to step out of the door for the weekend, but will place some instructions how to achieve this, during the course of next week.

Regards,
Joerg

P.S.: The aircraft.cfg is not involved, but the layout.json needs to have a reference for the WASM module.

Gary Oliver

Ah yes!  There's a tool called layoutgenerator in the wasm aircraft folder.

If you drag a layout file over it in windows explorer it will generate one for you

Aleks

Did Ross indicate when the vpilot update may arrive?

beat578

Quote from: joergalv on Fri, 27 Jan 2023 08:33I've been basically successful merging the Salty 747 with PSX.NET.MSFS.WASM.

Joerg, thanks for the info. Thasts good to know. Is the Salty 747 finally online again, or do you have the files from before they took it down? I always wanted to use that model, but was never able to find it online again...

Aleks

Quote from: beat578 on Fri, 27 Jan 2023 14:14Joerg, thanks for the info. Thasts good to know. Is the Salty 747 finally online again, or do you have the files from before they took it down? I always wanted to use that model, but was never able to find it online again...

Did you try FlyByWire installer? I can see Salty 747 in there.

beat578

Ah my bad. Yes it's there. I confused it with the canadian mod 747-400, wish was amazing but has been pulled from flightsim.to...

joergalv

Below the steps I took to make this 'merge' work( **cough** I would not consider this to be a functional merge, but a dirty hack, and it was not tested very intensevely). I used the Salty-Mod because i'm not aware of any decent 747-400 model currently available for MSFS. This will most likely work with other models as well.

Limitations:
I was only aiming to have the wonderful smoothness of the PSX.NET.MSFS.WASM combined with the VC view in MSFS. Therefore I did not put any effort to mitigate the following limitations.

- Sounds: They are not touched at all. It's probably a good idea to completely mute MSFS.
- Gear: partly synced with PSX. If you want the gear to remain in the commanded position, the VC gear lever needs to be operated too.
- Flaps: I haven't seen them move at all when operated in PSX. Flap lever in the VC needs to be operated if you care about the flap position of the model.
- Lights: Looks like they are working the same as with the model that comes with the PSX.NET.MSFS.WASM client
- you name it if there are others I did not notice

The steps to take:

1. Make sure you have the PSX.NET.MSFS.WASM Client installed, and working with PSX.
2. If not done already, install the Salty 747 using the FlyBy Wire installer
3. Find both installations in your community folder.
4. Rename the "PSX.NET.MSFS.WASM" folder to something like "PSX.NET.MSFS.WASM.original". (Source from now on)
5. Make a copy of the "salty-747" folder, and rename the copy to "PSX.NET.MSFS.WASM" (Dest from now on)
6. I also renamed the "salty-747" folder to "salty-747.original" to make sure it is not active in MSFS.
7. Copy the file "WASM_Version_2.txt" from the Source to the Dest
8. Find the 'panel' subfolders, and copy both WASM-Files from the Source to the Dest 'panel' folder.
9. From the Source panel.cfg, copy the whole [VCockpit01] section, and add it as [VCockpit17] to the Dest panel.cfg, below the [VCockpit16] section.

[VCockpit17]
size_mm = 10,10
pixel_size = 10,10
texture = $Screen_1
background_color = 0, 0, 255
htmlgauge00 = WasmInstrument/WasmInstrument.html?wasm_module=PSX.NET.MSFS.WASM.UserObject.wasm&wasm_gauge=wasm, 0,0,10,10
htmlgauge01 = WasmInstrument/WasmInstrument.html?wasm_module=PSX.NET.MSFS.WASM.SimObjects.wasm&wasm_gauge=wasm, 0,0,10,10


10. Modifying layout.json in the Dest folder, which needs to include a reference to the WASM Module.

Quote from: Gary Oliver on Fri, 27 Jan 2023 09:05Ah yes!  There's a tool called layoutgenerator in the wasm aircraft folder.

If you drag a layout file over it in windows explorer it will generate one for you

Most likely the way to go, but when I generated a new layout.json with this method in the first place, the AC did not move for some reason. So, when this fails for you too, you can add the following manually, .

{
      "path": "SimObjects\\Airplanes\\Salty_B747_8i\\panel\\PSX.NET.MSFS.WASM.UserObject.wasm",
      "size": 988875,
      "date": 133105803280000000
    },

Done!


In MSFS this 'mod' will not show up as PSX.NET in the aircraft selection dialog. You'll need to select the Salty B748 with Boeing House Livery (unfortunately easy to mix up with the default 748), unless you applied the above to another model/salty livery.

Not sure if future updates of the client will 'break' this mod, so it might be a good idea to copy the edited panel.cfg into a safe place.

Hope this works for those that like to try this 'merge'.

Joerg

Hammerstan

Quote from: Gary Oliver on Sun, 15 Jan 2023 15:13Completed SimObject router implementation.
 (Ask for details if you want to sync MSFS traffic between multiple instances (I think I am the only one in the world using this?)
Yes Gary I'm interested in these steps, thanks for the development.  I'm currently migrating my sim to use 3 instances of MSFS to drive 5x4k monitors.  Currently vatsim traffic is only shown on the "vPilot" PC.

Captain_Crow

Hi Joerg,
I did all, I hope, what you described above. Salty donĀ“t move.
where to put the json manually in ?
best
steff

joergalv

Hi Steff,

the layout.json file is in the directory "PSX.NET.MSFS.WASM" (i.e. the ex-'salty-747' folder, after renaming it). look for any entry referencing to the panel folder ( "SimObjects\\Airplanes\\Salty_B747_8i\\panel\\..."), and add

{
      "path": "SimObjects\\Airplanes\\Salty_B747_8i\\panel\\PSX.NET.MSFS.WASM.UserObject.wasm",
      "size": 988875,
      "date": 133105803280000000
},

below.

You might also want to try Gary's method, using the MSFSLayoutGenerator.exe, you'll find in Gary's Client package. Complete steps 1-9 first, and then copy the exe to the 'new' PSX.NET.MSFS.WASM folder. Then drag the layout.json file from that directory over the exe, which will create a new layout.json, containing all references to the WASM modules in the panel folder.

For both methods:
If the salty does not move in the first attempt, close MSSF completely, restart it and try again.

Hope that helps!
Regards
Joerg