Crashing and progress question
Hey all,
I posed this scenario under the feature request section but my issue has gotten a bit worse and am looking for some advice as soon as I can get it.
I've got a massive model I'm trying to render in high and RC is crashing at the worst hours - the last one being after 20 hours of rendering the scene.
In the last update post, someone insinuated that if you abort a reconstruction, save and restart, that you'll pick up where you left off. Is that true? Can I do that if I'm worried if a recon won't finish to mark a mid-save point?
Or do I need to even do that? Surely RC writes to disk during a day's worth of rendering, does it pick up where it left off? Since the progress on this one is so long, I have no idea if it is picking up from square one, my tests at midpoint saves as described above, or if it's picking up where it left off and has a while to go yet.
Thanks a lot for any responses, need to figure out if I should just give up on high and settle for normal which I REALLY don't want to do.
I posed this scenario under the feature request section but my issue has gotten a bit worse and am looking for some advice as soon as I can get it.
I've got a massive model I'm trying to render in high and RC is crashing at the worst hours - the last one being after 20 hours of rendering the scene.
In the last update post, someone insinuated that if you abort a reconstruction, save and restart, that you'll pick up where you left off. Is that true? Can I do that if I'm worried if a recon won't finish to mark a mid-save point?
Or do I need to even do that? Surely RC writes to disk during a day's worth of rendering, does it pick up where it left off? Since the progress on this one is so long, I have no idea if it is picking up from square one, my tests at midpoint saves as described above, or if it's picking up where it left off and has a while to go yet.
Thanks a lot for any responses, need to figure out if I should just give up on high and settle for normal which I REALLY don't want to do.
-
RealityCapture cache all possible data and always try to reuse it.
This can be depth, dense, image, etc.
But some steps is not possible to cache, or this data is never used in other process, so this data probably will not cached.
So if you stop calculation process, and run it again, this time it will faster because RC will try reuse already calculated data.
On system crash or RC crash can be a reason for corrupted cache, in this case RC probably can't reuse cached data. -
Thanks everyone for the prompt response - Chris/Vladlen, when it saves the data such as depth maps and gpu work, does it do so automatically or should I abort the calculation, hit save and continue onwards? Anyone else have crash issues on projects that have over 1.5k registered 20MP images? I don't crash on any other program, and have done a fair share of tweaking on my rig.
Please sign in to leave a comment.
Comments
3 comments