New forum up and running. 3DF Zephyr will be released next week.
3DF Zephyr forum
Collapse
X
-
Please use this topic to report bugs or request new features.
Known Issues:
- Crash when processing a low number of photos and selecting this combination of parameters in the settings page (sequential or circular ordering AND non-automatic matching details) [Solved, fix in the next release]
- Image Matches discarded occurring with some old Nvidia cards (Cuda capabilities [= 1.2) AND Cuda enabled. [Solved, fix in the next release]
Features in development (to be shipped with the next release):
- Mesh simplification and densification.
- Adding option to link file instead of incorporating them in zep file.
- Adding axis to rendering window.
Comment
-
Full changelog from version 1.001:
- Added post-processing remeshing. When generating a mesh, the desired number of final vertices can now be specified.
- The evaluation version can now be used with any number of images.
- Added the possibility to link image file instead of embedding inside the .zep file. This is useful when dealing with very high resolution images.
- Log files can now be sent to developers when a crash occur.
- Added a warning message when trying to export with the evaluation version.
- Fixed a crash occurring when sequential or circular photo ordering was selected in conjunction with high matching level.
- Fixed a bug occurring with some old Nvidia card during the alignment phase
- Fixed an alignment problem occurring in some degenerate configuration during orthophoto generation.generating orthophoto
- Fixed the extrinsics camera paremeters importing with Euler angles (Omega/Phi/Kappa).
- The distance constraint button now works properly (was locked in some cases).
Comment
-
Hello,
after using zephyr for a while, I must admit the accuracy of the photo alignment phase is very good and it often succeed where other software fails. However it is quite slow. What parameters do you suggest to change to make it run faster? I'm already using cuda. I tried to change the keypoint density so far. Also, do you plan any speed up in future?Comment
-
Hi, thanks for your feedback. As the documentation suggests, if you lower the keypoints density, the matching stage depth, select a hierarchical reconstruction engine and a local bundle adjustment you can speed up the computation. In particular, I suggest to start with the keypoints density to Low and a hierarchical Reconstruction engine and change them only if the reconstruction fails. In addition, remember that if you specify the internal camera parameters in input you can speed up the processing and improve the accuracy.
We plan to implement some improvements in terms of speed in both the structure from motion and the multiview stereo phases. At the moment, we are optimizing the latter one and we think the new version will be ready by the end of the month.
-
-
Hi, thanks for your feedback. As the documentation suggests, if you lower the keypoints density, the matching stage depth, select a hierarchical reconstruction engine and a local bundle adjustment you can speed up the computation. In particular, I suggest to start with the keypoints density to Low and a hierarchical Reconstruction engine and change them only if the reconstruction fails. In addition, remember that if you specify the internal camera parameters in input you can speed up the processing and improve the accuracy.
We plan to implement some improvements in terms of speed in both the structure from motion and the multiview stereo phases. At the moment, we are optimizing the latter one and we think the new version will be ready by the end of the month.
Comment
-
Comment
-
Comment