Viture Beast Support

[lukeedward12]

Just bought the Viture Beast, and am curious when driver support will be coming to Breezy? Super excited to use Breezy when the Beast Driver is released! Will likely get the Pro Plan

[wheaney]

I'm waiting on VITURE to update their SDK with full Beast support. Their Beast firmware update from a couple days ago included release notes that seemed to hint that it was the last firmware update needed to allow for SDK usage, so I hope that the SDK update will be coming soon as well. Nothing I can do on my end otherwise.

[jerafsarkul]

Hi @wheaney — the VITURE SDK update you were waiting for appears to be out. I can confirm the following on CachyOS (Arch, kernel 7.0.11) with xr-driver-git 2.9.2:

What works:
The official VITURE SDK demo (glasses-demo) successfully detects the Beast and runs 3DOF tracking out of the box:

Device: Viture Beast
Mode: Native 3DOF (on-device)

What the new SDK contains:

• libglasses.so (2.2MB) — Beast-compatible, replaces the old one
• libcarina_vio.so (55MB) — new VIO library for the Carina chip
• viture_device_carina.h — new header exposing XR_DEVICE_TYPE_VITURE_CARINA and a separate init API (xr_device_provider_register_callbacks_carina, xr_device_provider_set_dof_type_carina, etc.)

What's failing in xr-driver-git:
libGlassSDK.so still uses the old Gen1/Gen2 code path — it calls open_imu (MsgID 0x0301) which returns -3 immediately and eventually segfaults. The Beast (USB 35ca:1201) needs to be detected as XR_DEVICE_TYPE_VITURE_CARINA and use the new Carina API path instead.

Happy to share full strace output, lsusb -v interface layout, or any other diagnostics if helpful.

[wheaney]

The latest SDK version minimally supports the Beast in that I can receive the raw, unfused IMU data. All other VITURE devices send the fused pose data through the SDK and that's the path my driver requires... It's kind of the point of the SDK so I don't have to roll my own fusion which will be inferior to a first party algo. I'm waiting for VITURE's dev team to notify me when there's an update that actually provides that full support.

[wheaney]

I just pulled up the release notes to make sure I wasn't missing a notification that it was ready. https://www.viture.com/release-updates/sdk

You can see this in the 2.3.1 notes:

IMU pose callback is not delivered
xr_device_provider_register_imu_pose_callback and xr_device_provider_open_imu(VITURE_IMU_MODE_POSE) return success on Beast, but the firmware emits raw IMU samples only — the registered pose callback will never fire

I need that imu_pose_callback to be supported for Beast, so that's the change we're looking for in an upcoming SDK update.

[TheCelebrimbor]

@wheaney thanks for keeping this in your mind! Would love the support

[kungfusaini]

Yes, very eagerly awaiting!

Would love an update here whenever they update the SDK :)