FAQ

Best Practice: How do we overlay Point Clouds and Models?

This question and answer does not just apply to Vrex.

  • Best practice is to get your scanning team or consultants to deliver point-cloud files already align with your 3D model. They have the tools to do accurate alignment for both position and rotation.
  • Next best alternative is to get the same tools yourself, such as the point-cloud alignment tools from Faro or Leica.
  • If the above is not possible, then it is possible to do it inside the CAD tools and Vrex, although this is the least accurate method.

First check if point cloud has the correct orientation, if not the third option is not possible.

**How to offset model and point-cloud using your CAD tools.
**Navisworks is used as an example in the text below.

  1. Locate a reference point in the model and point-cloud that you know is accurate.
    E.g. preferably something small, like the corner of a structural column.
  2. Use “point-measuring” in Vrex, Navisworks, or Recap to collect the XYZ-coordinates from the reference corner in the model and point-cloud.
  3. In Navisworks choose offset and input the difference in the XYZ coordinates between the reference point the model and point-cloud.

Use this formula to find the offset value to offset the model.

XYZ of the point cloud [e.g. 123, 123, -123]
- XYZ of the Model [e.g. 1, -2, -3]
= XYZ offset of the Model [e.g. 124, 125, -120]

Note: Vrex will soon have an offset feature, however, it is still recommended to save this in project files, and not within each tool separately.

How large data-sizes can Vrex handle?

We recently had an upgrade that increased capacity by 1600%. The next upgrade will allow Vrex to handle nearly unlimited data, and fast access without downloading data. This will give a very responsive user experience. By choosing your starting location Vrex will populate the areas you move through with details. ETA: Rollout begins Q1 2025.

We have some features to overcome these short term data size limits

Data Processing via the Vrex Admin Website: Upload limits are 5GB per file, but you can have 100s of files. This is to have files suitable for collaboration, without preloading 100GB before a session.

Vrex in use via Streaming: No limits, as the Innoactive server can be increased accordingly. (increasing capacity may change Innoactive pricing.)

Vrex in use via Desktop app:  Limited by your computer’s GB memory.

Note that file sizes are misleading, as 1 million similar pipes will have small files yet be heavy in VR, so consider this a guideline.

Best practices: How to optimize Point Clouds in Autodesk Recap?

Step 1 - Set resolution to 10mm.
https://academy.vrex.no/knowledge-base/optimize-point-clouds-for-vrex-use-with-recap/

Step 2 - Define regions, and export E57s without “3D data only”, which removes 360 photos that often takes 50% of the size.
https://academy.vrex.no/knowledge-base/auto-export-scan-regions-recap-to-vrex/

Step 3 - Inside Vrex, use this feature to increase point-cloud resolution
Feature is found in VR, under the point-cloud list, as shown below.

Best practices: How to optimize Models with Vrex Model Decimation?

“Model Decimation” is found under project-settings (app.vrex.no).

This adjusts the level of detail for your project. Low values retain details, while higher values simplifies the model to enable processing or improve performance. It also helps with keeping a uniform LOD level across the project.

If your 3D-model processing fails it can be caused by what is often called “LOD 1000”. It refers to vendor-models that contains objects with excessive detail. E.g. nuts/bolts with inside threading inside, or charcoal bricks with millions of 3D-points. Both has been observed in your projects. - Model Decimation can help with this.

**Guide to setting values, if your project fails processing
**“1.0” excludes excessive details, and is generally a good value for most complex projects.
“5.0” excludes details typically not needed for virtual walkthroughs, e.g. sprinklerheads.
“15.0” excludes more details and enables walkthroughs in vast models, such as full shis or plants.

The optimal value varies between projects, so please contact support@vrex.no for help with calculating the optimal values for your project, if you cannot get it to work right. They have a calculator for doing quicker experimentation.

How to fix low latency when Streaming Point Clouds?

VR streaming services are sensitive to visual noise, so the noise found in point-clouds caused by light reflections, etc. can cause lagging.

To fix this, use the “Point Cloud Noise Reduction” found under project settings (app.vrex.no).

It evens out the color-variation in your point-cloud, and helps the Streaming service maintain low latency. Supported formats: Can NWD / NWC files contain Point Clouds?

Yes. - Vrex reads point clouds from NWD/NWC files, or via the Navisworks plugin.

However large projects + large point-clouds produces huge NWD/NWC files. So for large projects it is best to ignore this for now, it becomes more relevant next year.

Supported formats: Is LAS / LAZ files supported?

Not currently. Because file-handling is needed to offset and optimization point clouds, the best workflow is to do this process on the LAS/Z files, then at the last step simply save the result as an E57 file.

At a later point, when file-handling is no longer needed, then LAS support is a natural next step.

Supported formats: What formats are supported?

  • openBIM IFC files
  • openBIM BCF issues
  • BCF rest API for issue integrations
  • Autodesk Revit files
  • Autodesk Navisworks files, with all 60+ formats it supports
  • Siemens JT files
  • E57 Point-Cloud files