MopicHub 1.3.0
1.3.0 supports the new Mopic OpenXR runtime that ships without the MOPIC SDK, lets the hub use the newest compatible MOPIC runtime instead of a fixed version, and repairs installations that are missing files on its own.
OpenXR runtime
- Runtime files linked for the new OpenXR runtime. Starting with Mopic OpenXR 0.1.7, the OpenXR package no longer includes the MOPIC SDK. The hub links the files of the newest MOPIC runtime that the installed OpenXR version supports into the OpenXR service folder. The links are hard links, so they take no extra disk space. The hub checks them right after OpenXR is installed, at startup, when a newer runtime arrives in the hourly update, and just before a game starts in OpenXR mode.
- Safe switching. The hub never switches runtime files while the OpenXR service is running, never overwrites files that came with the OpenXR installer, and restores the previous links if anything fails. Files that are still in use are moved aside and removed later. The runtime version linked to OpenXR is kept when old versions are cleaned up.
- Relink from Home. If the files cannot be linked, Home shows a card with a Relink button. A game launch in OpenXR mode stops with an explanation instead of starting without the runtime.
- Clearer installer results. If an OpenXR app is running during an OpenXR update, the update is postponed and retried later with a notice, instead of being reported as failed. An install that finished with a verification problem, or that failed, appears as a card on Home. After an install the hub also checks that the installed version is the one it asked for.
- Mopic OpenXR 0.1.6 and earlier keep working as before, with the runtime copied into their own folder. With 0.1.7 and later, that old copy folder is removed once.
Hub runtime
- Newest compatible runtime, no fixed version. The hub now loads the newest installed MOPIC runtime that is compatible with this hub version. If none is installed, it downloads the newest compatible one at startup. A newer runtime installed while the hub is running is used from the next start.
- Hub compatibility from the server is honored. The hub compatibility set on the server for each component was not read before, so a component that needs a newer hub could be installed. Install, automatic updates, and update badges now follow it.
- Apps and modules started by the hub are given the runtime folder they need directly, instead of inheriting the hub's own library search settings.
Installation integrity
- Missing files are detected. A component counts as installed only when its files are actually present. Right after a download is extracted, every file is checked against the package, and a mismatch is reported as an install failure.
- Automatic repair at startup. When the hub is online at startup, apps and components with missing files are downloaded again in the same version. If the download fails, the existing folder is kept as it was.
Fixes
- The shared hub state that newer MOPIC runtimes read stays current. If the file could not be replaced because another program was reading it, the hub now writes it again shortly afterwards instead of waiting for the next license or monitor change.