I’m working on a board that started life on v4.7 and has been updated along the way as I have updated to the latest version of KiCAD (currently running 5.1.2). I recently needed to rework a section of the board and I was running into weird routing problems where is seemed like I was running into something invisible. I checked all the layers, and even removed all the footprints from entire sections, but nothing helped.
Finally I changed the routing mode to highlight collisions, and low-and-behold a huge number of strange traces started showing up like fireworks as I moved the mouse around. Where did these come from? Never mind that, how can I get rid of these traces? I cannot select them; I can only see them while routing with highlight collisions enabled.
It is fairly common. It seems like there is a message about it every week or so. Though, I’m not sure what search terms that I’d use if I wasn’t familiar with the bug.
The only word which is common to all these reports is probably “trace” and even that can be “track”. Luckily we will get rid of this problem after 5.1.4 has been released and most users update their version.
Don’t worry, you will get the same official binary. It’s just because code is always tagged first it’s the first thing to be built on linux but on other platforms kicad distributes everything (binaries, translations, libraries) in single package so there is a small wait for everything to be ready.
About 9 hours ago Adam Wolf wrote: “MacOS is building. I am out of town and return tomorrow. If there are no issues I should be able to get them uploaded tonight, if not, Sunday.”
