Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Work of magic Leap development libraries for unity misunderstanding

Discussion in 'AR/VR (XR) Discussion' started by TwighlightSparkle, May 22, 2020.

  1. TwighlightSparkle

    TwighlightSparkle

    Joined:
    Mar 4, 2016
    Posts:
    5
    Hello, i had been analysing existing Unity ML dev libraries to take solid understanding of how does it work and for finding out what certain one of it need i for my purposes. I find following libraires: Magic Leap XR Plugin, MagicLeap.package from magic leap official site. At first i try to make ML app only with Magic Leap XR plugin, but there was very poor functionality only with it. And i download MagicLeap.package from ML off. site. I thought this AR-foundation/Interaction toolkit - level library will use data handling functionality of XR.MagicLeap plugin (provider) without any low level calls, but I find two type of "lowest level" calls in code in both libs:
    1. Dll import at first screenshot (from Magic Leap XR plugin code)
    It is lowest level input (as i understand)
    Скриншот 22-05-2020 164802.png
    2. And standart unity calls from Unity.XR (from MagicLeap.package code)
    Скриншот 22-05-2020 162855.png
    Why there are second types call? Doesn't it only Unity XR Plugin responsibility? And why does Unity XR plugin is required for MagicLeap.package from ML off-site if that package handles device low level data by himself? Don't i understand something? Or it is bad software design with a lot of dependencies?
    And more. I cannot start zero iteration mode without MagicLeap.package from off site. Why that package required for zero iteration mode using?
    xrff_class_hierarchy.png
     
    Last edited: May 22, 2020