I don’t know what I did but I broke routing thru-holes. I even upgraded to KiCad9 and told it not to import my preferences and I’m still stuck here.
Whenever I try to route from or to a thru-hole, it acts like that’s an edge and I cant violate it.
If I start from the thru-hole, i can’t leave the hole.
If I try and route TO the thru-hole, it just goes around it.
What is the origin of this footprint? My guess is you found it on some internet site far, far away. pads / holes look weird to me, although that could be because you are using KiCad V9 and I’m still on V8. (In V9 pad colors have changed because a pad stack has been added, in which pads can have different shapes and sizes on different layers. In V8, all THT pads are always Yellow).
Pads with oval holes in those far away internet sites are often defined with routing on the Edge.Cuts layer, and that is something that KiCad does not like very much. KiCad also paints a black hole in the center of THT pads. This obscures anything could be inside the hole (Even grid points) and that is a bit unfortunate.
For comparison, you can have a look at one of KiCad’s default footprints, for example: BarrelJack_CUI_PJ-063AH_Horizontal It has oval pads with oval holes, and both are defined in the pad properties themselves.
These exact footprints are routeable in other designs; and it’s happening for every single thru-hole component, not just a single footprints object.
It was behaving the same in KiCad8, I upgraded to 9 to see if ignoring preferences on Import fixed anything and it didn’t; so there has to be something odd about this specific board file (which is my own)
