STL from verify

[Cuda84]

Can we get a simple explanation of the differences between the two problems?

[Don LePore from CNC Software]

I don't know if you'll consider this simple, but here goes.

 

Robert's problem: In the process of saving the STL file, it was simply using up all the available memory. The solution was to pre-compress the memory used by the results of the Verify session. By doing this, there was sufficient memory to complete the saving of the STL file.

 

Dave's problem: There is a bug in the API call we use to convert the model into an STL file. That problem has been reported to the vendor and we are awaiting a solution.

 

Hope this helps.

[88Matt]

Hey guys, I just have to say that this thread is an excellent example of why I love using mastercam. The communication and cooperation between CNC, end users, resellers, etc. is top shelf.

 

I am currently in a room full of UG and ProE users right now , luckily it's temporary (just kidding) . They do not have near the support or fast responses as we do.

 

Thanks guys

[Don LePore from CNC Software]

Our Verify vendor has supplied us with a fix for Dave's problem. It has been incorporated into vX2 MR2. There is no guarantee that this will fix other problems exhibiting similar symptons. Once again, if you are running into this problem, please send me the parts so that we can test them.

 

Thanks...