If the NVM file contains features with invalid number of refs, mvs-texturing fails with
terminate called after throwing an instance of 'util::Exception'
what(): Invalid number of feature refs: 1
as it uses MVE, which crashes when it sees features only seen by a single camera (https://github.com/simonfuhrmann/mve/blob/d4bc2ee02a6b57130751c012a8893b3bd4d6540c/libs/mve/bundle_io.cc#L190). Since this is not a problem for mvs-texturing, one can simply filter out the invalid features from the NVM file and the texturing works.
Not sure how to go about solving this issue, though, as it's on the MVE side - perhaps a flag to not fail on feature errors while loading the file?
If the NVM file contains features with invalid number of refs,
mvs-texturingfails withas it uses MVE, which crashes when it sees features only seen by a single camera (https://github.com/simonfuhrmann/mve/blob/d4bc2ee02a6b57130751c012a8893b3bd4d6540c/libs/mve/bundle_io.cc#L190). Since this is not a problem for
mvs-texturing, one can simply filter out the invalid features from the NVM file and the texturing works.Not sure how to go about solving this issue, though, as it's on the MVE side - perhaps a flag to not fail on feature errors while loading the file?