V9-rc1 / latest v8.99 rerouting a "bad" routed track

“Cleanup tools won’t clean up the redundant cabling caused by this bug, just try it”

I also tried the cleanup tool, didn’t work, and it’s not really a part of this topic, which is about the “live” router, not a post processing thing.

Cleanup Tool and the Interactive Router settings are two different things . . .

But yes, to get back on topic . . . IMO what you showed was just adding addition tracks not re-routing. Why aren’t you re-routing by editing the existing track by dragging segments ?

1 Like

Looking at my reply record above, this is a BUG, I have reported it to the developer, and it has been confirmed

Overlapping track segments created when routing multiple turns (#19538) · Issues · KiCad / KiCad Source Code / kicad · GitLab

Good to see it’s reported and accepted as a bug.

Maybe I’m missing something, I hope I am, but as far as I can see what you have reported in your Bug report is not the same as the original topic of this thread . . .

Yes, that’s probably unrelated to the OP’s issue.

1 Like

As I can see it and understand HAYDEN reported exactly what this topic is about.

I suspect the fix to address his issue will still leave you unfulfilled . . . hopefully I’m wrong :wink:

I think and hope the results of this will be just fine :wink:

The imported Kicad file routed in Altium Designer

Well with a bit of luck in a few more iterations, say V15.0.0 Kicad will be able to wipe my arse for me :rofl: Happy New Year Dev’s :smiling_face_with_three_hearts: Now, get back to work.
:mouse: :zipper_mouth_face:

1 Like

Version: 9.0.0-rc1-608-g30d43c30b7, release build

Yeah.

1 Like

This is relevant to this thread

1 Like

Gitlab text is difficult to understand but it means the issue has been solved, right? Great work! :clap: :birthday: :champagne:

It’s for you to try and see if it fixes your case

Version: 9.0.0-rc1-608-g30d43c30b7, release build

Almost

The fix is almost complete, only this little thing found now when starting another track on the top layer, and adding a via, going to bottom layer, going up to top layer again—then the first track remains when it should be automatically removed.

I suggest you raise a new bug report with clear details of the remaining issue

1 Like

Don’t know how to do that, isn’t it enough with the current report, which report that now could be. I think 2 reports are mentioned in this thread, what that now might mean.

When the existing reports get closed by a patch, which seems to have fixed most errors, it is usually better to start a new issue with focus on the remaining errors. The cause may be unrelated.

Sorry to ask, but can you do that and just send the video and my short story about it. I can’t handle GIT.