I’ve been happily making scans with around 300 - 400 photos without any issues. RC is fast and the whole process usually takes around 6 or 7 hours.
Now I’m making a bigger scan with 1600 photos and I’m running into this problem:
Alignment is relatively fast and all goes well
Reconstruction in Normal Detail (default settings) starts well and seems to be going fast.
After 5 hours the progress bar is around 50% and the finish estimation says it will finish in around 5 hours, which makes sense because the progress is on 50%.
After that the progress starts slowing down and the finish estimation starts to move further away. +7hours…+12 hours… seems to be pointing to the infinite…
After running for 30 hours the progress had been minimal. The progress bar was just a bit over 50%. So I terminated RC.
What could be the cause? Why does the progress slow down with time?
The PC becomes very irresponsive and it’s almost impossible even to move the mouse cursor.
I’ve seen a user here in the forums with a somewhat similar problem and there was no solution in sight.
My PC specs: i72600k 16Gb Ram - GTX 1060 3Gb (normal HDD drive)
1600 RAW photos from 2 cameras - some are 18Mp and some 12Mp
That’s really annoying, not having an idea when it will be finished. I’m having this problem with large scenes. I simply have no idea if it’s going to take 10 hours or two weeks…
Could you explain how creating a new file and aligning again could help on this?
In my experience (no data, mere gut-feeling), it can take up to 3 times (or so) as long as initially displayed. There is no general rule because it depends on the dataset. Usually, I would say it’s about twice as long.
I am quite confident to say that 10 times the original estimate is too much. Similar things have been reported and also remedied by starting from scratch. It could be that in certain constellations RC kind of gets stuck due to some mathematical peculiarities in the model, which are not supposed to be like that. Sorry for being so vague, but I am a user and not a software engineer. Another possibility is that the file got corrupt. In any case, I myself have used this “method” a few times and it worked for others, too.