I found an oddity when routing traces. Please checked movie.
I would like to route a trace to one pad as indicated by the ratsnest.
Whatever I do, it doesn’t want to stick to the pad. On the other hand, if I start
from the pad, then it works fine.
Any idea of what happens?
Just for info, I found a workaround by tuning the net default sizes. The minimal track size used to be 0.2 for some reason. I don’t know exactly why because I have always been using 0.125, and these days 0.1. By setting it to 0.1, the problem was solved. However, it does not explaines the behavior. There is enough space for the 0.2mm trace, and it refuses to route.
I’ve seen that as well, although I don’t recall what version of V6 I was using. You rightly called it out as a bug, I just started from the other pad and thought of it as a quirk.
Is there anything on or under the pad?
What does it look like if you: PCB Editor / View / Drawing Mode / Sketch pads
I think I’ve seen similar behavior before with attempts to draw castellated pads, which by definition overlap with the outside perimeter of the PCB. Some external sites that generate footprints draw some lines on the Edge.Cuts layer in the center of a pad, and that could be a reason you can’t reach the pad with a track (It preserves the clearance from the lines on Edge.Cuts).
I do agree with twl though. It looks like a bug, and to fix the underlying issue a test case is needed.
No, there was nothing under the pad, it’s a plain resistor taken from a standard library and copied to my personal component list. The only thing I usually change is the radius at corners.
Yes, but in this case, how can you explain that it works when drawing from the pad?
And beside this, sorry, I cannot publish the file.
I’m trying to reproduce the bug in a new file right now. Stay tuned!