search
M-XR

Common Issues

Common Issues can be found below.

Find here a list of common issues people encounter and how to resolve them. Error messages are shown below, if your error message matches up to any below, please see the resolution. If the issue persists, reach out to [email protected]envelope.

hashtag
Issue - RC or Agisoft Alembic Export Error: 

[ERROR  ] module 2/5 process.pipeline.transform.gl_uv_reprojection failed: 
RESULT: 1
OUTPUT: 
Pinged your deployment! You successfully connected to MongoDB!
STDERR: 
[tid:  15252][W] Logging to '%LOCALAPPDATA%\M-XR\Maestro\Logging\gl-uv-reprojection\gl-uv-reprojection_20250205-025816.log', use argument --print to log to console
[tid:  15252][C] Cannot extract a number from: 00011.png

hashtag
Resolution:

This is usually something to do with your export settings in your photogrammetry software, please follow our export configurationarrow-up-right if using Reality Capture or this Agisoft page in our docs.

hashtag
Issue:

Prepared JPEG Data for photogrammetry looks high contrast.

hashtag
Resolution:

Currently for the jpeg based workflow brightness control is the only setting offered.

You can use the EXR workflow and edit the contents of the EXR (brightness, contrast, LUT, color space, tone mapping). However it is extremely important the filename, resolution, aspect ratio and orientation are preserved exactly.

We don't use the pixel values in the photogrammetry images so you are free to adjust them in any way to help your photogrammetry.

hashtag
Issue - Connection to database:

hashtag
Resolution:

This is quite likely an antivirus/security software blocking access. You may also see the Windows Security Smart Card pop up at this point. Please see this page and follow the necessary steps to solve the issue.

hashtag
Issue:

IIQ images not working for exposure calibration.

hashtag
Resolution:

We are working on a resolution for this.

hashtag
Error:

[C] CheckGLR: No models in scene for contributing to memory calculation!

hashtag
Resolution:

This likely means there was no mesh exported in the alembic file, be sure to re-export with the correct settings from your chosen photogrammetry software. You can find the export settings for Reality Capture under the photogrammetry page in our docs.

hashtag
Error:

[W] Cannot find source photo in source directory

hashtag
Resolution:

This quite likely means that your RAW image dataset has been moved or deleted. In the Marso Measure process step, the software will look for your RAW files in the same path you configured in the develop step, so be sure to keep the folder in the same location and do not delete it.

hashtag
Error:

[C] Fatal Error: Mesh polycount and size of textures exceeds available VRAM! Possible fix is reduce polycount by: 0

hashtag
Resolution:

This is quite likely to Marso Measure not fully utilising the GPU on your system, to fix this please do the following:

  1. Go to Settings → System → Display

  2. Scroll → Graphics

  3. Add the Marso Measure app:

    • Desktop app → Browse → select the .exe

  4. Click the app → Options

  5. Set to:

  6. Save and restart the app.

triangle-exclamation

Please note, to run Marso Measures Gen 2.0 model, you need an Nvidia GPU.

hashtag
Error:

Fatal Error: There are more frames in the scene than frames in the scan: 195 > 5

hashtag
Resolution:

This means there is a mismatch between the camera count in your alembic file and the amount of images in your RAW image dataset when the job was created, these need to match up for Marso Measure to be able to process further.

hashtag
Error:

The system cannot find the path specified.

hashtag
Resolution:

This quite likely means that your dataset has been moved or deleted. In the Marso Measure process step, the software will look for your files in the same path you configured in the develop step, so be sure to keep the folder in the same location and do not delete it.

hashtag
Error:

[W] metadata key 'ExposureTime' values differ: 1/160 =/= 1/250

hashtag
Resolution:

This means that your shutter speeds do not match up, either in your RAW scan or between your calibration image you used when creating your exposure system and your RAW scan.

Marso Measure requires identical manual camera settings in your RAW scan and your calibration image.

hashtag
Error:

[C] Cannot extract a number from: 00xxx.png

hashtag
Resolution:

This is usually something to do with your export settings in your photogrammetry software, please follow our export configurationarrow-up-right if using Reality Capture or this Agisoftarrow-up-right page in our docs.

hashtag
Error:

[ERROR ] Cannot start Marso Processing Server on port 18070, already in use.

hashtag
Resolution:

Check if a version of Marso Processing Server is is already running via Task Manager on your machine, if so terminate it. If the issue persists, please open a ticket via the button below.

hashtag
Error:

Fatal Error: Uncaught ImportError: Error importing numpy: you should not try to import numpy from its source directory; please exit the numpy source tree, and relaunch your python interpreter from there.

hashtag
Resolution:

There is a python virtual environment on your system interfering with Marso Measure, please clear it.

hashtag
Error:

EXR file(s) have dimensions that don't match the camera settings.

hashtag
Resolution:

This is quite likely an issue with your export of the ST maps from either Agisoft or Reality Capture, see the correct settings here.

hashtag
Error:

Error invoking remote method 'alembic:open-file': IpcError: IPC_MESSAGE_START:Error opening alembic file: RangeError: Array buffer allocation failed

hashtag
Resolution:

Marso Measure is unable to preview the alembic information in the UI, you can still proceed.

Get Support

PreviousMarso Measure Processing OptionsNextContact Support

Last updated