photogrammetry | A python notebook using Meshroom | Data Manipulation library

So to get around this first make your app has permission to access the users camera(go to Info.plist or info tab beside the build settings at the top and add Privacy camera usage and add "We need your camera to perform this action")

After that a simple call in the sheet's modifier should do the trick

tl;dr: Try another set of images, probably there is something wrong with your set of images.

I've had it work successfully except in one instance, and I received the same error that you are getting. I think for some reason it didn't like the set of photos I took for that particular object. You could try taking just a few photos of another simple object and try again and see if that is the problem with your first run.

The reason for the problem with these files is the large offset combined with 32-bit float values. In this case the objects all use the same geographic origin, probably at a lat/long of 0.000N/0.000E

Nearly all 3D graphics programs use 32-bit floating point values to store each points location, and the combination of the offset and the 32-bit value causes some of the precision to be lost. 32-bit floats have about 7 decimal digits of precision, so the offset of 4460688 in the example file completely dominates, and effectively cuts the model from 1mm resolution to 1m resolution data. The reason for the long triangles is that there is more data lost in one direction due to the asymmetry of the offset.

The solution is to apply some offset to bring the objects close to the origin BEFORE importing them with the 3D software. I wrote a quick python script that can help with this: https://gitlab.umich.edu/lsa-ts-rsp/xr-shiftOBJ/-/blob/main/shiftOBJ.py

Unfortunately there's no official way of customizing the environment: How to add custom environment map for background in autodesk forge?.

I think you could hack your way out of this, though, for example, by switching to one of the "simpler" environment presets, and finding an angle where the photogrammetry output is lit reasonably well:

I think that your link is trimmed (perhaps by your application).

I just runned a scene and compared my results with your link and note the difference:

yours:

The Answer to this was simply that the color display was distorted in ArcMap. The calculations were right, however it generated som extreme values which shifted the color scheme stretch. This created a big black/grey square. To fix the problem quickly, one can mask out the outliers using Raster calculator. Allthough, in the long run it's of course better to investigate why these outliers occur. I did not get that far with this project.