Validating your work before Publishing

Testing your 3D models before you start to author is a critical step in the production process. We recommend validating the model in 3 ways:

• Fidelity - Does the model look the way is should? Is it as accurate? Are there any visual anomalies?
• Functionality - Is the model organized (levels, groups, components) in such a way that it will support animation needs? Is the orientation correct? Is the scale correct?
• Visibility - are all parts or components included? Do their visibility settings support the correct visibility Modes (Stand-Alone vs Device Mode)?

The Project Health window will also help you identify potential issues before publishing.

Additionally keep in mind these recommendations in regards to triangle and node count, to ensure your project is performing well on the end device.

 

Project Health Window

The Project Health window will warn an author when there are potential issues/malconfigured entry fields in the project that might affect the end user experience, both in usability and performance.

The Project Health window will display a warning or error for these occasions:

 

Warning for missing targets

• Camera inset is missing a target camera
  
• Custom Material in Standalone or Device visibility is missing a material
  
• An Object's action is missing a target

 

Warning for performance impact

• An image is attached to a disabled inset
• Total asset size of assets used in a Project exceeds 200MB. In other words, this is the combined size of Assets In Use assets. Additionally the project save file itself can also cause longer load times (eg. with very high amounts of steps), but this is not taken into account for this calculation.
  When a project is packaged for publishing into a scenario, the file size of the .scope file will likely not be the same as the total size of an exported file, as the .scope file can discard information that is needed for a project. As an example, when you import the 3D model of a car, but you delete everything but one wheel in a project, the project will still load the original asset upon load time, as we always want to maintain a connection with the source data, while the packaged scenario upon publish will only contain the wheel.
  As a result, as a user you could go over 200MB in total asset size, as use cases might vary, yet it is an indication you might need to look into optimizing your project.
• Triangle on a step is count over 2 million triangles
• Object/node count on a step is over 5,000 objects/nodes

 

Error messages (failure to publish)

• An AR Object Tracker is missing a a target object
• A step has a graded question, but there is no Quiz Results UI template

 

When your project is healthy, a "Project Health OK checkmark will appear in the bottom toolbar of Create.

If any of the criteria of the Warnings or Errors are met, these will be displayed in the bottom toolbar as well.

When you click on this area, the Project Health window will automatically open to show you the issues.

Hovering over a warning will display the suggested resolution as a tooltip.

Clicking on the warning will open the corresponding step and window, so the author can easily fix the issue.

Once the issue is resolved, the warning or error will be removed from the Project Health window.

Errors will prevent the author from publishing:

Clicking the "View Errors" button will open the Project Health window as well.