Describe the bug
No ‘scene.mvs’ file generated when running InterfacePolycam use parameter " -o SAVE/PATH/scene.mvs ".
if don't use parameter " -o ", it will save ‘scene.mvs’ file successfully in current folder.
To Reproduce
Steps to reproduce the behavior:
- prepare polycam raw datas
- running
InterfacePolycam -i polycam/ -o scene.mvs
.dmap could be generated, but NO ‘scene.mvs’ file
Expected behavior
Generate ‘scene.mvs’
Additional context
I noticed that apps/InterfacePolycam/InterfacePolycam.cpp Line 151
// initialize optional options
Util::ensureValidFolderPath(OPT::strOutputFileName);
if (OPT::strOutputFileName.empty())
OPT::strOutputFileName = "scene" MVS_EXT;
if OPT::strOutputFileName is not empty, it will add a ‘/’ in the end , causing failure in scene.Save Line 357 .
So, by commenting out this code in line151, the program will work correctly. Here is the code:
// initialize optional options
//Util::ensureValidFolderPath(OPT::strOutputFileName);
if (OPT::strOutputFileName.empty())
OPT::strOutputFileName = "scene" MVS_EXT;
Describe the bug
No ‘scene.mvs’ file generated when running InterfacePolycam use parameter " -o SAVE/PATH/scene.mvs ".
if don't use parameter " -o ", it will save ‘scene.mvs’ file successfully in current folder.
To Reproduce
Steps to reproduce the behavior:
.dmapcould be generated, but NO ‘scene.mvs’ fileExpected behavior
Generate ‘scene.mvs’
Additional context
I noticed that
apps/InterfacePolycam/InterfacePolycam.cppLine 151if
OPT::strOutputFileNameis not empty, it will add a ‘/’ in the end , causing failure inscene.SaveLine 357 .So, by commenting out this code in line151, the program will work correctly. Here is the code: