Table mounted version PT II


Just a short update post today :)

 Note:
I'm not sure if what I've done today is correct but this is the path that I went down that seems to be working.

So because I couldn't work out how to change the origin point (set (0,0,0) to a specific point in the real world) I used the HMD to chose a point. I did this by putting the HMD in a specific point in the real world and checking the position of the center eye camera. Not sure if the centre eye camera is the best one to use though as I'm not sure where exactly on the HMD it was located. Anyway as a starting point I went with this and took the position  as (0,-0.4,0.24). Using this I attempted to account for the location of the camera by subtracting half of the HMD height which left me with a real world position (x marked on my desk) and it's Unity coordinates.

Using this point I measured the position of the sensor away from the point and placed a gameobject representation of the sensor in the scene. The main issue with this is that it's still not perfectly accurate. It looks a lot better than the original version however the small amount of guess work involve with the camera means it won't ever be fully accurate.

Also I realized why my original idea of using the OVRManager Tracker.getPose() method wasn't performing as expected. This was because it wasn't returning the coordinate in Unity space rather it was returning the position in relation to the last centered position of the HMD. So for example if GetPose returned the vector (0.2, -0.1, 0.1) it means that the sensor is 20cm to the right, 10 cm below and 10cm behind the headset rather than the actual position. A potential direction to take this in would be to get the position of the HMD at runtime and add the pose returned from the method to it to find the real time sensor position in Unity space.




Current Scene
I have two black tape lines running down the 1m mark  (measured from the edge of the table) and the 0.5m mark. Both the leap and sensor are centered on the 0.5m line, and the leap motion is mounted 0.5m in front of the sensor.

  • 0.5m line:
    • x =  0.06
    • y = -0.445
  • 1m line:
    • x = -0.44
    • y = -0.445
  • Sensor (Top middle point):
    • x =  0.06
    • y = -0.185
    • z =  0. 74
  • Leap (origin of leap, middle)
    • x = 0.06
    • y = -0.42
    • z = 0.24




Comments

Post a Comment

Popular posts from this blog

Texturing Hands

Image
Texturing the 3D Hands The purpose of texturing the box was so that eventually I could move on to texturing realistic hands.  The first issue I had was that Leap Motion export their prefabs in the ASCII format of .fbx (i'm guessing because it's human readable?) and Blender doesn't allow importing of ASCII file so I had to convert to a Binary file using an external application.  After importing it into Blender I realized there was something called Armature which I hadn't heard of before and as I started reading I figured it would help to look a little bit into how animation works so I could understand the Leap Motion documentation a little bit better. Leap Motion uses something called Skeletal Animation for their hand prefabs. When using this method we split the character object (in this case hands) into two parts, the skin/mesh and the interconnected bones/rig. The bones are connected in a hierarchy so that when you move for example the tip of the fin...
Read more

Day 2

Image
Sam's Demo To start today, as per Holger's request I captured an admittedly very amateur screen cast of Sam's Demo. I wasn't quite sure how to best show the different functions of the program. After a few failures this was the best I could come up with: Will have to add video capturing skills to the list of things that will (hopefully) improve throughout the duration of this student ship. I'm not sure how to get four hands up and going currently. Creating a trial leap hands project Today I decided to start by attempting to create a basic program that could render two hands as an attempt to get my head around the software a little bit.  I first downloaded a bunch of stuff: Leap Orion (The SDK for leap) Leap Core Assets (Package with basic functionality) Leap Graphic Renderer (Aims to create a system that allows you to to treat a collection of objects as a group) I followed a set up tutorial found here: https://developer.leapmotion.com/do...
Read more

5th of Dec Update

Image
Haven't updated in a while because I haven't really made any major achievements, everything has been very gradual in growing my understanding with the Leap API as well as how Sam's demo actually works. I've been focusing the last few days on how Leap works, from how to access any leap data within a script to detecting hands using the HandModels[] from the current Frame. I had a slight play around with the concept of four hands simply by duplicating the LeapController and HandModels twice over and position them in a way as to replicate four hands. Movement is that where both the left hand controls both hands on the left side and vice versa with the right. This was a good way to visualise the task and see the gaps in why this technique wouldn't work. My current challenge is to replicate the mirroring from Sam's demo. Now that I understand the code better I can see that the way that Sam has implemented it is no longer possible with the new Orion API. He mir...
Read more