CAM Pattern's "Target"/simulation does [not] work as intended

CAM Pattern's "Target"/simulation does [not] work as intended

ltomuta
Advisor Advisor
575 Views
3 Replies
Message 1 of 4

CAM Pattern's "Target"/simulation does [not] work as intended

ltomuta
Advisor
Advisor

ltomuta_1-1597245880100.png

I prepared a nice little project to show you how Target in patters behaves exactly the opposite vs. documented intent. But it turns out, it is a known issue since at least 2018. Two more months and we can bake a 🍰 for it.

Anyhow, now that we're talking patters, when simulating it, shouldn't the "Go to the next operation" button go to ... the next operation in the pattern, instead of the same operation on the next component?

ltomuta_2-1597246356015.png

 



0 Likes
576 Views
3 Replies
Replies (3)
Message 2 of 4

seth.madore
Community Manager
Community Manager

Regarding your first portion; The thread you linked to seemed to indicate that this was intentional and not a bug. So...

I can see why it's doing what it is. If you have it set to Automatic, it will recognize everything, until you select "Targets", then it just selects those instead. It does seem to me that "Automatic" should get turned off when Targets are selected, but it also seems that it has no effect.

 

Your second; I believe you used to get it to work like that, prior to the implementation of In Process Stock caching. There were changes that were necessary and it seems this was one of the casualties. I don't see it returning to prior behavior.

 

Oh, prior behavior DID require you to intentionally select the operations instead of the Pattern itself..


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 3 of 4

ltomuta
Advisor
Advisor

Hi @seth.madore 

 

The thread does say that the behavior is intentional but also promises to improve/fix the hint displayed on Targets. Even better, if Automatic is checked then "Targets" should change to "Exclusion list" since that's the actual behavior: it allows me to select components which are not to be targeted. Exactly the opposite of Targets. Two years should be more than enough time to fix the UI to reflect an intended behavior.

Regarding the simulation, I am rather sure the behavior was the same before the IPS but even if not so, I fail to see how IPS impacts this. It's a timeline. You simply have to skip over n-bookmarks in it instead of jumping to the next one. It can take time to generate up to n-1 IPS meshes if needed. But right now I can click on the simulation timeline and immediately jump to where that button should have taken me, without problems. 

0 Likes
Message 4 of 4

seth.madore
Community Manager
Community Manager

Image - 207227] | You Must Be New Here | Know Your Meme

 

We have bugs and shortcomings that have been around so long it ain't even funny 😂🤣

 

The teams are working hard on delivering added value to the product. I don't at all disagree that bugs needs to get fixed; I'm a customer as well, I feel these pain points!


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes