Just installed V9, and it seems that it’s not hard to trigger that weird behaviour. Lots of acute angles, unnecessary track segments etc. Something definitely went sideways…
2 Likes
Good, a reproducible bug. Hopefully a fix very soon.
Yes, hopefully/probably soon as now v9 is quite unusable.
As a side note, which I think here is a bit funny/comical. I’ve been mentioning the Cadsoft “Follow-Me” router (released like 10 years ago) quite some times in this forum, have been mentioning this as in my opinion that function was a very good idea. Even if it was not “perfect”, the main idea with it and the function was interesting and now in this version of KiCad (9-rc1) it seems like we got a “Don’t-Follow-Me-At-All” router 
10 years ago there was already a pcad in which everything was there) then it turned into something incomprehensible)
8.99 and v9-rc1 router can work if routing very very slowly, though that’s not a progression or not even as good as v8. So let’s see soon what the thought is with the new router, this is thrilling.
v9-rc1 (8.99 Nightlies post v9-rc1) routing below (9.0.0-rc1-106-g0c60f368fa):
It could be interesting to see in what version of the macOS Nightlies this issue started but as there is no “old” (pre December 2024) macOS Nightlies available on the download page it’s not possible. Hopefully this wild routing issue will be fixed soon so we can begin to Test-use te newer version of KiCad for real. I have high hopes a new hotter version of Eagles “follow-me” router will be included
fyi, this isn’t just a v9 issue, I have “triggered” it with v8.0.6 (last night)… I however forgot to take a screenshot nor could I repeat it…
What I can state is the router “feels” like walking through treacle and also the resulting track, even if straight, has multiple segments once it is complete … I found it more likely to behave odd IF rounded 45 or 90 was selected
1 Like
Not related to V9, but has there been some changes to the router trace modification in 8.0.7? I feel some difference from 8.0.6 while trying to drag segments
even if straight, has multiple segments once it is complete …
This problem was also present in previous versions, although to a lesser extent.
In version 8.0.7, many times after routing, I have to correct the tracks that became multi-segment.
Hm, interesting, I did not notice it in any v8 but it was so obviously crazy in 9,0 rc-1 and 8.99 so I didn’t dig deeper, backwards, as I was thinking v9 is the way to go. I will not try to make it happen also in v8 as I’m soon ready to leave it for an outstanding v9
The best that I could do to trigger it
it looks like the real time DRC is calculating and then aspects of tracking catch up and “smooth” out the track … HOWEVER, sometimes that 2nd step doesn’t occur so you get the intermediate part is the real track.
yup I got it stuck
the hatching is a rule exception area (basically an ADC breakout zone so my 3W spacing allows me to… break out). If I move the mouse quickly out-in-out of this area, aspects of the “calculation” almost stop as it keeps permitting tracking where the new node is… IF I click to set the track I would get this, but a bit more “moving” of the mouse permit it to recalculate and create a cleaner track, consistent track.
Even if I don’t understand much of what you say here I like what you explain. Is it possible to make a video to show what you describe? Can what you explain soon be a solution to make the routing in v9 work to make the routing pretty calm and easy without too many wild/random tracks?
Downloaded and tested (just briefly so far) the latest 8.99 and the router now seem to have been born again! 
Application: KiCad PCB Editor x86_64 on x86_64
Version: 9.0.0-rc1-402-g9a3d7594d9, release build
Platform: macOS Sequoia Version 15.2 (Build 24C101), 64 bit, Little endian, wxMac
Build Info:
Date: Jan 5 2025 09:09:21
wxWidgets: 3.2.6 (wchar_t,wx containers)
Boost: 1.87.0
OCC: 7.8.1
Curl: 8.7.1
ngspice: 44
Compiler: Clang 16.0.0 with C++ ABI 1002
KICAD_IPC_API=ON
2 Likes
I can confirm it’s much more predictable now.
Application: KiCad PCB Editor x64 on x64
Version: 9.0.0-rc1-401-g3add0afdff, release build
Libraries:
wxWidgets 3.2.6
FreeType 2.13.3
HarfBuzz 10.0.1
FontConfig 2.15.0
libcurl/8.10.1-DEV Schannel zlib/1.3.1
Platform: Windows 11 (build 22631), 64-bit edition, 64 bit, Little endian, wxMSW
OpenGL: Intel, Intel(R) Iris(R) Xe Graphics, 4.6.0 - Build 32.0.101.5972
Build Info:
Date: Jan 5 2025 06:18:08
wxWidgets: 3.2.6 (wchar_t,wx containers)
Boost: 1.86.0
OCC: 7.8.1
Curl: 8.10.1-DEV
ngspice: 44
Compiler: Visual C++ 1942 without C++ ABI
KICAD_IPC_API=ON
Locale:
Lang: en_GB
Enc: UTF-8
Num: 1,234.5
Encoded кΩ丈: D0BACEA9E4B888 (sys), D0BACEA9E4B888 (utf8)
Yes, it seems to work really fine now, like clever and rhythmic. I only had one small little extra thing happening, because I was too fast and shabby with the mouse probably. Great work, very impressed so far!
I’ve learnt that one have to help the router by clicking (fixing) segments here and there, so it doesn’t have to focus on optimizing the whole track each time.
I have noticed that too.