I have an issue in an app that I am working on.
The controller tracking seems inconsistent, and degrades over time/distance. Moving from room to room will cause the ray to drift from the actual controller, if the controller loses tracking, or goes to sleep, during this degraded performance it can become stuck without tracking. Additionally during this degraded performance returning to the home screen will also show the degraded performance. This seems to be somewhat mitigated by returning to either the original room, or upon repeatedly going to the new location (the first time I go to a room this is more likely to occur, but less likely on subsequent times).
There doesnt seem to be an error, the controller ray simply goes back to origin.
controller is setup as per default magic leap rig with some additions.
During a tracking loss event the buttons will continue to read, and going back to the menu seems to show some interaction profile thrashing in the systemui
I am also getting a lot of NovaInputService input_event_manager.cpp:507: App (pid=4550, uid=4023) registered more than one handler for the same event.
Hi Sidney. I hope all is well. We're so glad that you're here with us.
Regarding the controller tracking degradation, I would try looking directly at the controller periodically to see if that helps with regaining tracking. I would also like to ask about the lighting in your real world environment.
If this method fails, would you mind sharing a video of the controller tracking at the start of your application and during the tracking degradation phase.
@etucker I have done some additional tests. I tried mapping my whole area in spaces, which did not improve things. I also tried building with hand tracking disabled in the app, which did not improve things. I also tried building with reduced scene complexity and did not see any meaningful changes. I was also able to reproduce the problem in an area with more uniform lighting, but it was more difficult. (the problem is inconsistent to begin with though)
@etucker further findings
the general pattern I am getting is that controller will work fine. I will leave the origin by ~10 ft and the ray will begin to drift from controller origin. I will continue to use the controller and it will start either sticking in place but continuing to rotate, or it will briefly snap back to origin and unresponsive. then after some time, generally continuing to move around, it will snap back to origin and stop tracking altogether, after which it is unrecoverable
going through challenging lighting conditions, or intentionally losing tracking seems to speed up the process
the thing I find really interesting is that the offset or loss of tracking propagates back up to the system menu
Are you using the pixel sensor at all? We are investigating an issue that may be causing the controller to not regain tracking after looking at it due to the pixel sensor.
Would you mind trying this in the examples project with and without the pixel sensor?
