Skip to content

megbeckim/arbounce

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Project Tango UnitySDK Example Project

Copyright (C) 2015 Google Inc.

Contents

These are the Project Tango UnitySDK Examples compilable in Unity 5 and above:

  • Motion Tracking Example - This example shows how to use our motion tracking APIs.

  • Point Cloud Example - This example shows how to use the depth APIs, and use the pose data to transform the point cloud into world coordinates.

  • Area Description Example - This example shows how to use the Area Description File (ADF) APIs.

  • Persistent State Demo(Experimental) - The persistent state demo shows how to store/load data along with a specific Area Description File, to create a virtual real time strategy game/experience.

  • Mesh Builder(Experimental) - The mesh build demo shows how to build a mesh using both motion tracking and depth API.

  • Augmented Reality Example(Experimental) - The augmented reality example shows how to use the video camera overlay and motion tracking data to create a augmented reality experience.

Project Layout

The example project has the following folders:

  • Editor/Tango/ - Tango-specific Unity3D editor integration
  • Google-Unity/ - General Android lifecycle management
  • Plugins/Android/ - General Android and Tango-specific libraries
  • Scenes/ - All the Tango example scenes
  • Standard Assets/ - Unity packages we are using
  • TangoExamples/ - One subfolder here per example
  • TangoPrefabs/ - Common Tango prefabs, like a simple camera
  • TangoSDK/ - Unity3D interface to the Tango libraries

Support

First please take a look at our FAQ page. Most of the issues can be solved by the FAQ section.

If you have general API questions related to Tango, we encourage you to post your question to our stack overflow page.

You are also welcome to visit Project Tango Developer website to learn more about general concepts and other information about the project.

Contribution

Want to contribute? Great! First, read this page (including the small print at the end).

Before you contribute

Before we can use your code, you must sign the Google Individual Contributor License Agreement (CLA), which you can do online. The CLA is necessary mainly because you own the copyright to your changes, even after your contribution becomes part of our codebase, so we need your permission to use and distribute your code. We also need to be sure of various other things—for instance that you'll tell us if you know that your code infringes on other people's patents. You don't have to sign the CLA until after you've submitted your code for review and a member has approved it, but you must do it before we can put your code into our codebase. Before you start working on a larger contribution, you should get in touch with us first through the issue tracker with your idea so that we can help out and possibly guide you. Coordinating up front makes it much easier to avoid frustration later on.

Code reviews

All submissions, including submissions by project members, require review. We use Github pull requests for this purpose.

The small print

Contributions made by corporations are covered by a different agreement than the one above, the Software Grant and Corporate Contributor License Agreement.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •