+1 239 999 4122
+1 239 999 4122
Free Download

Knowledge Base

Back to support overview

Spatial Workplace App unable to scan a marker

Here are some pointers in case the Spatial Workplace app is not able to scan your marker:

  • Was the correct marker/QR code number printed/scanned?
  • Workflows played on a HoloLens 2 device need to use QR codes, whereas workflows played on a mobile device (iOS and Android) or HoloLens 1 need to use an ArUco marker. This difference should be checked.
  • All four corners of the marker should be visible to the scanner camera, including the white space around it.
  • The marker should always be flattened, without curls, rips, or wrinkles.
  • Reflective surfaces covering the marker can compromise the tracking (e.g. glass or lamination). It is also not recommended to place the markers over reflective surfaces.

Pins are shown in the incorrect order or not loaded in Workplace

In case the pins are not shown in the correct order or do not appear at all in the Spatial Workplace app:

  • Please check if all connections are in place when creating the workflow. This is required to create the planned workflow order.
  • Besides this, Auto-type connections automatically transits to the next pin which could be misinterpreted as a missing pin. Click over the connections in the 2D connector in Spatial Editor to check their types and ensure this is not the case.

Scene state nodes visibility displaying incorrect parts/assemblies

There are multiple reasons why the visibility feature might seem not working.

Consider the following points:

  1. Did you create a SceneStateNode to make parts/assemblies visible?
  2. Did you use the wrong SceneStateNode type (Interactable, Reset Transform) instead of Visible?
  3. Is the toggle next to Targets visible set correctly?
  4. Have you selected the correct parts/assemblies in this SceneStateNode? If the imported CAD model includes different variants/versions of the same parts or assemblies that have the same name, it could happen that you selected the wrong target part/assembly within the SceneStateNode, leading to hiding or showing different parts than the ones intended.

Holograms are broken

When adding/creating holograms, the selected parts/assemblies are merged and optimized to reduce vertex count and minimize the loading duration within the Spatial Workplace app.

If the optimization breaks the part resulting in holes and wrong shapes of final holograms, please change the optimization quality in the hologram settings in Spatial Editor.

User: "Animation of clicking on the edit button for the hologram on the panel on the right. The hologram settings appear, with the first option being hologram quality. You can click on the dropdown and select between Low, Medium, High or Original quality."

Holograms are flickering or flashing

This flickering effect occurs when at least two 3D parts are overlaying each other at the exact same position.

In order to prevent this Z-fighting, either hide/remove the overlaying parts or move the parts to have different positions.

Inaccurate hand tracking/touching buttons on HoloLens

Consider running the eye calibration on HoloLens again or reset your device.

To recalibrate, you can follow the instructions in the Microsoft HoloLens documentation.

HoloLens field-of-view is cut off

The HoloLens 2 field of view is limited to 43° x 29° by design. This limited field of view might be smaller if the user wears the device in the wrong position.