Difference between revisions of "AndroidAR"
(→Goals) |
|||
Line 33: | Line 33: | ||
[http://tordenoglynild.dk/files/cse298/aar3.jpg] Xoom 2 running the Virtual Reality app | [http://tordenoglynild.dk/files/cse298/aar3.jpg] Xoom 2 running the Virtual Reality app | ||
+ | == Caveats == | ||
+ | The project has not focused on various security aspects that may appear when communicating over an open network. No authentication is done with the mobile phones connected to the tracking server, but at worst, an attacker will be able to flood the server or find an offset location from tracker to our virtual origin in front of the desk computer. | ||
+ | |||
+ | Optimization (more clients than 2) and robust general implementation (the ability to move to other machines. Addresses are hardcoded) has been given a lower priority in favor of features. | ||
== Related work == | == Related work == | ||
Greg is working on doing all the tracking internally in the phone, using all its sensors and the camera(s). | Greg is working on doing all the tracking internally in the phone, using all its sensors and the camera(s). |
Revision as of 12:18, 29 May 2012
Contents |
Introduction
This project uses 2 infrared trackers and a tracking target that is attached to some android device. The data is collected from the trackers by CalVR in the form of a homogeneous 4x4 matrix which is processed by a CalVR plugin that sends packets using UDP to whoever sends a request packet. It is sent as a comma separated string and then unwrapped an parsed on the android device; stripping the position and axis column vectors.
On the android device, we are using the Min3D framework which is based on a scene graph and has excellent wavefront .obj file loading. When you first start the app, you a presented with a screen that allows you to choose which model you want shown. After picking a model, it should appear on the screen along with some information text in the upper left hand corner. Pressing the context menu button and then "Start tracking" will enable the tracking feature and continuously update the camera of the scene graph based on what we receive from the CalVR plugin.
Goals
Rendering on Android (done)
Camera tracking (done)
Head tracking (done)
Interactivity on device (in progress)
Rendering in Cave and device
Rendering in Cave and stream to device
Developers
Pictures
[1] Mads holding the final tablet and tracking the chair
[2] Xoom 2 running the Virtual Reality app with IR Tracking
[3] Xoom 2 running the Virtual Reality app
Caveats
The project has not focused on various security aspects that may appear when communicating over an open network. No authentication is done with the mobile phones connected to the tracking server, but at worst, an attacker will be able to flood the server or find an offset location from tracker to our virtual origin in front of the desk computer.
Optimization (more clients than 2) and robust general implementation (the ability to move to other machines. Addresses are hardcoded) has been given a lower priority in favor of features.
Related work
Greg is working on doing all the tracking internally in the phone, using all its sensors and the camera(s).