Hello dear user.
I cannot share with you any specific date of such release but we surely wont let people wait too long. Every bug that shows up and is being reported by users is immediately getting attention and according to priority they are being fixed.
That is GREAT news !!! We will wait patiently - we are in the middle of a large project (3500 images) and RC freezes at 95% every time… we updated our nvidia drivers and still no luck so will happily wait !
Note that we have to force quit the app when this happens (it becomes unresponsive and there is no CPU action) and when it restarts it can never upload the crash-logs for some reason.
Hey again.
could you please give me your hardware specifications and detailed information about the inputs? Shot from camera on ground or drone, amount of megapixel, which process is getting stuck, settings for the process (alignment settings or reconstructions settings screenshot, depending on which process is this case). This should not be happening at all even now, so I will try to assist you to get this correct.
Did you try to wait longer anytime? The percentage of the progress bar does not always have to be the real representation of time left and High detail can really take a long time. The other thing that may be causing this are the control points. In some cases users had too many CPs and pointed to very wrong spots or inaccurately (control points had big pixel errors). I would suggest checking your control points and possibly disabling the wrong looking ones and run the reconstruction again, but as I said this could take longer than you may think. If I had to guess according to your configuration possibly 2 or 3 days, also depending on your settings of course.
nope pretty sure the application totally freezes every time and always around 95% complete with the only way to get out being a force quit.
in the task manager its using 0% processing power if it was working it would use some processing power
in the applicatio windows it says the application is un-responsive.
the application screen itself turns grey
i will try to see if i can clean the control points but they are all pretty clean. I will also try to process the scene again with the console open so i can try to see what happens / where it freezes up
This normally happens when your RAM fills up. What you can try to do is increase the size of your “Paging file” (it should normally be twice as size of your RAM) but more can save you better in some cases. As a short description: Paging file supports your RAM and when the RAM fills up the rest of the data is being stored there to prevent lack of memory. Surely try the control points as well but try to adjust the paging file too. It is easy to search on the internet, nothing too complicated.
Ok great - as a first step I will increase the paging file and run with the console open so we can see whats going on. If it crashes again then i will try to edit the control points.
A few questions here as well :
Does adding control points help RC to run better ? ie is more better than less ?
Do they use up a lot of additional resources ?
We mainly use CP’s to align shoots across different cameras or on different days when the environment has changed a bit so trying to get the best strategy here.
Well control points are only there to fix misalignments (tearing falling apart) or to merge components together (also for setting the scale but that is not this case) a smart number even tho this cannot be said generally is somewhere between 5 and 10 adding too many or too less can result in failure. Also it is important to maintain their accuracy. They don’t slow down or make the process faster by any noticeable amount. Best solution is to keep good overlaps and not changing the height of the camera position too far if you shoot on ground and then do drone photos you should fill the empty space in height, as well as while shooting on the ground you should not take one shot from 1 meter and next one from 10 meters. The detail in the images changes brutally and therefore the features as well. If the shooting is done right the Control points should not even be needed.
That is not a bad size for your RAM, but as I said you could try to increase it even more and possibly that could help. While running the reconstruction check your task bar performance tab to see how much is the RAM being filled. If it raises the top the whole time, it is almost sure that the paging file is being filled as well.
well now at 38 hours RC keeps timing out and asking to renew my licence and my only option seems to be to quit RC and loose all my work… have a separate ticket for that now… nothing wrong with my pc the internet connection is strong ? why does RC need to ping the licence servers every 5 minutes ?
fixed the licencing but had to kill the project at 90% so will try to process again now with the extra ram and larger paging file and see what happens !!!
this is a screenshot of where RC usually crashes in my large projects after 26 hours - i have wasted 3 weeks now trying to get it to finish high quality on two different workstations but it cashes every time no matter what i do
i upgraded to 64gb ram and my paging file is 128 gb and whenever i am 90% at high detail the app slows to a crawl, my computer becomes un-resonsive and eventually RC crashes hard with no option to send a crash report (memory leak i assume)
i am now also noticing issues at high detail with smaller projects as well - just posted another ticket about missing parts when processing at hi-res for a much simpler piece
i sent a video using wetransfer to your support email with my workstation dieing so you can see as looks like a total memory leak however when RC crashes the workstation goes back to normal
i am sending another video where you see the RC processing screen starts flickering terribly at 95% before the computer looses all resources and reboots - this is happenoing on two different workstations of similar bjild (64gb ram intel i9900k)
here is a screenshot of the task manager resources
i am unable to complete my jobs!