Could you please remake the zip including your packages folder to make sure we're getting the correct packages on our end?
Zip should have Assets, Project Settings, and Packages.
Could you please remake the zip including your packages folder to make sure we're getting the correct packages on our end?
Zip should have Assets, Project Settings, and Packages.
When using the Size Estimation feature, you need to around for the marker to become detected. For example, I used this website and set the Aruco Marker to Dictonary 5x5 and marker to ID 100.
Then I used the marker tracker script. The size will report zero at first, but then move your head left to right, sweeping across the marker back and forth.
As you move, the headset triangulates your movement and the estimated position of the marker to estimate the marker's size.
You can disable EstimateArucoLength on the marker detector if you want the detector to initialize more quickly.
I also noticed that in the script above, you are trying to use MarkerFeature.UpdateMarkerDetectors() even before MarkerFeature; is assigned. I recommend adding a null check.
if(MarkerFeature == null)
return;
MarkerFeature.UpdateMarkerDetectors();
Size Estimation seems to be what was causing the issue. I'll have to try in my main project sometime tomorrow to fully confirm, but in my minimal project with just the marker tracking, it works.
However, it does still return a zeroed out pose for me when it initially detects a marker, but then it returns the correct pose on the next frame, so that's something to keep in mind.

Unfortunately the Packages folder is several GB which is why I omitted it. The project is the Magicleap examples 2.2.0 project that can be acquired with packages from the hub. You can see the scene I used my unzipping and including the attached unitypackage, but it is just the script from above. If you are getting those size estimation issues in logcat though make sure size estimation is set false _detectorSettings.AprilTagSettings.EstimateAprilTagLength = false;
Also you may want to make the adjustment that @kbabilinski said in order to not get null refs before the feature is found
markertracking_custom_scene.zip (13.6 KB)
Like @chaseryals219 I was unable to get marker tracking to work with estimation enabled, but disabling it seems to have solved my issues and allows me to progress with my project. Thanks