Memory Allocation in X5

[EX-wccprogrammer]

I am using X5 MU2 (Verisurf Version) to handle point clouds from a laser scanner. I have a large file (~500MB) that I have been getting a popup error 'Out of Memory'.

 

I have hunted the configuration file, and can not find anything that deals with memory allocation. Am I missing something here?

[CJep]

Is that is point cloud data,.... can you filter some of the data?

[EX-wccprogrammer]

That is when I get the error. Trying to filter. Is there someplace to increase the memory allocation? I have 24 Gb on this box, it should not crash.

[CJep]

Can you filter the points prior to opening in Mcam?

 

I created a file with only points in it, 10,000 gave me a Mcam file of 1.5meg,... how many points are in a 500meg file?

I know there is a limit to the number of entities I can efficiently work with for surface model.

[TheePres]

Not sure if this helps, but under system config, toolpath tab, there is a memory buffering that you can increase,

[CJep]

Not sure if this helps, but under system config, toolpath tab, there is a memory buffering that you can increase,

 

That applies to toolpaths.

 

Page from Mcam Help Guide:

[EX-wccprogrammer]

Can you filter the points prior to opening in Mcam?

 

I created a file with only points in it, 10,000 gave me a Mcam file of 1.5meg,... how many points are in a 500meg file?

I know there is a limit to the number of entities I can efficiently work with for surface model.

12.8 million points.

 

Hence, the need for filtering.

[EX-wccprogrammer]

Normally, there is no problem handling the point clouds from a scan. This one is exceptionally large, and is pushing the limits of the software configuration. Hopefully I can find a way to manage it better, I have plenty of hardware to back this up.

[Bill Cronkhite]

Just a thought. Is it possible to re-scan? If so reduce the resolution on the scanner for lower point density?

 

[EX-wccprogrammer]

I finally managed to filter it down to a reasonable level. Multiple tries and crashes, but it is workable now. I will work with my tech that does the scanning, and ask him to crank it down a few notches.