I’m hitting a similar wall encountered by this user, here this red flag comes up in Reconstruction during grouping depth maps:
I have plenty of space on SSD with temp folder, tried restarting> Reconstruction, see cache stores previous work in producing depth maps, but hits this bump regardless.
I also tried changing permissions in RC to Run as Administrator, trying that now, but hoping to get ahead on this problem to beat down a deadline, so question is, if this doesn’t work, what’s my next step? Clear cache? Run new Alignment? I hate to loose coordinate system from related Reconstruction Zone, no way to preserve that work? Thanks for any ideas and insights what’s causing the issue.
I’m thinking the issue has cleared (ran the first Reconstruction Region successfully, awaiting to see how additional RRs go), but not without questions.
Firstly, I’m curious what all can cause this issue? I’ve suspected lack of system resources, yes? What else?, is there something in an Alignment that can spell problems for Reconstruction?
Secondly, I cleared the cache in Temp, and this now relates to the same question in a separate post, but I’m not clear how Temp functions in RC. If I clear Temp for a reason related to one .rcproject, then don’t I impact all other .rcprojects? That would seem to defeat the conventional use of a cache. If this is the case, I just need to know so I can do a workaround, e.g. assign each project its own Temp folder, a bit of a pain. Thanks for considering an option to make Temp project specific to alleviate the extra steps of setting and restarting RC with every project.