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 
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 
Happy New Year Dev’s 
Now, get back to work.
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! 
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.
Tried with a new issue report, hopefully made correctly this time.
What I understand, this what I call an issue/bug has now ben downgraded/classified as not a bug on Gitlab.
It’s now a feature request. Still valid.