Im trying to work out if i can use CR for a project that I’m doing and am using the trial version. I was wondering if the build version for the actual program was any more stable? Im trying to reconstruct a 1500 image model in high detail and the program seems to have caused a system reboot several times and on the one occasion it didnt it appeared to get stuck about 50% through the process. CPU was still very active, program gave no errors, but the estimated finish and progress bar didnt move for hours, paused, saved resarted, seemed to be working again but system rebooted about an hour later.
I would really like to be using CR as it seems a lot faster, and from what I’ve read (I’ve yet to get it to finish a reconstruction) the models are more accurate. but it’s just not going to be viable if i have to keep going back to the workstation and restarting things every day.
has anyone got any positive or negative feedback on the stability of the licenced version?
thanks
Im on windows 10, 2x6 core x5690 (3.46), 96GB RAM, GTX970, with everything running off an ssd. The images I’m using are 24.3 megapixel RAW files.
I was having the same problem as you - but it was a very nuanced issue on my computer, took me over 7 days of hard work to figure it out and to stop blaming RC for it. It was only happening in RC, not in my stress tests, etc.
Point is this software will take your machine to the absolute limit, so if there is even the slightest thing off, RC will break it. I’ve found that if it doesn’t produce a dump file, it may very well be your machine.
Other than that, it’s stable for the category of software that it is in. It’s very picky with UV maps, and will occasionally get buggy but the help is rather quick on the forums to help figure out if it is the program or something with your machine.
I can’t texture my models and am getting a dump file, but my machine also went kaput a few days ago - that’s me not being able to work on a project, but I’m used this software enough to know that I’ll fix it in a few days or someone from RC will help out if I can’t.
Long story short, my experience has been very positive with RC and CapturingReality as a company (even if you haven’t bought 7.5/15k options). Keep in mind that it’s a small team and relatively specific set of customers, so unless you are paying for the super expensive versions, there will be some waiting involved to resolve whatever issue you’re running into.
I have used Demo and Full version on my Z170 ivi bridge i7-6700, 64Gb (Crucial Ballistix), SSD (Crucial M200), Gigabyte GTX 960 with days long (3-4 days) calculations without any problem.
And as i can see, most of system crashes is not a RealityCapture but hardware. Well, to be honest, this is RC, because with 100% CPU and 100% GPU 24/7, and memory bandwidth it work as perfect stress tester for problems in PC hardware. And about 50% of this is just a PSU problems.
BTW, this is self assembled PC that work much much better than bought on work DELL XPS, with similar configuration except less memory and AMD video (i’m designer, so no huge requirements in GPU) so this DELL crashed to blue screen 2-3 times in month.
Its been running for about 12hours straight again now and with about 50% progress it’s still ok (i hope writing that hasn’t jinxed it!).
Im not sure how i would go about trying to narrow down a hardware issue as there is nothing obvious as far as i can see at the moment. The processors are xeons, and aren’t overclocked or anything like that so should be happy running full tilt 24/7. and the machine is a dell precision r5500 workstation so the rest of it should be ok with that too - even if it’s got some years under it;s belt. But it could as well be something more to do with windows and how thats working with the hardware, but as someone thats come across from the mac world specifically for CR i don’t know all that much about the OS. At any rate… it seems to be coping in this attempt, so fingers crossed we’ll get to the end this time.
Hi Wilkie
Please take a look in the Windows EVENT VIEWER, there is detailed information on CRITICAL ERRORS, so it is then easier to pinpoint the troublemaker…