v0.6.2

What's fixed

This release resolves the two issues that prevented Prosim2GSX from
working when ProSim runs on a different PC to MSFS/GSX (a common
networked "sim rig" configuration). Single-PC users are unaffected —
the default behaviour is unchanged.

Beta ProSimSDK connection failed for remote hosts

Prosim2GSX was silently trying to connect to localhost regardless of
what you set for ProSimSdkHostname, so a remote ProSim PC could never
be reached. This was caused by a mismatch with the beta ProSimSDK's new
API shape. The SDK adapter now correctly routes the configured hostname
through the right overload, and works with both the legacy and beta
ProSimSDK versions.

EFB / loadsheet calls were hardcoded to localhost

Even when the SDK connected to a remote host, every EFB, GraphQL and
loadsheet HTTP call still went to http://localhost:5000 on the MSFS
PC. These calls now use the same ProSimSdkHostname as the SDK, so
all ProSim traffic goes to the correct machine.

New documentation

Section 2.3.5 – Running ProSim on a Separate Computer in the README
now includes full firewall setup instructions for the ProSim PC:

• TCP 8082 (ProSim SDK) and TCP 5000 (ProSim EFB) inbound
• Both a Windows Defender Firewall (wf.msc) click-through walkthrough
• And a PowerShell New-NetFirewallRule one-liner for CLI users
• Plus a matching Remove-NetFirewallRule teardown command

Upgrading

1. Download Prosim2GSX-Installer-latest.exe below.
2. Run it — your existing AppConfig.json settings are preserved.
3. If your ProSim runs on the same PC as MSFS: nothing else to do.
4. If your ProSim runs on a different PC: see README section 2.3.5
   for the (small) config + firewall steps.

Thanks

Thanks to Peter who ran this through a real networked setup and surfaced the issues.

---

Full changelog: v0.6.1...v0.6.2