Known Verity Issues & Tips

      Comments Off on Known Verity Issues & Tips

Search Knowledge Base by Keyword

You are here:
← All Topics
Table of Contents

Getting Started

This article will cover known Verity issues, as well as some tips and best practices. If the Verity issue you are experiencing is not listed below, please contact ClearEdge3D support at the following email address:

  • To maintain the link between Verity items and elements in Autodesk® Navisworks®, you must save the Autodesk® Navisworks® project after adding the items to Verity and before closing Autodesk® Navisworks®. Verity is a database and saves on every operation, but Autodesk® Navisworks® is not and must be saved to retain the data pushed into it.
  • Verity does not support working on files on network storage. Working with files on a network storage device can cause extremely slow performance. Please store all working files locally.
  • One of the most common known Verity issues is that Verity does not support using unified scan data, but there is no way to prevent you from doing so. If you add unstructured scan data, Verity will attempt to process it and will load the entire scan into memory. With a large unified scan, this may cause your computer to run out of memory, crashing Verity and Autodesk® Navisworks®. If it completes, the fitting results will be highly compromised. A high percentage of bad fits in your data indicate unstructured scan data.
  • When using the Add to Verity (Selected Node) option, Verity brings in your selection at the exact level you have picked it in the selection tree. So, if you select the entire architectural model in the selection tree, Verity will attempt to load it in as a single item in Verity. This will, at the least, take a very long time, and may cause your computer to crash if it runs out of memory.
  • Verity’s process is running inside Autodesk® Navisworks®, so occasionally, Navisworks® will take operating system focus from Verity, and you’ll have to manually re-focus on Verity to see the Verity console or the progress bars.
  • Calculating three-dimensional rotations is a complicated procedure as there are multiple ways to calculate it. Additionally, if Verity has incorrectly identified the long axis, then these calculations will not likely be relevant. This may happen in the case of beams with lengths shorter than their depth as an example. Please refer to the “Rotation Metrics” section in the user guide for specifics.
  • Occasionally, locking the Push Properties to Host or Push As-Built Position to Host buttons will cause Verity to Auto-Zoom to the currently selected items even when Auto-Zoom isn’t checked.
Was this article helpful?
4.5 out of 5 stars
5 Stars 0%
4 Stars 100%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Need help?
Previous License Troubleshooting
Next “Please Connect to the Internet” Error