Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Collision Map Gets Reset when Using Simplify Mesh

#1
When I right-click on an item and select "Simplify Mesh", the collision map gets reset after saving and reopening.

Steps to reproduce:
1. Download the Additive-Manufacturing-and-Machining-with-Mecademic-Meca500-R3 workstation from the sample stations library to use as an example.
2. Open the collision map from the toolbar as shown below.
   
3. In the Collision Map Settings dialog, click "Select none" to remove all collision pairs
4. Close the Collision Map Settings dialog
5. Save the workstation (wait for the message in the bottom-left corner confirming a successful save)
6. Open the Collision Map Settings dialog and verify that there are no active collision pairs (as-expected)
7. Close then re-open the workstation
8. Open the Collision Map Settings dialog and verify that there are no active collision pairs (as-expected)
9. Close the Collision Map Settings dialog
10. In the item tree, right-click the "3DBenchy" object and select "Simplify Mesh". Run with default settings and wait for it to complete.
11. Open the Collision Map Settings dialog and verify that the only active collision pairs include the new version of "3DBenchy" (as-expected). (Note: There is also something that probably shouldn't be there called "TEMP (DELETE ME!)".)
12. Close the Collision Map Settings dialog
13. Save the workstation (wait for the message in the bottom-left corner confirming a successful save)
14. Close then re-open the workstation
15. Open the Collision Map Settings dialog and observe that there are many active collision pairs for various items (I think it's the same as default). This is NOT as-expected.
#2
This issue is probably related to the fact that you are using a very new addin (Simplify Mesh) with a not so new version of RoboDK.

I have not had the time yet to reproduce this issue, however, the hidden object called TEMP should not be there if you use the latest version of RoboDK. Is it possible for you to test with the latest version of RoboDK?

On the other hand, you'll loose the collision map settings for the object you simplify (behind the scenes, a new object is created and the original is removed). However, we'll try to improve it so that we hold the same properties for the simplified object (including the collision map settings).
#3
Hi Albert, using the latest version of RoboDK (5.7.1) looks like it resolved the issue. There's no TEMP object and the collision map does not get reset.
#4
Wonderful, thank you for your feedback.
  




Users browsing this thread:
2 Guest(s)