A new build of OSVR, along with its documentation, is deployed to the preview site.
This build updates to both the OSVR core and is numbered 322
Here are the key changes in this build:
- Interconnection is now user-defined. A key attribute of OSVR is that it allows connecting various software components while providing a common interface to the application. For instance, a Razer Hydra component might be connected to a “1-euro” smoothing filter which then connects to hands/left and /hands/right outputs. Previously, these interconnections (or “the routing”) were hard-coded. Now, they are defined in the osvr_server_config.json files. In the future, we expect an interactive tool or auto-routing, but for now this JSON file provides greater flexibility in changing components.
- Coordinate system transformations. Another part of osvr_server_config.json allows coordinate system transformations such as swapping axes or rotating on a certain axis. This can help with calibration of trackers that are positioned in non-standard ways. For instance, here is an example setting where some of the bold lines show swapping axes or rotations. BTW, you can leave the tracker view app open when you change this, if you want, and just shut down the server, change the config file and start osvr_server again. The viewer app will automatically reconnect.
- Oculus Rift support. This is an experimental plugin that allows using the orientation and position tracker of the Oculus DK2 inside OSVR. This shows the promise of OSVR to support applications across multiple HMDs and can also be used as a debugging tool. If you want to try this out, let us know.
- Hardware redetect. Starting from this release, every time an application launches, osvr_server will redetect the available hardware. This means, for instance, that if you forgot to plug in your Hydra, you don’t need to restart osvr_server after you plug it in. Just restart your app.