A new build of OSVR core and Unity plugin, along with its documentation, is deployed to the preview site.
OSVR core update is numbered 339. Updates are:
- Supports routing and transforming tracker reports from external VRPN servers (running on the same or different machine – if same machine an alternate port must be used). This screenshot (of a sample config file included with the snapshot) shows the portion of the JSON transform tree to route data from sensor 1 of a VRPN device called “YEI0@localhost:3884” (that is, running on the local machine, port 3884 instead of the default 3883 – note the leading slash added in the JSON.) This provides initial basic compatibility with all trackers supported by a VRPN server.
- Silence client-side messages that the server is not responding, which are often spurious due to the current routing setup.
- Fix to routing code to solve issue of missing input data.
- Avoid re-detecting Razer Hydra upon application connect that triggers a hardware detect.
- add reference to the separate Unity docs, mention that the server must be running.
Unity plugin update is numbers 31. Key changes:
- Includes fixes from core.
- Stability and lifetime management improvements.
- Feature: Button and analog support: Add a Unity-specific wrapper around the .NET OSVR code, to simplify listening for button or analog callbacks. Example scripts included, with example usage in the “minigame” scene.
- Docs for writing a callback handler.
- Add “known issues” section to docs, primarily to note that at this time, input data only comes in during the first time a game is run during a single Unity editor session. The workaround is to close and re-open the Unity editor. (No need to restart the server: this is specific to the Unity client)