Highlights

change them, and Store on device… (now also for gravity compensation) is how you keep a

value across a power cycle. Values saved in the Hub by 1.4.0 are no longer replayed — see

_Before you upgrade from 1.4.0_ below.

one Settings → Privacy switch; every install that never answered is reset to off and asked once.

Settings tab to keep the tool pointing the way you hold it over long sessions. Needs service

3.5.7 (embedded in 1.5.0) and grip firmware (handle release 1.3.1) for the non-Off options.

501, Freeform 2026.2 is recognised, VerseGrip battery no longer sticks at 0%, mount edits stick,

newly connected devices appear without a refresh, and where WebGL is unavailable the 3D views

show the device image instead of crashing.

orientation on every device instead of tilting with the mount.

rejected before the device restarts, a failure says what went wrong, and the update page shows

its steps with Retry.

New features

Device Settings (all users)

is about to write, as a warning once more than one setting changed.

records whether it can be trusted and now also covers devices connected before the Hub started;

Reset to defaults is withheld while the snapshot is untrusted.

immediately), RAM-only settings (applied with Auto Apply) and Pairing.

off, and are no longer saved or replayed by the Hub — Store on device… is the only

persistence. Return to home keeps the Hub save (Save in user prefs). Anyone who saved a value

in the Hub on 1.4.0 and never stored it on the device is affected; see the upgrade call-out.

VerseGrip (service ≥ 3.5.7)

choosing a profile reconfigures every VerseGrip. It needs service 3.5.7 (embedded in 1.5.0) and

grip handle 1.3.1; below them only Off is available and a note names the version it needs.

Values that match no profile leave the picker unselected.

Privacy (all users)

replace the two switches and two pages. Neither Sentry nor PostHog starts or sends until you opt

in. Support bug reports still send without consent, through a feedback-only client. The Windows

installer shows the Hub's own agreement and Next stays disabled until I accept is ticked.

_On upgrade, both settings reset to off for every install with no explicit answer — even if you

had both on, and even with "show on new updates" off — and the page asks once. Answer it, or turn

the switch on in Settings → Privacy._

BigVerse

"BigVerse" type name (before: no mesh). Body yaw and both arms follow the live joints.

BigVerse, instead of turning with the device or its mount. _The paired grip no longer tilts with

a mount rotation on any device._

Improvements

and firmware ≥ 7.10). Auto Refresh's source row now offers Continuous, and the source

selector appears as soon as Continuous is available. With an older service or firmware, its

tooltip names the version it needs; nothing to do on upgrade.

shares the common gizmo and orbit controls.

calendar day in every time zone.

and Auto Apply on, the rotation now reaches the device when you release the gizmo; with Auto

Apply off nothing changes until Apply_); fields commit on Enter, stop at their limits, and the

gravity factor steps with the wheel.

Modified pill.

flash, reboot, reconnect), moves its progress bar while writing, and confirms the new firmware

version once the device is back; the error screen now has the cause, a recovery hint, Retry,

Back and View logs.

of hanging when the network is slow or offline.

Fixes

Bugs that were present in 1.4.0.

tab, basis, preset and filter changes, workspace scale and recenter, and the pie menu's reads.

work.

reading must hold for 1.5 s before it is trusted.

lands; switching the mount off and on restores its mode.

the forced license dialog.

straight away.

file that cannot be read is rejected before the device restarts; when a flash fails before

anything was written the device is booted back to its previous firmware; waiting for the

bootloader is bounded (about 20 s instead of forever); a failure names its cause instead of

"Error flashing firmware".

sessions, VMs and webviews with the GPU disabled show the device or demo image with a "3D view

unavailable" note in the Overview panels, setup modals, Input Control, Visualizer and Academy.

frame no longer drops the whole update, and a grip re-classified under the same id refetches

its extras.

Before you upgrade from 1.4.0

One warning stands above the rest: if you saved a handedness or gravity compensation value in

the Hub on 1.4.0 and never used Store on device…, set the value and store it on the device before

or right after upgrading. The Hub prunes that saved entry on first read and no longer replays

it, so the device falls back to its own stored value at the next power cycle — a bench setup may

change. Use Store on device… from the field's Modified badge.

Also small: Blender gestures in Input Control now fire for any window whose name contains

"Blender" (it was an exact match), like the other apps.

Deprecations

None.

Known issues

the reset lands the factory constant while the Modified badge anchors on the real power-up

default, so the badge can read Modified right after a reset. Service 3.5.7 restores the

