﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Vuzix Forums / VR920 / Tracking  / 1200VR: Has anyone been able to make sense out of the X-Y-Z data the 6TC produces? / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>Vuzix Forums</description><link>http://forums.vuzix.com/</link><webMaster>forums@vuzix.us.com</webMaster><lastBuildDate>Fri, 18 May 2012 07:32:56 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: 1200VR: Has anyone been able to make sense out of the X-Y-Z data the 6TC produces?</title><link>http://forums.vuzix.com/Topic6577-8-1.aspx</link><description>I must say I am a bit unhappy with my Wrap920VR.  I want to write my own VR app, and was hoping on at least semi-decent 6DOF functionality from the 6TC tracker, as advertised.  At the moment I am stuck with 3DOF...&lt;br&gt;What I don't understand about the 6TC is that, when you don't have a software interface for head translation, then how can you claim it to be 6DOF in your marketing, since then you should have the software to make it run, but thats "in beta".  Have the engineers at Vuzix ever had translation working, and if so, then why so long before it filters through into the SDK?&lt;br&gt;Whatever, I hope for the best and maybe some Vuzix spokesperson can confirm 6DOF support being on the horizon, and maybe something about the timeframe this is going to happen within, since I'll need 6DOF for my app really soon?&lt;br&gt;&lt;br&gt;Greets,&lt;br&gt;Gert</description><pubDate>Fri, 27 Apr 2012 05:02:33 GMT</pubDate><dc:creator>paleajed</dc:creator></item><item><title>RE: 1200VR: Has anyone been able to make sense out of the X-Y-Z data the 6TC produces?</title><link>http://forums.vuzix.com/Topic6577-8-1.aspx</link><description>Position data is still in a developmental stage and is not accurate enough to track more precisely than general motion.  For instance, you might be able to read when a user moves their head quickly to the left, but you wouldn't be able to tell precisely where their head now is.&lt;br&gt;&lt;br&gt;The examples provided in the SDK are only built in VS2008.  We are currently updating these workspaces to build in VS2010, which should hopefully alleviate the build issues you are seeing.</description><pubDate>Thu, 02 Feb 2012 13:31:08 GMT</pubDate><dc:creator>Starnerf</dc:creator></item><item><title>1200VR: Has anyone been able to make sense out of the X-Y-Z data the 6TC produces?</title><link>http://forums.vuzix.com/Topic6577-8-1.aspx</link><description>Hello,&lt;br&gt;&lt;br&gt;I've been trying to make sense out of the X-Y-Z data that the 6TC offers, to no avail. I am able to convert the yaw, pitch and roll into degrees following the documentation to SDK, but there is nothing in there that touches on the xtrn, ytrn, and ztrn data. I was wondering if anyone has been able to convert it into real world values, or if there have been any releases that support the full potential of the 6TC.&lt;br&gt;&lt;br&gt;On another note, I am having trouble editing the HelloTracker3 project in Visual Studio 2010. It says that it was created with an older version of visual studio and then it converts it. Once that happens, if i try to edit the code in anyway I get an error and weird code errors for anything I type. For example, for: &lt;br&gt;&lt;br&gt;float degrees_yaw;&lt;br&gt;degrees_yaw = yaw;&lt;br&gt;&lt;br&gt;It underlines the "t" in float in red and says that "t" is an unknown identifier. Its like visual studio isn't reading the code correct for some reason. &lt;br&gt;&lt;br&gt;I'm trying to edit the HelloTracker in order to save the coordinates into a spreadsheet file every ~20ms in order to compare to the head tracking capabilities of the Kinect. I haven't written in C++ in awhile and that file I/O is a whole other problem.&lt;br&gt;&lt;br&gt;Any insight into any of my problems would be appreciated.&lt;br&gt;&lt;br&gt;</description><pubDate>Fri, 27 Jan 2012 13:40:37 GMT</pubDate><dc:creator>ryman714</dc:creator></item></channel></rss>
