Hello,
As part of the XR Lab at the European Space Agency (ESA), we are currently developing an AR application for the use on the ISS. The Magic Leap 2 is particularly useful for us because we can easily access the video and depth cameras. Previous tests with various VR headsets have shown that it is quite challenging to use them in space. In microgravity, the readings from IMUs and magnetometers do not behave the same as they do on Earth. Most XR headsets do not know how to interpret this data and lose tracking.
As a first test for the Magic Leap 2, we tried using it in a car to see what happens when the IMU readings conflict with the camera data. As expected, the headset lost tracking.
We are reaching out to find ways to modify the head pose tracking of the headset. By correcting or disabling IMU readings for the head pose tracking algorithm, it should be possible to get a sufficient result for a moving platform or other extreme conditions. We are aware that the Magic Leap does not support a travel mode, but this is essentially what we need. We could implement this mode ourselves, for example by implementing our own SLAM algorithm in the application. However, when the Magic Leap loses tracking, it shows a warning that blocks all other applications. This makes us suspect that such a tracking algorithm would need to be implemented at the driver or firmware level.
We are aware that this problem is quite niche and complicated. We are willing to implement such a solution ourselves, but we need access to the head pose tracking algorithm of the device (signing an NDA for this is not a problem). Alternatively, we could also provide funding if you are willing to develop a customized solution for us.
Any help on this matter would be highly appreciated.