Sebastian

`npm i @types/node -D` fixed the errors and I could successfully run `Blender Development` with `Blender 3.1.2`

Btw: I've noticed that my Meshlab version is not able to read `*.mlx` files that are located under `/tmp/...`

Usually it is a good (and common) practice to describe your solution here as a reference for others - and potentially for the gladguy from the future who forgot how...

MVE allows now to import Colmap Models, so you can use [https://github.com/nmoehrle/mvs-texturing](https://github.com/nmoehrle/mvs-texturing) for texturing.

Since `MVS-Texturing ` uses the `MVE workspaces`, I've added the importer of the Colmap workspace directly to MVE (https://github.com/simonfuhrmann/mve). This converts the Colmap workspace to an equivalent MVE workspace. Using...

Note that there is an open [issue ](https://github.com/simonfuhrmann/mve/pull/517) regarding the import of the depth maps. As far as I can tell the problem affects only very special camera models -...

Btw: the bug has been fixed - totally forgot to update this thread

Sorry, I've no experience with unity :/

I'm not sure what you are asking for? OpenSfM (like any other Structure-From-Motion tool) takes a set of input images and computes a set of cameras and a point cloud....

Btw: Reading the data format of opensfm is relatively straight forward, see this [script](https://github.com/SBCV/Blender-Addon-Photogrammetry-Importer/blob/master/photogrammetry_importer/file_handlers/opensfm_json_file_handler.py)