Hello,

From our experience, there are several factors that can cause an augmentation to be offset, including:

• HoloLens user calibration. MS recommends that each user perform the HoloLens calibration steps before using the device. This is obviously tedious, but when sharing HL devices within a team, we've chased a similar performance 'ghosts' that were resolved when a user calibrated the device for themselves
• The size of your printed targets. For optical see-through devices (such as HoloLens), the printed target must match the dataset's target size exactly, as uploaded to the Target Manager. Recall that the Target Manager works exclusively in the units of meters.
• HoloLens device calibration. All HL devices have some level of factory calibration done before shipment, and we've had to have devices re-calibrated by MS. Although this does not seem to be the source of your issue, it is something to be aware of with HL devices that the factory calibration can be compromised.

You may also want to examine the HL mesh in that area. This can be done by orienting the retical towards the area in question and "air-tapping" while in the HL shell (the home screen without the start menu - no apps running). Perhaps this will reveal some errors in the HL spacial map that are affecting their position estimations.

Thanks,

Vuforia Engine Support