Downloaded ver 30 yesterday, no 3D model visible today

I’ve just tried to produce a 3D model of a tractor, 397 images and 3 hours of processing, but the screen is blank.

Open in a new tab to view full size

No apparent errors in the console log, other than

[WARNING] Negative GSD estimated, this might indicate a flipped Z-axis.


[WARNING] Maximum resolution set to GSD - -100% (6.71 cm / pixel, requested resolution was 5 cm / pixel)

I just used the default 3D settings, perhaps I needed Ignore GSD, as actual sampling distance was more like 1mm?

1 Like

Hit the Zoom to Extent / Zoom All button in the Navigation part of the PoTree control panel on the left there.


Thanks, the tractor has suddenly appeared! I’ve never needed to do that previously, my subject has been visible initially. Is this something that needs to be done due to the latest version update?

It looks like I need to add some more images to fill in holes and remove the ground from under the canopy

1 Like

Yeah, it is a regression that came with a fix we made so that people couldn’t break projects by putitng/removing camera animations.

1 Like

I added more images to try to get rid of some of the holes and incorrectly placed textures, but it crashed after 18 h 36m. Below is the end of the console log from the final successful operations to the crash.
Any ideas on what the problem might be?

2021-08-21 03:33:59,336 DEBUG: Undistorting image DJI_0196.JPG
[INFO] running C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\opensfm\bin\opensfm export_visualsfm --points “C:\WebODM\resources\app\apps\NodeODM\data\1c6d4ea4-5c1d-4199-a35c-fd86238abe83\opensfm”
[INFO] Finished opensfm stage
[INFO] Running openmvs stage
[INFO] running C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\opensfm\bin\opensfm export_openmvs “C:\WebODM\resources\app\apps\NodeODM\data\1c6d4ea4-5c1d-4199-a35c-fd86238abe83\opensfm”
[INFO] Running dense reconstruction. This might take a while.
[INFO] Estimating depthmaps
[INFO] running C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\OpenMVS\DensifyPointCloud “C:\WebODM\resources\app\apps\NodeODM\data\1c6d4ea4-5c1d-4199-a35c-fd86238abe83\opensfm\undistorted\openmvs\scene.mvs” --resolution-level 1 --min-resolution 2736 --max-resolution 5472 --max-threads 16 --number-views-fuse 2 -w “C:\WebODM\resources\app\apps\NodeODM\data\1c6d4ea4-5c1d-4199-a35c-fd86238abe83\opensfm\undistorted\openmvs\depthmaps” -v 0
===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 3221226505
Traceback (most recent call last):
File “C:\WebODM\resources\app\apps\ODM\stages\”, line 89, in execute
File “C:\WebODM\resources\app\apps\ODM\opendm\”, line 340, in run
File “C:\WebODM\resources\app\apps\ODM\opendm\”, line 340, in run
File “C:\WebODM\resources\app\apps\ODM\opendm\”, line 340, in run
[Previous line repeated 1 more time]
File “C:\WebODM\resources\app\apps\ODM\opendm\”, line 321, in run
self.process(self.args, outputs)
File “C:\WebODM\resources\app\apps\ODM\stages\”, line 79, in process’%s “%s” %s’ % (context.omvs_densify_path,
File “C:\WebODM\resources\app\apps\ODM\opendm\”, line 106, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 3221226505

===== Done, human-readable information to follow… =====

[ERROR] The program exited with a strange error code. Please report it at

Did you rerun from load dataset after adding the new images just to see if it will process it all at once?

1 Like

Yes, I started again with loading the full set of images. I’m not sure if the problem occurred due to the extra 150 images being on the next day, but the tractor was not moved, and lighting on the tractor was the same- diffused skylight in the shade of trees a few hours before sunset.

Options: feature-quality: ultra, ignore-gsd: true, mesh-octree-depth: 12, mesh-size: 250000, min-num-features: 9000, orthophoto-resolution: 0.5, pc-geometric: true, pc-quality: ultra, use-3dmesh: true

1 Like

Yeah, maybe it didn’t like that, though it really shouldn’t matter much… Hmm

1 Like

I’ve just set it running again with:

Options ignore-gsd:true, mesh-octree-depth:12, mesh-size:300000, pc-quality:high, use-3dmesh:true

I’m on the side of not adding in ignore-gsd until you know something will process. It is oftentimes the cause of many hard to trace issues and failures.


It completed with those settings, so ignore-gsd wasn’t the problem, taking 4h 16m.
Unfortunately the included bits of background texture incorrectly stuck under the tractor canopy are worse now, plus a whole lot of distant background is included, putting the tractor way off centre, and making it very small in the 3D, so not usable.

Have you run with pc-geometric yet?

1 Like

I’m running it now, with 15 of the images with sky taken out of the data set, although there are some remaining.

1 Like

Even with pc-geometric, sky masking might have to be a thing if you really want to eke out that last bit of precision.

1 Like

I removed all the images with significant areas of sky, and used pc-geometric and pc-rectify, but the problem persists.
The point cloud is fine, but textures are being added in the wrong place.
499 images
Options: mesh-octree-depth: 12, mesh-size: 300000, min-num-features: 10000, pc-geometric: true, pc-quality: high, pc-rectify: true, use-3dmesh: true

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.