> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/section-01-getting-started/release-notes-frameblaster.md).

# Release notes: FrameBlaster

Release notes for Velogic FrameBlaster software that runs on Orbbec Femto Mega cameras to enable integration with Velogic Studio.

## Release Notes - FrameBlaster

This section summarises bugs and features released to Velogic's FrameBlaster software, which runs on Orbbec Femto Mega cameras.

Note that new releases of the FrameBlaster software are NOT automatically delivered to your camera. You can check the FrameBlaster version number in the "About" section of the Orbbec camera configuration UI, and if a new version is available, you can update it from there.

## v1.5.2877 on 2025-10-21

1. Fix for issue where skeleton looks one frame ahead of colour image

## v1.4.2819 on 2025-06-30

1. Better sync of frame time with host computer time
2. Fix issue with depth frame being out-of-step with color frame, but only on newer firmware
3. Ability to provide firmware and hardware version numbers to host computer
4. Stop streaming frames if there's a network disconnection
5. This is the first version that Velogic Studio users can update onto the camera themselves, with the new "About" panel on the camera configuration.

## v1.3.2511 on 2024-06-04

1. Initial release


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.velogicfit.com/section-01-getting-started/release-notes-frameblaster.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.