Skip to content

Releases

ION COMMAND v0.9.2

Choose a tag to compare

@svabi79 svabi79 released this 26 Jul 04:04
v0.9.2

If you downloaded the 0.9.1 installer, replace it with this one. The installer attached to v0.9.1 contained the 0.9.0 client — a build-script defect on my side, not a problem with the 0.9.1 source. Its collector and launchers were correct, so the reserved-port startup fix did work; the client-side changes were simply not in it. This release ships what 0.9.1 was meant to ship.

What 0.9.1 was meant to give you

If the globe started empty, this is the fix. Windows reserves whole TCP port ranges for Hyper-V/WSL NAT. Where the collector's port 7810 fell inside one, binding failed even though nothing was listening — the collector died instantly and the launcher started the client anyway, with the only warning in an invisible console window.

The launchers now probe the port first, fall back to 17810 and then 27810, notice immediately when the collector exits, stop a candidate that never becomes healthy instead of leaving it running, point the client at whichever port worked, and show a message you can actually see when nothing works.

Check whether your machine is affected:

netsh interface ipv4 show excludedportrange protocol=tcp

Thanks to @die-Anna for finding this and tracking it to the reserved ranges in #1.

Vertical orbit no longer feels inverted. A right-mouse drag moved the camera with the mouse horizontally but dragged the surface against it vertically. Both axes now agree. INVERT ORBIT Y in the settings panel (O → SETTINGS >) restores the old direction exactly, and the choice persists.

Also: replay (R / L) follows the collector onto a fallback port, and the new -listen flag moves the collector without editing your config.

New in 0.9.2

Hidden HUD rows no longer answer clicks. With the HUD switched off (Tab), the settings panel's click targets stayed active. A click near the middle of the screen could silently hide most aircraft, flip the orbit axis, or drop you into text entry — with nothing on screen to explain it, and it persisted across restarts. Clicks now fall through to the world whenever the HUD is not drawn. (#2)

Full detail in the changelog.

Install

Download ION-COMMAND-0.9.2-Setup.exe below and run it. It is not code-signed, so SmartScreen will warn — choose More info → Run anyway if you are comfortable with that. Installing over an earlier version is fine; it stops a running instance first and keeps your collector\configs\live.json.

Requires 64-bit Windows 10 or later, a GPU that can run UE5, and about 1.5 GB of disk. The collector listens on loopback only and has no authentication — it is built for local single-operator use.

Several feeds are run by volunteers and are non-commercial only; the lightning layer streams from Blitzortung.org and is on by default. Please read DATA-SOURCES.md before redistributing your own build.

ION COMMAND v0.9.1

Choose a tag to compare

@svabi79 svabi79 released this 25 Jul 21:30

Warning

The installer that was attached to this release was defective and has been removed.
It contained the 0.9.0 client, so none of the client-side changes described
below were actually in it — a build-script defect on my side, not a problem with
the source at this tag. The collector and launchers in it were correct, so the
reserved-port startup fix did work.

Please use v0.9.2,
which ships what this release was meant to ship. The cause and the guards added
against it are documented in the changelog.


A maintenance release, driven by what actually broke for people who installed 0.9.0.

If 0.9.0 started with an empty globe, this is the fix

Windows reserves whole TCP port ranges for Hyper-V/WSL NAT. On machines where the collector's port 7810 fell inside such a range, binding it failed even though nothing was listening — the collector died instantly, the launcher waited its full 20 s, wrote a warning into an invisible console window, and started the client anyway. All you saw was a globe that never filled.

The launchers now probe the port before using it, fall back to 17810 and then 27810, notice immediately when the collector exits instead of waiting out the timeout, point the client at whichever port actually worked, and show a message you can see when nothing works at all.

You can check whether your machine is affected:

netsh interface ipv4 show excludedportrange protocol=tcp

Thanks to @die-Anna for finding this, tracking it to the reserved-port ranges, and fixing it in #1.

Vertical orbit no longer feels inverted

A right-mouse drag moved the camera with the mouse horizontally but dragged the surface against it vertically. Both axes now follow the same convention. If you preferred the old direction, INVERT ORBIT Y in the settings panel (O → SETTINGS >) restores it exactly, and the choice persists.

Everything else

  • Replay (R / L) keeps working when the collector runs on a fallback port.
  • New collector flag -listen overrides the configured listen address, so a launcher can move the port without editing your config.
  • The collector reported its version as 0.1.0-bootstrap; it now reports the real one.

Full detail in the changelog.

Install

Download ION-COMMAND-0.9.1-Setup.exe below and run it. The installer is not code-signed, so SmartScreen will warn — choose More info → Run anyway if you are comfortable with that. Installing over 0.9.0 is fine; it stops a running instance first and keeps your collector\configs\live.json.

Requires 64-bit Windows 10 or later, a GPU that can run UE5, and about 1.5 GB of disk. The collector listens on loopback only and has no authentication — it is built for local single-operator use.

Several of the data feeds are run by volunteers and are non-commercial only; the lightning layer streams from Blitzortung.org and is on by default. Please read DATA-SOURCES.md before redistributing your own build.

ION COMMAND v0.9.0

ION COMMAND v0.9.0 Pre-release
Pre-release

Choose a tag to compare

@svabi79 svabi79 released this 21 Jul 04:54
v0.9.0

First packaged release. A live situation display for HF propagation, aircraft, lightning, satellites, earthquakes, ionosphere soundings and space weather on one globe.

Install

Download ION-COMMAND-0.9.0-Setup.exe (267 MB) and run it. Windows SmartScreen will warn — the installer is not code-signed. It installs the Unreal client, the Go collector, a default configuration and a Start Menu entry that starts both.

Requires 64-bit Windows 10+, a GPU that can run UE5, ~1.5 GB disk, internet. The collector binds 127.0.0.1:7810 only and has no authentication — keep it local.

First steps

Press O → SETTINGS > and set your callsign and grid locator. Press M to see only your own station's paths. If the airspace is too busy, set MIN FLIGHT LEVEL to FL100.

What's in it

  • Propagation paths from PSKReporter (RBN and WSJT-X available, opt-in)
  • Worldwide aircraft from OpenSky plus regional detail from adsb.lol, oriented on true track with dead reckoning between updates, type-specific glyphs and emergency-squawk highlighting
  • Lightning strikes from Blitzortung
  • Satellites (CelesTrak TLEs, SGP4), earthquakes (USGS), ionosonde soundings (GIRO/KC2G), space weather (NOAA SWPC + GOES)
  • Live EUMETSAT cloud imagery, refreshed hourly, and the real star sky rotated to sidereal time
  • Cockpit HUD: band activity, path rate, top DXCC regions, auroral oval, HF conditions estimate, hop/MUF path analysis

Please read before you use the data

The MIT licence covers this project's code, not the data it fetches. Several sources are non-commercial only — Blitzortung, OpenSky and GIRO/KC2G among them.

The lightning layer streams from Blitzortung.org, a network of volunteers who each buy and maintain their own detector. Raw access is intended for contributing station operators, commercial use is prohibited, and it is not a warning system — never use it for safety decisions. If you keep the layer on, please consider running a station; switch the source off in any commercial deployment.

Full attribution and terms: docs/DATA-SOURCES.md.

Notes

  • Recording is off by default — the live feeds produce several GB per hour.
  • OpenSky's login/password fields are currently ineffective: OpenSky retired HTTP basic auth in favour of OAuth2. Anonymous access still works.

Pre-1.0: single-operator local use, Windows only, no support promise.