Examining these, it does a slow shift, but never really looses sync with the design. I would think the basic controller would be eliminated. I’ll mention a possible exception.
How I evaluate these also include if it is a single item at a time or if there is a row of them to see if the problem is corrected or propagates on the next item. That also depends on how you have them being lased or what type of optimizing is enabled. I’m assuming certain ideas of how it’s being produced.
Do you do ‘sets’ of these?
If so is the problem propagated?
This is a shot in the dark, but I think it might show more of a problem at some speeds, so I’ll post the link to the issue. You are only having an issue with a single axes, so if you try this, which shouldn’t hurt, only change that axes, not both.
I’ll wait to hear back… maybe I can come up with something else…
![]()
