Many thanks! I really appreciate all your inputs.
The rollback function worked out great. I used it to reverse the move as well[bigsmile].
The process still gets slower and slower over time which seems like something I have to endure because moving objects around causes a lot of updates, but...
Ok, another thing that worth mentioning is that when I added one more body to the "slow .prt file", it was numbered as 5033 (see screenshot). So obviously, 5032 minus 18 bodies were created during the execution, and they seem to occupy some resources even though they were deleted.
Hi Tomas,
The Part Navigator remains the same throughout even when the intersections are generated (probably because their type is boolean?). I think no feature will be generated when I move a solid body because otherwise I would end up having a ton of bodies on my screen...
Hi BubbaK,
Thank you very much for your valuable input. I'll definitely give 'Orphan' function a try!
Here is a portion of my SNAP code which basically consists of three parts: first perturb a randomly chosen body, then calculate the distances between bodies, finally generates the...
Hi Thomas,
Thanks for your reply! I have 18 bodies in the .prt file which is given by our customer, imagine 18 irregular cylinders. In each iteration, the code will randomly choose one from 18 and perturb it (do either translation or rotation).
The size of the file is actually very small...
Hi everyone,
Please excuse my English, not a native speaker. Here is my problem.
I wrote a piece of automation code using NXopen (SNAP) to move the bodies around repetitively in a .prt file in order to pack them together in the tightest fashion. Through the course of which, the code will also...
