I am coming across a couple of issues with using the teardrops feature.
I have a footprint that uses multi same numbered pads. Since it has multiple pads then traces can connect to the numerous connection points of each pad.
However, when enabling teardrops, the teardrop for each trace gets drawn, but there is an additional internal teardrop between the points - for example:
Secondly, if I convert the multiple same numbered pads into a single complex/custom pad, then teardrops does not work at all for any trace going to the single complex/custom pad.
Will teardrops for complex/custom pads be supported in the future?
There are not very many people who use teardrops, and your usage is also a bit unusual. KiCad developers are also spending most of their (KiCad) time on developing (which is what they do best), and not on debugging (with which any active user can participate in) Combine those factors, and it’s quite likely that bugs like this go undiscovered for a while.
So now you have an excellent opportunity for helping with KiCad development by reporting this on gitlab.
All of KiCad’s GUI program have a button for reporting bugs, that directly opens a gitlab topic. But you do need a gitlab account, and search a bit to see if your issue has already been reported.