Release notes and downloads for MopicHub.

total 16EA

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.

MopicHub 1.2.1

1.2.1 adds a Reinstall button for every app and add-on, separates license refresh from removing a manual key, launches OpenXR-capable games in OpenXR mode by default, and moves administrator tasks so the hub asks for permission at most once while it is running.

Reinstall

  • Reinstall button. Every add-on card, including System components, now has Reinstall, and apps have it in Runtime settings. The installed version is moved aside, the same version is downloaded again, and the original is put back if the download fails, so a failed reinstall never leaves a half-deleted folder.
  • Programs that use the folder are closed first. Reinstalling the runtime or a library closes running apps, and the confirmation says so. The eye-tracking module is started again afterwards whether the reinstall succeeded or not.
  • The runtime the hub itself uses is reinstalled at the next start. The hub asks to restart and replaces it before loading it.
  • The OpenXR runtime is reinstalled by running the same version's installer over the current installation, because its service keeps files open.

License

  • Refresh and Reset are separate. Refresh under Settings > License looks the license up again, with the manual key if one is set and otherwise with the monitor serial, and keeps the manual key. A monitor card that uses a manual key shows Reset, which removes that key.
  • Apps get the license the hub is using. Apps now receive the same license as the eye-tracking module, with a manual key taking priority. Previously an app could receive the monitor's serial license while the module ran with the manual key.
  • Support reports show manual key changes (entered, removed, reset) right away instead of after the next license lookup.

Installation and permissions

  • Installed for all users again. The hub installs to Program Files. The installer adds the firewall rule for eye-tracking data and removes old autostart entries, so installing or updating the hub asks for administrator permission.
  • One permission prompt while running. The only administrator task left while the hub runs is setting MOPIC as the system OpenXR runtime. A signed helper does it with a single prompt, and if the prompt is declined the hub does not ask again in the same session.
  • Fixed startup install order. Components are installed in the order runtime, eye tracker, other components, then the OpenXR runtime. Previously the OpenXR runtime could be installed before the runtime it needs.
  • The OpenXR runtime installer is started with administrator rights only when the installer itself requires it. Version 0.1.6 and later raise permission only for the steps that need it.
  • Hub runtime pin updated to 2.1.1.

Games

  • OpenXR by default. Games that support OpenXR now launch in OpenXR mode unless AI 3D is chosen. A mode you already picked for a game is kept.

Fixes

  • On a first launch that downloads the hub runtime, the Connection screen no longer fails to load diagnostics and module status.
  • Closing an app is no longer reported as failed when the app did close but one of its child processes refused to be stopped.

MopicHub 1.2.0

1.2.0 keeps the hub responsive when the license server is slow or unreachable, makes sure every app runs on a MOPIC runtime it is compatible with, and publishes a shared hub state that newer MOPIC runtimes can read instead of looking up licenses again.

Runtime and compatibility

  • Compatible runtime for every app. If an app needs a MOPIC runtime version that is not installed, the hub installs a compatible one right after the app is installed and again just before launch, with a waiting overlay. An app that requires a runtime is no longer launched without one.
  • Compatibility ranges come from the server. The runtime range for apps, engines, and the OpenXR runtime is read from the server catalog first, and from the app manifest only when the catalog has none. Required engines are matched to that runtime; if no matching engine version exists, the latest one is used after a warning.
  • Eye tracker matched to the hub runtime. The eye-tracking module is installed and launched in the version compatible with the hub runtime, and its license file is saved in that same version folder.
  • OpenXR runtime copy refreshed on install. Right after the OpenXR runtime is installed, its runtime folder is overwritten without a version check, so an outdated copy is not left in place.
  • New versions show up on the Add-on screen right away. After a background install (at startup, in the hourly sweep, or on catalog refresh), the newest installed version is selected immediately instead of after the tab is reopened.

License and stability

  • No freeze when the license server does not respond. Runtime initialization and monitor enumeration run off the main thread, network timeouts now cover reading the response body, and each license request is capped at 45 seconds, after which the hub continues with the cached state and shows a timeout notice. Display changes no longer pile up repeated license requests.
  • Exit always completes. Cleanup steps at exit are capped at 3 seconds each and 8 seconds in total, and the hub ends immediately if native calls are still pending. A hung exit can no longer hold the single-instance lock and block the next launch.
  • Shared hub state. The hub writes the connected monitors and their license decisions to hub_state.json in %APPDATA%\MOPIC whenever a license or monitor changes, including when a monitor is only moved, and marks the hub as stopped on exit. Newer MOPIC runtimes read this file and skip their own license lookup while the hub is running.

