Unity plugin improvements, .Net bindings and new projects

Dear OSVR developers,

We wanted to briefly update you on several OSVR improvements:

Unity plugin:

Refers to version: 0.1.71-ga184206

Key changes (see CHANGES.md file for complete list):

  • Updated plugin to be compatible with Unity 5.
  • Increased frequency of OSVR client updates for reduced latency as well as additional performance improvements
  • Dynamically sets display parameters (field of view, resolution, side by side mode) based on JSON display descriptor. This allows the same Unity app to run well with multiple different OSVR-supported HMDs

We recommend that existing users of OSVR Unity plugin re-build their project with this new plugin. The performance and usability improvements are worth it.

Additional updates:

  • Improved locating of DLLs in both the editor and built players, and improved locating of the (temporary, game-local) json file in built players. Previously, some Unity projects ran fine inside the editor but had to have files copied over to run standalone. With this fix, it is no longer necessary to move the built executable to the project root.
  • Modified DisplayInterface to look for json in _Data folder at runtime.     If it’s not there, load json from Unity scene as usual.
  • Moved DLLSearchPathFixer.fix() to Awake().     Removed constructor.
  • Created static DeviceDescriptor.Parse method and moved code from DisplayInterface.GetDeviceDescription over to to this static method.
  • Untabified changes to DeviceDescriptor and DisplayInterface.

This version does not yet include support for Unity 5 64-bit – that is in progress and being tested, expected soon. https://github.com/OSVR/OSVR-Unity/issues/19

Vuzix plugin:

Version v0.1-18-g7758a1c

  • Resolved issues with orientation and zero-point.

 

.NET bindings:

The base .NET bindings for OSVR have been extracted from the OSVR-Unity plugin into a separate repo – https://github.com/OSVR/Managed-OSVR – for optimal re-usability, and are being actively improved by us and the community. This separate version currently includes support for 32 and 64 bit native libraries, have a fully MSBuild-based build system, and builds assemblies for both .NET 2.0 and 4.5 framework versions. A NuGet package is coming soon https://github.com/OSVR/Managed-OSVR/issues/2

New projects on osvr.github.io:

  • OSVR HDK: includes production file for the OSVR Hacker Developer Kit
  • sensics/Latency-test: includes code and instructions for Arduino-based latency tester

 

Definition of OSVR interfaces:

We are working to define and enhance additional OSVR interfaces such as eye tracking, locomotion (for devices like those from Cyberith and Virtuix) as well as support additional devices. If you are interested in participating in this process, please let us know.

Additional updates:

1. We have updated a couple of white papers on the OSVR site:

2. We are providing additional suggestions for OSVR roadmap on our Wiki page
3. The OSVR waffle.io board contains an overview of issues currently in GitHub issue trackers for all OSVR framework projects. It summarizes the issues in a number of lists:

  • Those under “Contributions Wanted” are likely to be the easiest entry points into contributing, though in some cases they may simply be tasks that require skills that existing contributors do not have.
  • Those under “Ready” are not blocked by any other issues and are approved for development for integration.
  • Those under “In Progress” should typically show a user who is working on them – if you want to take on a task, move it here and assign yourself.
  • The “Done” list should be self-explanatory – it contains closed issues from the past 7 days (automatically removed).
  • All issues not otherwise assigned to a list end up in “Backlog”. You’re welcome to work on these (whether through verification, triage, or development), though please use the issue thread to communicate your plans and progress.

Of course, the issue lists are not all-encompassing: if you’ve got a contribution you’d like to make, we’d love to see it! Filing an issue on the right project would be a great first step.
These latest updates also include contribution from the OSVR community, for which we are very thankful.

Interested in contributing? Start here: http://osvr.github.io/contributing/

Any questions or issues? email support@osvr.com

Thank you for being part of OSVR!

 

Leave a Reply

Your email address will not be published. Required fields are marked *