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.

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.

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.

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.

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.

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.

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.

1.1.1 is a stability release focused on eye-tracking diagnostics: the Connection screen now tells you exactly which step failed and can fix common display and camera problems with one click, and Full check reports are sent to MOPIC support automatically.

Eye tracking and diagnostics

• Initialization failures are reported by stage. When the eye-tracking module fails to start, the panel now distinguishes camera open failure, tracker device preparation failure, license re-registration required, and configuration errors, each with its own guidance. The raw error text is shown only for the camera stage.
• Camera-in-use detection. If another program is holding the camera, the hub identifies it, confirms the state, and offers to close the program and restart the tracking module.
• Fix buttons in Diagnostics. Problems found by the check can be corrected in place: display resolution, refresh rate, and orientation, extend-mode display setup, GPU preference, firewall rule, closing the camera-holding app, restarting the eye tracker, re-applying manual settings, and relaunching the hub.
• Full check reports go to MOPIC support automatically. After a Full check the report is uploaded to the MOPIC log server regardless of the result. If the PC is offline the report is kept locally and re-sent on the next start. The upload result (server id, saved offline, or failed) is shown on the Connection screen. A per-installation id groups reports from the same PC.
• EDID unreadable is now a monitor verdict. A monitor whose EDID cannot be read is reported as such instead of appearing as not a Mopic monitor.
• Eye-tracking module state is written to a status file for HubDoctor and support tooling.
• The hub opts the eye-tracking module out of Windows power throttling so tracking stays responsive on battery and in efficiency modes (stopgap until the module handles this itself).

License and connection

• Manual license entry merged into the monitor list. Monitors with a manually entered license appear in the same list as detected monitors, and license keys from older MOPIC software on the PC are offered for import.
• Reload button in license details. Permissions changed on the server can be pulled into the hub from the license detail screen without reconnecting the monitor.
• The license is re-queried before the eye tracker restarts so a renewed license takes effect immediately.

Fixes

• Fixed a brief false error banner right after startup, before the tracking module had started.
• Added the U15A731 panel variant to the monitor lineup so it is recognized as a Mopic monitor.
• Typo fixes in UI text.

Other

• Updated native components: libmopic_monitor.dll, mopic_doctor.dll, mopic_runtime.dll, MopicAuth.dll.
• Native .node modules and previously unsigned DLLs are code-signed during packaging.

1.1.0 makes AI 3D the default way to play, lets you pin an OpenXR runtime version, keeps system components up to date automatically, and adds HubDoctor integration for on-site diagnostics.

Games

• AI 3D is the default launch mode. Every game card now offers a split button: Play in AI 3D as the primary action and Play in OpenXR (UEVR) as the alternative for supported Unreal titles. Cards are laid out in four columns.
• GPU gate warning for AI 3D. On machines without a supported GPU the hub warns before launch. DirectML is used as the fallback backend, and a CUDA-capable NVIDIA GPU is recommended for the best result.
• Depth Stream install dialog. If Depth Stream is missing when you start an AI 3D game, the hub offers to install it on the spot.
• UEVR moved to Add-ons as an optional install. It is no longer installed automatically with the system engines. Install it from the Add-on tab when you need OpenXR playback.
• UEVR user.config seeding. A default user.config is written on install so SteamVR is no longer picked up as the runtime by mistake.
• SteamVR detection false positive fixed. SteamVR is no longer reported as active when it is only installed.
• Game rescan hang fixed. Rescanning the library no longer stalls on certain store manifests.

OpenXR runtime

• Manual version install and pin. Choose a specific OpenXR runtime version and install it manually. A pinned version shows a Manual badge and is excluded from automatic updates; a toast tells you when a newer version is available.

System components

• Hourly automatic update of system components. Runtime, libraries, and the eye-tracker module are checked and updated every hour while the hub is running, not only at startup.
• Obsolete DLL cleanup. Leftover native DLLs from earlier releases are removed during installation.

Diagnostics and connection

• HubDoctor integration. The hub exposes eye-tracker status through a shared schema and ships mopic_doctor.dll so HubDoctor can read device and module state directly.
• Loopback UDP self-diagnosis. At startup the hub tests its own loopback UDP channel and reports when security software blocks it, which previously showed up as a camera stall.
• RealSense DFU recovery mode detection. A camera stuck in firmware recovery mode is identified and reported with guidance instead of appearing as a missing camera.
• USB descriptor decoding fix. Corrected parsing of some USB device descriptors that caused cameras to be misidentified.
• USB camera add and remove events are written to the log for troubleshooting.

License

• Manual license input. Enter a license directly when automatic lookup by monitor serial is not available.

Other

• Native .node modules and DLLs are now code-signed.
• Developer tools open docked inside the window instead of a separate window.