Diagnostics

  • Facts first while checking. While the first check is running, the Connection screen shows facts such as model, license key, camera, and GPU right away, and holds back verdicts, Fix buttons, and HubDoctor cards from the previous snapshot until the check finishes. The Details button stays available during the check.
  • A main-thread stall detector writes a log entry whenever the hub UI is blocked for more than 5 seconds, to help support locate freezes.

MopicHub 1.1.8

1.1.8 fixes a crash at startup when the eye-tracking camera was already connected, and keeps monitors that report a blank serial number from sharing one license.

Fixes

  • Crash on startup with the camera connected. If the camera state changed while the hub was still starting up, the hub could close with an error. Startup now completes normally whether or not the camera is connected.
  • Monitors without a serial number are kept apart. When a monitor reports its EDID serial as 0 or blank (for example a demo monitor and a laptop built-in panel), the hub now identifies it by model name and device path. Previously such monitors shared a single key, so they shared the manual license and product data, and the built-in panel could be classified as a MOPIC monitor. A manual license saved under the old key is moved once to the matching connected monitor.

MopicHub 1.1.7

1.1.7 makes OpenXR game launches start in 3D immediately, brings UEVR back as an automatically maintained system component, and adds key art to Battle.net game cards.

Games

  • Immediate UEVR injection. When a game is launched in OpenXR mode, UEVR is injected as soon as the main game window is detected. The previous settle delay of up to 60 seconds is gone.
  • UEVR is a system component again. mopic-uevr is installed and kept up to date automatically at startup, on catalog refresh, and in the hourly component sweep, and appears under System components. It is only launched when a game is started in OpenXR mode.
  • Battle.net key art. Game cards for Battle.net titles now show the key art cached by the Battle.net launcher, with the large icon as a fallback.

MopicHub 1.1.6

1.1.6 settles how the hub picks a license when more than one is available, moves live connection verdicts to HubDoctor so the Connection screen and support reports always agree, and adds a watchdog that restarts a tracking module stuck in initialization failure.

License

  • Fixed license priority. The license looked up by monitor serial is used by default. A manual key is used only when it was entered on purpose (the hub asks for confirmation when a MOPIC monitor is already connected), and a key inherited from older software comes after that. When candidates are equal the previous choice is kept. The tracking module runs with the same key the hub selected.
  • Camera check on manual key entry. If the camera bound to a manual key differs from the connected camera, the hub asks before saving, and a mismatched key is blocked rather than silently selected.
  • The license decision for each monitor, the reason it was chosen, and the context of a manual entry are written to the status file and included in support reports.

Diagnostics

  • Live verdicts come from HubDoctor. Whenever the module state, camera holder, USB devices, or loopback status changes, HubDoctor evaluates the situation and the Connection check list and cards show its verdict with area, evidence, and Fix actions. The hub's own camera, USB 3, and loopback checks are replaced by this. An older HubDoctor engine falls back to the previous hub verdicts.
  • Watchdog for a tracking module stuck in initialization failure. A module that stays in init_failed for 30 seconds is restarted, with the wait doubling on each retry up to 10 minutes. Restarts are deferred while the camera is in use or a check is running, and the backoff resets once tracking is idle or active.
  • The first busy check on a camera with no identifiable holder is treated as undetermined. An error card appears only when the second check confirms it.
  • The startup report is sent after the module has come up and the recheck has settled, so it reflects the real resting state.

MopicHub 1.1.5

1.1.5 removes a false camera-in-use error that could appear after a hub update, keeps the OpenXR runtime pointed at MOPIC after installs, and sends every startup diagnostic report to MOPIC support.

Fixes

  • False camera-in-use error after a hub update. When the hub restarted for an update, the tracking module was force-closed and its camera re-enumerated on USB at the same moment the hub probed it, which was recorded as another program holding the camera. The hub now waits a few seconds after a USB change before probing, re-checks a busy camera that has no identifiable holder every 15 seconds and clears the state by itself, and shows a warning (checking again shortly) instead of an error until the busy state is confirmed twice.
  • OpenXR active runtime restored after install or update. Right after the OpenXR runtime is installed or updated, the hub checks the system ActiveRuntime and switches it back to MOPIC if another runtime took it over.

