Hello,
i’m placing multiple vias to increase current capabilities of a connection:
the mechanism of removal of redundant tracks seems that is stronger than the locking flag on the tracks, no matter if i start connecting and locking from top or bottom, i always end up with 1 via unconnected on top or bottom:
is this something new? there is a way to avoid this behavior?
Don’t remove redundant tracks if you want to keep redundant tracks . . . 
“Elementary, my dear Watson” 
for context:
Totally disagree! When you deactivate this, you globally end up with tracks looking like that:
This problem is not solved in my opinion.
@Claudio.Lorini I don’t know if this works, but you could assign a special net class to the nets, where you want to have redundant tracks. That would be helpful regardless of the initial problem, so you can route, for example power lines, with a set width and via size.
And with that existing net class maybe there is the option in the custom rules to exclude this netclass from the redundancy option.
So remove the redundant part that is clearly right in front of your nose . . . only you know which of the different routes is what you want, KiCad can’t read your mind.
No, with the option on, the existing/old track path gets deleted while routing/completing the alternative path.
This screenshot is the result, when the option is switched off.
My view is that the removal should fail to remove locked tracks, but create a report of the failures.
I agree, locked items should be locked; i was thinking about a feature request/bug report (not sure if this is expected behavior)
I think there is an issue with that . . . the removal function is running all the time, it’s not a user initiated thing like a delete . . . so it would potentially report constantly.
Unless you meant a DRC report type thing ?
Why would it, if it detects locked items and doesn’t try to delete them?
Anytime this check is made it would potentially report . . . maybe the check is only made when a user creates a new track or a track mod ?
