in the attached demo, select Local_CS001, and then change AttachmentOffsets (Z and Roll for example) in the Property window and see what happens. Of course you could do that otherwise too. If your changes are too wild the fillet might not pass.
in the attached demo, select Local_CS001, and then change AttachmentOffsets (Z and Roll for example) in the Property window and see what happens. Of course you could do that otherwise too. If your changes are too wild the fillet might not pass.
Thank you for the example. I am trying to understand the advantages of the LCS compared to the Body origin and sketch attachment properties.
As I understand, you can have only 1 Origin in a Part or Body, but you can have many LCS
OS: Ubuntu 18.04.1 LTSWhen I try to make any attachment change to the Local_CS001 the model breaks as shown below. What version are you using?
But, you can have any number of sketch attachment offsets.
Same, same result.
yes, I know that you can do the same with other tools. But how do you visualize the position of the sketch when you're creating it ? Also, what if you want to attach more stuff on the same position ? Like a sketch, a Datum Line ...
strange .... dunno
I suppose one of us should submit a bug report if someone can duplicate the behavior
Your modified file now works as expected with my version, so perhaps it is not a bug but a problem with the original model?
Syres wrote: ↑Thu Jan 24, 2019 6:20 pmFirst thing to say, I had to remake the Fillet in @Zolko's demo file for any of my builds to work including the latest ASM3. Then with my modified file (attached) I narrowed the issue down to a Py3Qt5 problem based on just changing the Roll anywhere between 90 and 45 degrees in the same build revision:
Works using:
Version: 0.18.15697 (Git)
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Doesn't work using:
Version: 0.18.15697 (Git)
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
The oldest Py3Qt5 build I have is 018.15468 and it fails in that too.
realthunder wrote: ↑Mon Jan 21, 2019 10:01 amYou are using an older OCCT 6.9. It is (so much) better to use 7.3 (used in my AppImage) instead. That's probably why you are getting lots of model breaking when switching between different FC builds. And that may also be part of the reason of the above performance difference.
Ok, thank you for the explanation, I don't use PD much and my models are nothing like as comprehensive as @ppemawm produces so I've never come across any OCC bug as much as I swap between OCC 7.2 and 7.3.