When I am browsing through lots of images in the 2D view port to set control points eventually I run out of memory, RC eats all 64 GB for image cashing and then the system becomes unresponsive. Is there a way to limit this cache RAM usage ?
Hi Boris,
thanks for the report. The cache should not exceed 200MB so it looks like a bug. We will check it.
I had the same issue yesterday when I ran RC on my work laptop- it is only 16GB ram but after a fair bit of scrolling thru images for placing GCPs (project had ~2000 images) it was giving me an out of memory error and windows was requesting to shut down RC. Instead I saved and did a re-boot- which improved for a while then had to re-do a while later.
On this topic- what will improve the speed of the image display in the 2d window- when placing GCPs and scrolling thru images with the left / right keys it can take a little while to get a proper image (ie. not pixelated preview) image appear… just wondering what hardware or software settings would speed this up?
thanks
Hi Peterwatson
To speed it up only SSD can help…
Thanks Wishgranter, luckily this machine has space for another drive, so I will put in a decent size SSD when I get a chance. From reading the machine specs it will also take a nvme drive as well ( HP zbook 17 G2) but this will default to boot drive so I doubt I can do this on a corporate machine- would need a re-install of operating system which isn’t easily achieved/allowed.
Will I get a decent performance boost by installing a secondary SSD drive and running RC projects on this? Are there settings within RC that I would need to define to run this SSD as scratch disk so it’s using the solid state memory not the slower boot drive?
Hi Peter,
we have fixed the issue. It will be fixed in next update. Thanks for reporting again.