Go to your probe utilities window, then select the button 'tolerances...' you can ignore tip touches so if your cad vs theo values are a little different it will no longer trigger the warning.
Though, I would check the help file for what the value in the box would stand for.
It may also help to reduce your Tessellation multiplier value (Edit - Graphics Display Window - OpenGL). The lower this value is, the more polygons will be used to render the model. This can help avoid false positive collisions, especially in holes and on curved surfaces.
Go to your probe utilities window, then select the button 'tolerances...' you can ignore tip touches so if your cad vs theo values are a little different it will no longer trigger the warning. Though, I would check the help file for what the value in the box would stand for.
I have tried to adjust the tolerance value on the tip of the probe, but I haven't noticed a difference no matter what I try. It could be that I'm doing it wrong - the help file isn't much help on that matter. It doesn't mention if this is an absolute value, like a value of -.01 reduces the probe tip by .01mm. Or, if it is a percentage, like -1 would reduce the probe tip by 1%. Or if it is a proportion, like a value of -0.1 reduces the probe tip by 10%. I have tried them all and haven't seen a difference with number of false positive collisions detected. I'm wondering if the tolerance field just doesn't work properly (at least in 2020R1).
As you say, R2ah1ze1, ignoring the tip entirely can be a good way to go. Shank and probe module collisions are still detected, which are mostly what I'd want to know about. But I'd like to retain the ability to detect the tip of a large radius probe clipping an edge.
I'm thinking about making some custom probe files where the tip Sphere value is just a little smaller than the Hotspot value and trying that, but I don't have a lot of time to play with that right now. I'd want to test for unintended consequences - maybe it would mess up the probe compensation.
onw of the biggest triggers of false contacts for collision detection for me was when i checked circles with a sample hit and the circle had a chamfer. The circles x,y,z don't always come to the edge, and your sample hit sometimes hits below the surface because of the chamfer. keep a look out for that.
scans and tip change in a star probe always show collision. I asked
Don Ruggieri for help with this in the 2023 tech preview. Has been an annoyance for a very long time.