boot-cached value, so the service 1.5.0 embeds resolves it; not re-tested against 3.5.7 in this run.

"Save as PDF" in that dialog for now.

Highlights

docked stylus is set to moved from 135 to 180 degrees. This is the single expected visible

difference from 3.5.6 in an otherwise unchanged default session — ungated, no opt-in, every user

on handle firmware 1.3.1 or above. Detailed under Fixes.

20 Hz instead of freezing as soon as an application starts driving it (Inverse3 / Minverse

firmware 7.9 or newer, on by default).

config/torque_scaling, config/gravity_compensation and config/handedness returns the value

the device powers up with instead of a factory constant compiled into the service — so a

left-handed device saved as left-handed no longer resets to right-handed.

one shared mount or body-orientation write used to emit a session-updated per holding session,

none of them naming the device; every holding session still refreshes from its next snapshot.

Internal improvements

range 0–5000) tunes the live orientation read; the 50 ms device motion timer is an effective

floor.

devices/*inverse/query_orientation_on_idle on against old firmware tells you the knob is inert

instead of staying silent.

its last good value forever; the held value itself is unchanged, so the device stays usable.

default events channel exactly as before — only the device-scope cause was withdrawn, and

handedness, torque_scaling and gravity_compensation keep their per-session announcements.

Fixes

stylus is set to on inkwell calibration moved from 135 to 180 degrees, and the value became the

setting devices/*inverse/inkwell/dock_heading_deg. Measured 2026-09-22 on a Minverse with a

stylus at handle firmware 1.3.1: the old 135 degrees left the docked pen 45 degrees short, so the

yaw estimator had to drift it back (+42 to +50 degrees observed); the residual is now within about

5 degrees. Not stage-gated — the dock-calibration path always runs — so a docked pen's

published orientation changes by 45 degrees for every user on handle firmware 1.3.1 or above.

Below that floor the firmware ignores the value and snaps the full pose, so those users see no

change.

application started streaming forces and every consumer read a stale handshake snapshot. It is now

polled on the existing motion timer and is live in-session.

compiled-in factory constant over the device's own stored configuration, so "reset to default"

and the device's real power-on state diverged — config/handedness always snapped to right

regardless of what the device had been saved as. All three now restore the stored value, falling

back to the old constant only for a field that was never read from the device.

the payload carries only session_id, profile and scope — no device identifier — so a

subscriber could neither attribute a copy nor deduplicate the set. The device-scope announcement

is withheld pending a device-addressed replacement; the per-session refresh is untouched.

Potential breaking changes

a reset means: the reply and the written value are now the device's stored configuration rather

than a fixed service-side constant. Response shapes are unchanged and the values only differ on a

device whose stored configuration differs from the factory constant — but an integration that

asserted the literal constants (false / {enabled: true, scaling_factor: 0.0} / right) will

see different values.

was effectively static for a streaming client now moves at 20 Hz. A consumer that treated it as

constant-after-attach sees new behaviour with no opt-in.

config.body_orientation when the cause is a device-scope write, and the deprecated flat

body_orientation scope follows the same lane rather than leaking back to the default channel.

Migration: stop treating the event as the refresh trigger and read the value from the session

snapshot — it still refreshes on every holding session with no opt-in at all. The equivalent

session-scope events, and the handedness / torque_scaling / gravity_compensation

announcements, are unaffected.

bug fix and is published under Highlights and Fixes. Recorded here because the observable value

moves with no opt-in for every user on handle firmware 1.3.1 or above, so anyone who calibrated

their own application against the old 135-degree datum has real migration work. No shape changes.

Deprecations

whenever the new poll interval is non-zero, but it is deliberately not flagged deprecated in

3.5.7 — that deprecation is scheduled for 3.6.

🔖 Release 7.10.1

7.10.1 (2026-10-13)

Bug Fixes

Highlights

gravity compensation and home return can be staged, applied and — for the first time — saved;

the Hub restores them automatically when the device connects. Two upgrade notes ride along — see

If you might roll back to 1.3.0 and Store on device… below.

live under Show advanced settings; on service 3.5.6 or newer, no experimental-API opt-in is

needed at all.

and Transfer to profile hands the rotation back when you want it.

inverse3-family units get a telemetry panel instead of a misleading mesh.

notice, with a redesigned animated intro behind a new ? button.

and safety notifications included.

rewritten or deleted on upgrade.

New features

Device Settings tab — persistence and one field model (all users)

return gain Modified/Saved pills, a per-field menu and a footer Apply + Save/Reset row. Profiles

saved before 1.4.0 are migrated once, one-way — back the file up before any return to 1.3.0

(see the rollback call-out).

the device's first calibration. Fields the device already matches are skipped, and an open

Settings panel reseeds its badges instead of stranding a stale Modified.

the new Store on device… action — behind a warning, because it persists the device's entire

configuration against a limited lifetime write budget.

"Revert" splits into _Revert unapplied edits_ and _Revert to Saved_.

home return, disabled below service 3.5.6. Handedness deliberately has none: the service's reset

forces right-handed, which would physically flip a left-handed unit.

Profiles tab.

Device mount (Show advanced settings)

gizmo-space toggle and device reset. Nothing applies while you drag; everything commits through

the panel's Apply.

source selector replace the old two-option control. Turning the master off also resets the

rotation on the device — the confirmation says so first.

with the experimental API on; below either floor it shows disabled with the missing half named.

deleted: the rotation returns when the device mount is turned off.

applying it immediately. It applies, it never saves.

no more out-of-step reads.

Device panel and 3D views (all users)

the Control readouts become pills, collapsing to one muted pill when the device is idle.

Input Control (all users)

Control is active — no longer a bare button in the bottom-right corner.

the left-handed caveat now lives inside that intro.

Improvements

now lands off, home-return reset genuinely switches on — and the live, no-opt-in mount

surface.

checkbox and acceptance flow. The View License browser link is gone (use Download PDF), and

the Updated date currently renders as a raw ISO date — a tracked regression.

rather than unresponsive.

tutorials now read in all seven non-English locales, and strings that used to bypass translation

— the tray menu, the firmware-update warning, the safety overlay and its notifications — come

through the same layer, falling back to English if a string is missing. Product names stay in

English on purpose.

Fixes

Bugs that were present in 1.3.0.

instead of rendering live and failing every read and write.

from the connected service's version.

orbiting during the animation, and no longer leaves the controls stuck.

telemetry panel filling the column — visible on narrow windows too.

If you might roll back to 1.3.0

One warning stands above everything else in this release: back up device-settings.json before

your first 1.4.0 launch if there is any chance the machine returns to 1.3.0. The migration is

one-way, and a 1.3.0 build silently reads the migrated file as empty and overwrites it on its

first save. Restoring your copy is the only way back.

Deprecations

mount master toggle plus Auto Refresh.

read the agreement outside the app.

overwrites the new file rather than refusing it. Keep a copy.

from service 3.5.6 up; the Hub still speaks the old pair to older services.

No action, trigger or keyboard shortcut was deprecated this cycle.

Known issues

Shipped behaviour we know about and are not fixing in 1.4.0.

damping's displayed value is not always correct, and the force gate starts at 0.3, showing

_Modified_ from the first frame. Both need a service-side fix first.

unchanged out of the box: the default Inkwell source recaptures the rotation on every

recalibration, and changing that default on a minor release would be a breaking change. The

escape is opt-in: switch Auto Refresh off to freeze the rotation, then save it — the Hub

restores it on every connect.

Input Control intro.

Highlights

just the one that wrote. A second viewer refreshes on its own session-updated event instead of

polling — exactly one event per holding session, and never two for the writer.

always reporting the mount the session configured. The label that tells you which of the two you

are looking at is now truthful by construction, in every output shape.

service served a value captured when the device came up and never revisited it. It can now

refresh that reference on demand at the client's own render cadence — rate-limited service-side

so a fast client cannot flood the device link — and announce the change once the mount has

actually rotated.

Internal improvements

Wireless VerseGrip's inertial yaw drift: it fits the grip's absolute yaw against the motion of

the paired Inverse3 or Minverse it is attached to, and once a stack of quality gates all hold, it

writes a single correction back to the grip firmware. It ships disabled, is reachable only

with the experimental opt-in switch on, and carries a runtime switch that forces every live grip

back off the moment it is flipped — non-optional for something that writes to device firmware.

selection is validated — firmware capability and device readiness — before any device is changed,

so a mixed-firmware fleet can no longer end up half-switched behind an error on the second device.

two concurrent requesters could lose each other's answer, and one ambiguous value stood for both

"refused" and "nothing yet" — which could turn a refusal into a retry storm. Each request now

carries its own token, a request that never reached the wire registers nothing, and a lost

response resolves as failed instead of wedging. The sweep that does this costs nothing while no

request is outstanding.

pen performs a full pose recalibration, which is correct on every shipped pen regardless of

firmware version; that path is explicitly exempt from the capability floor introduced for

computed heading corrections, and the exemption is spelled out at the call site rather than

inferred.

Fixes

Despite its name, the scaling_factor field on config/gravity_compensation is not a

multiplier: it is the extra end-effector payload mass, in kilograms, that the device compensates

for on top of its own weight. The reset took the name at face value and restored the "neutral"

factor 1 — a phantom one-kilogram payload — so a reset left the device pushing the handle up,

which is not what a freshly connected device does. The reset now returns the real default:

compensation enabled with scaling_factor at 0, meaning the device carries its own weight and

assumes no payload. If your application had been using the reset to raise the compensation

strength, set the value you want explicitly instead.

come to disable home return while telling the caller it was enabled — a reset now genuinely

restores the factory default (on), and the value your application reads back afterwards is the

value the device is actually using.

a write that landed on the device itself — shared by every session holding that device — refreshed

only the writing client's configuration, and the device-wide routes refreshed nobody at all. Any

other client on the same device kept reporting the old value until it polled. Every holding

session is now notified.

previous dock persisted across docks, so the second dock treated its first rejection as the end

of its retry window. The retry window is now reset per dock attempt.

reassigned by the connection thread while a staging path read it under a different lock. The

identifier is now snapshotted once under the correct lock, and every path below — refusals

included — works from that copy.

message paths assembled their payload and checksum and requested the send without taking the

write lock, so two senders could interleave on the shared buffer.

Potential breaking changes

was deleted or re-pathed, the public C API has no diff, and no settings key was renamed, removed,

or given a new default. Applications that opt in to the SDK's preview or experimental surfaces

do have migration work this cycle, including a switch-tier change and a removed token set;

every step is documented in the engineering companion changelog.

route or response shape changed, but an application that relied on the reset writing a

scaling_factor of 1 now gets the factory default of 0 — compensation itself stays enabled

either way. Set the value explicitly rather than depending on the reset; see the fix above.

changed, but an application that relied on the reset to disable home return now finds it

enabled instead. Set it explicitly to off after a reset if that is what you need; see the fix

above.

session-updated event only ever arrived because of its own write will now also receive one when

another client changes a device they both hold, followed by a full configuration render. This is

the intended consequence of the fan-out above; a client that simply re-reads on the event needs no

change.

🔖 Release 7.10.0

7.10.0 (2026-09-24)

Bug Fixes

Features

Highlights

New features

License and first launch

Freeform

Improvements

Fixes

Bugs that were present in 1.2.0 and are resolved in 1.3.0:

Changes to existing behaviour

Deprecations

Known issues

Highlights

stages before a stable release: internal alpha builds, then published beta builds that soak

before anything reaches stable. Every stable release is now preceded by a validated beta.

X.Y.Z-develop.N are now X.Y.Z-alpha.N, followed by X.Y.Z-beta.N on the beta channel.

The old naming sorted "develop" builds above "beta" builds under semantic-versioning

precedence rules; the rename fixes that ordering permanently.

existing history.

Internal improvements

deliberate, manually-triggered process gated on passing tests, and the whole new release

pipeline was rehearsed end-to-end before it shipped.

by roughly three quarters, while the full multi-platform test matrix still gates every

promotion toward a release — coverage before a release is unchanged.

1.0.228 -> 1.0.229 (lockfile-only patch bump), the release tooling's semantic-release

25.0.8 -> 25.0.9, and the Alpine container base image 3.20 -> 3.24.

Fixes

code changed. The auto-generated release notes list a handful of fixes to the new release

pipeline itself; these hardened brand-new infrastructure before it shipped and have no effect

on deployed SDKs.

🔖 Release 7.9.1

7.9.1 (2026-09-09)

Bug Fixes

🔖 Release 7.9.0

7.9.0 (2026-09-08)

Bug Fixes

Features

Performance Improvements

Features

Bug Fixes

3.5.4 (2026-08-26)

Internal Improvements

Bug Fixes

🔖 Release 7.8.1

7.8.1 (2026-08-25)

Bug Fixes

Bug Fixes

Features

Bug Fixes

3.5.3 (2026-08-06)

Internal Improvements

Bug Fixes

Performance Improvements

🔖 Release 7.8.0

7.8.0 (2026-08-06)

Bug Fixes

Features

🔖 Release 7.7.1

7.7.1 (2026-07-28)

Bug Fixes

Bug Fixes

Features

Performance Improvements

Reverts