This issue only showed up during recent heavy development runs. Earlier versions hounered clearances according to settings in their respective places in accordance with the intended behaviour.
It is 100% reproducible and applies to any project.
To test create a project with some SMD component. Add a couple of connections and a fill zone to one pad.
Regardless of clearance settings at global and/or net class levels the clearance does not go below 0.2 mm unless individually changed on a pad by pad basis!
The only way out is to set individual pads to a value <> 0. However this does not work for tack clearances since they do not have an individual track segment clearance setting. (yet)
It affects pads, tracks, zone fills, but works correctly for thermal pads likely because they have their own clearance setting.
So far I couldn’t find anything regarding this issue.
On first sight it looks like a bug that should be reported on gitlab.
However, narrowing down bug locations and behavior is detective work and something that users can do, and starting on this forum is a good way to do so.
I’ve seen several bug reports starting on this forum, nailed down to a very small area in the code before a bug report was made on gitlab, and then a fix committed within 24 hours after reported on gitlab.
I have not used 5.99 yet, so I can not help here.
Note “release build” for a 5.99? What sort of weirdness is that?
Release/Debug build is a technical detail about compiling binaries on certain OS’s, it has nothing to do with KiCad per se, the version string just shows it. Debug builds include some more debugging information which can be used with debugging tools.
