Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I'm operating right now with a not so huge point cloud of 400 M points with Recap 4.2 on a 64 Gb computer, and my windows task manager shows that Recap is eating more tan 2 GB.
When I orbit the point cloud, the RAM consumption varies slightly, but when I do a zoom closer to the surface, then the amount of RAM that Recap is using raises.
And the more time you are working in Recap, the more RAM is used.
I think that its not bad news that Recap uses a low amount of RAM.
If the overall performance is good, less memory used is better, for two reasons:
a) Recap would be able to run properly in average class computers, not only on the more powerful ones. For me is common to register pairs of foint clouds in different computers, not necessary that all of them would be the cutting edge, and later mount the register sets in the main computer or the best one.
b) If recap uses low memory, and works well, there are still enough memory to run other tasks at the same time.
The problem would be if Recap ran slowly. I dont think that recap can run faster using more RAM. The bottle neck I guess (at least in my case) that could be in the network bandwith (ethernet gigabit) when several computers are loading and registering pointclouds over a local network.
