Known issues
- Duncan Baird
- Rhys Howell
- Nathan Dunne
Current
Spaces in paths
Currently having spaces in paths is not supported. So most steps will fail if a path includes a space. This covers calibration and processing. As a solution for the time being it is recommended to move the data to a location where there are no spaces in the path.
Run out of storage
If the program is running and the drive that the sctrach directory is set to use fills up (due to Marso or other programs) then windows will throw a Storage Warning, the job in Marso will fail.
If the scratch directory is set to the C: drive, (and the disk is now full) the program will not be able to be launched
To resolve you must clear space on the drive, usually we aim for 250GB of free space. Then the program can be relaunched and job can be restarted safely.
Windows defender false positive
Windows defender has an AI based threat detection system that on some systems detects a portion of Marso as a threat. The threat should look like Trojan:Script/Wacatac.B!ml
To resolve, you will need to add an exception on this path %LOCALAPPDATA%/M-XR/Maestro/Unpack
If you are unable to add an exception due to security policy then we don’t currently have a solution.
Firewall blocked
If you have your firewall blocked and set not allow any connections then Marso will crash and will not provide a clear error. Marso requires external internet connection to run in order to connect to our DRM system.
To resolve, add a whitelist to your firewall for the Marso program and any program in this directory %LOCALAPPDATA%/M-XR/Maestro/Unpack
You may also need to add exclusions for the endpoints Marso needs to connect to:
https://api.keygen.sh/* - HTTP/HTTPS (80/443) - License validation
*.mongodb.net - TCP ports 27015-27017 - Database
*.backblazeb2.com - HTTP/HTTPS (80/443) - Binary hostingVPN support
Currently based on our testing, Marso does not work with VPNs. They can tried at the user’s own risk but we do not expect them to work.
Historic
Default type filter for ST Map explorer window
Reality capture is the default photogrammetry software selected when opening the configure dialog on a new unconfigured job. If you try and select the ST map with the button through the subsequent explorer window, the program will only allow you to select a file, it shoud only be allowing a folder.
To work around this, in the Photogrammetry Software dropdown, select Agisoft and then reselect Reality Capture. This will force the interface to reset the filter in the explorer window when you open it to select the ST map.
Portrait Calibration
Calibrating with camera orientated portrait will result in landscape photogrammetry images that repeat the subject.
The calibration should be done in landscape to correct this issue. If the light offset was relative to the camera in portrait orientation, this will also need to be recreated to match the new calibration orientation. Scan images can then be taken in portrait and they should be rotated to landscape by Marso. The photogrammetry solve should then rotate the camera object back to portrait.
If you have an existing scan with this issue it will need to be re-created in Marso with the horizontal calibration and new light system selected.
GUI not displaying error
In a small set of circumstances with the prepare step when it errors the GUI is unable to report the error back to the user as it would normally. It will just show the job in the FAILED PREP state. To get around this look into %LOCALAPPDATA%/M-XR\Maestro\Logging\Job_Manager_GUI for the error details.
License Key Activation Failure
Fixed: 24.4.2
If you are activating a license for the first time on a machine you may see the following error even if your license is valid.
To confirm that this error is invalid, check the most recent log file in
%LOCALAPPDATA%/M-XR/Maestro/Logging/Job_Manager_GUI/
If you see line similar to the below then your license may in fact be valid, and you should try following workaround.
[ERROR ] not enough values to unpack (expected 3, got 2)Workaround
Close Marso if you still have it open.
In a text editor open
%LOCALAPPDATA%/M-XR/Maestro/config.jsonInsert your license key in quotation marks like so:
Restart Marso
You should find that your license key is already populated in the settings dialog, and activating now works correctly if your license is in fact valid.
Update Failure
Fixed: 24.4.1
The Updater shipped with Marso in versions up until 24.4.1 has been disabled as of the 20th of September 2024 due to an access key rotation. If you are unable to update from a version before 24.4.1 you may need to re-download the Updater executable (M-XR_Marso_Update.exe) from here and replace the update executable in your install directory.
You should then be able to launch Marso and have it update correctly.
Normals Texture Files
Fixed 24.4.0
The colour space on the Normals for PNG and JPEG outputs is not correct. Normally the should be in raw/linear and not need an input transformation, there is an issue with the file authoring that is encoding them as sRGB. To resolve, adjust the input transformation in your program of choice to treat them as sRGB.
Light System Menu Crash
Fixed 24.4.0
When the menu is in this state, i.e. you have any number of rows in the New Light System frame, if you click on a row in this frame then the program will crash. Any data currently entered for a light system you are creating will be lost. No saved light system data will be impacted. If you are running a job and this crash occurs Marso will attempt to recover at next startup but progress for that job may be lost.