I’ve been working with the Estimote Unity Plugin for a project and it seems that the documentation is a bit limited. I’ve also looked through various discussions, posts, the Android Estimote SDK docs, etc. Thus I’m hoping others can confirm what I’ve found.
Mapping in Unity:
When building out the scene in Unity, the orientation of the map should match the orientation of the map in Estimote cloud.
0,0 is the bottom leftmost corner of the map as depicted in the Location map in Estimote Cloud.
The x,y coordinates gotten from the IndoorLocationManager is equivalent to the Unity x,z distance from 0,0 in meters.
If the Unity scene is setup where 1 unit = 1 meter then moving the user is done by setting the User’s location x and location z to the IndoorLocationManager x,y.
Can anyone confirm these things?
With those things in mind, I’m having serious issues with any consistency. Even when seated at my desk, the IndoorLocationManager x,y values are bouncing all over the place. I also can’t seem to get any consistent movement in any direction. I can walk one direction and see the avatar in my app move then I can walk directly back to where I started and the avatar walks in an entirely different direction. Sometimes I’ll walk several meters and the IndoorLocationManager x,y reflect only minimal change.
I’m also wondering how the algorithms work because I can be standing directly in front a beacon (i.e. <.5m) and the indoorLocationManager doesn’t recognize that and places me at an x,y somewhere else.
Perhaps there is something I’m doing incorrectly but some of these things shouldn’t be due to user error (such as if I walk 3 meters in one direction and then return to my original position, the IndoorLocationManager should reflect that regardless of scale, unity scene orientation, etc.). I’ve tried looking online, in forums, etc. but I can’t find a whole lot.
Thanks in advance for any sage advice you might have for me.