Improvements

  • Permission expiry notice moved from 30 days to 7 days. The startup toast and the red highlight on the monitor card now appear only within a week of expiry, so a license with plenty of time left no longer triggers a notice.
  • The startup diagnostic scan report is sent to MOPIC support on every launch, regardless of the result, and tracker fallback reports are tagged separately from Full check reports so support can tell them apart.

MopicHub 1.1.4

1.1.4 removes stale verdicts from the Connection screen: results are shown only after the current check has finished, and leftover state from a previous monitor or OpenXR version no longer leaks into the display.

Fixes

  • Old OpenXR version still shown as installed. After an automatic OpenXR runtime update, the version list could show both the previous and the new version as installed. The cache is now rebuilt from the installed manifest so only the actual installation is marked installed and selected.
  • No stale verdict while a check is running. While a basic scan is in progress the Connection screen and status bar show a checking state instead of the previous result, so a problem or all-clear from the last scan is not displayed before the new one finishes.
  • Disconnected monitor no longer drives the verdict. When all MOPIC monitors are disconnected, the license snapshot and environment are updated to the current state, so HubDoctor no longer reports the model of a monitor that was removed.

MopicHub 1.1.3

1.1.3 aligns HubDoctor with the hub's own license decisions so diagnostics and the Connection screen never disagree, and makes sure MOPIC apps run on the high-performance GPU.

Diagnostics

  • HubDoctor follows the hub's license decision. The hub records which license is actually in effect for the eye-tracking monitor and keeps the environment in sync with it. HubDoctor reads that snapshot instead of making its own guess, so a manual key stored for another monitor is no longer reported as active.
  • Fix buttons match hub capabilities. HubDoctor only offers Fix actions the installed hub can perform, so a newer diagnostics engine never shows a button that does nothing.
  • Report metadata from HubDoctor is consumed by the hub for display and upload.
  • When the tracker falls back to a secondary detector, a basic scan report is uploaded once per session to help diagnose the cause.

Performance

  • High-performance GPU preference for MOPIC apps. Installed MOPIC app executables are registered in Windows graphics settings to use the high-performance GPU. Registration is per executable path, so it is refreshed when an app is updated. A preference the user set manually is left unchanged.

Other

  • Hub runtime pin updated to 2.0.5.

MopicHub 1.1.2

1.1.2 changes how the hub loads its own native components: they now come from the installed MOPIC runtime and HubDoctor engines instead of being bundled inside the app, so component fixes reach the hub without a new installer. It also tightens the license rules and fixes an input focus bug.

Runtime and components

  • Hub runtime pinning. The hub pins the MOPIC runtime version it uses (currently 2.0.4) and downloads it at startup if it is missing, showing a waiting overlay. Native libraries (MopicAuth, mopic_runtime) are loaded from that pinned engine folder. Automatic installation keeps both the latest runtime for apps and the pinned version for the hub.
  • HubDoctor engine. mopic_doctor.dll is no longer shipped inside the app. It is loaded from the installed mopic-doctor engine that is compatible with the current hub, which now appears under System components. If no compatible version is installed, the hub downloads the latest compatible one at startup; without it, diagnostics are disabled rather than blocking the hub.
  • Smaller package. Five native DLLs that duplicated the runtime engine were removed from the app bundle.
  • OpenXR runtime install no longer redownloads a runtime that is already in use. Installs inside the queue re-check the disk first, fixing a case where the OpenXR runtime sync failed with a file-busy error right after first launch.

License

  • Register license button. When a connected monitor cannot be identified, the monitor card offers Register license directly.
  • Clearer manual license rules. Only keys entered by the user or inherited once from older MOPIC software on first install are accepted as manual licenses. Stale environment keys left by other software are ignored, and a key inherited for one monitor is no longer attached to a different monitor later.
  • The source of the active manual key is written to the status file so HubDoctor can explain where a license came from.

Fixes

  • Input fields could not be focused after a confirmation dialog. Browser-style confirm dialogs were replaced with native dialogs, fixing a case where the license key field would not accept a cursor after registering a monitor.
우리 서비스에 어떻게 적용할 수 있을까요?