Kicad v9 vs v8 router

Layout
1

Hi, it seems like v9-rc1 behaves different compared to v8 when it comes to the routing functions: v9-rc1 seem to add quite a lot more extra angles of the tracks, not as straight on and simple as v8. Is this about a setting I missed or do they work different in this case by specific reasons?

router settings
router settings1920Ɨ951 193 KB

5 Likes
2

Opinions in this anyone?

3

Definitely worth reporting, especially if reproducible on the test scenario.
Itā€™s either so hard to set up rules for the interactive router to do simple, clean tracks; or there are other priorities in the router. Iā€™m still using Higlight mode for daily operations, as otherwise the results of the Shove mode are worse than my expectations.

4

It seemed to follow your cursor accurately !!

1 Like
5

Probably not worth reporting if no once else experience this what I would call weird difference compared to earlier versions of KiCad. If others experience this as appropriate, or even better, the eventual strangeness or bug must be me :slight_smile:

6

Hereā€™s a bit extended version:

7

The result is so weird that it must be some bug. These problems are hard to reproduce, as there are many factors that influence the process (incl. mouse movement), but I believe it can be improved with proper reports (the easier it is for the devs to reproduce, the bigger chance it will be fixed). I donā€™t run v9 yet so I can not check it myself.

8

Thanks, we better wait and see what others may say.

9

The ā€œextentedā€ version is needless. Just share the design (zipped project) and the short video. Then the situation can be tested and verified independently. IMO itā€™s worth reporting.

4 Likes
10

Thanks but I will not report it now, better wait in case others experience something similar. It might be me only, and thatā€™s not a bug in the software.

11

Nah, this looks like a bug.
There maybe something in your placement that agrivates the bug

12

Looks like a bug to me too, but I wait as mentioned, as it seems Iā€™m the only one having this strange thing, in this project, havenā€™t tried it in other projects. Maybe more than one person will test out kicad 9 soon ā€¦

13

This is exactly why the developers need your sample that breaks the routing. Some combination of settings and the design has exposed a bug.

1 Like
14

Ok, tested another project, behaves the same (here) so I better upload some files. No one else experienced this?

15

Same here, not matter which project, happens for all of (my) projects.
Just a small example:

Application: KiCad x64 on x64

Version: 9.0.0-rc1-90-gbdf28a1c5c, 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 26100), 64-bit edition, 64 bit, Little endian, wxMSW

Build Info:
	Date: Dec 26 2024 06:17:20
	wxWidgets: 3.2.6 (wchar_t,wx containers)
	Boost: 1.86.0
	OCC: 7.8.1
	Curl: 8.10.1-DEV
	ngspice: 43
	Compiler: Visual C++ 1942 without C++ ABI
	KICAD_IPC_API=ON

Locale: 
	Lang: de_AT
	Enc: UTF-8
	Num: 1 234,5
	Encoded ŠŗĪ©äøˆ: D0BACEA9E4B888 (sys), D0BACEA9E4B888 (utf8)
1 Like
16

ā€œGoodā€ to see it happens on other places too. I have reported to Gitlab, hopefully I did it correct. Itā€™s not easy to do it without some ppl may get annoyed.

17

Link to issue: 9.0 rc-1 routing craziness (#19377) Ā· Issues Ā· KiCad / KiCad Source Code / kicad Ā· GitLab

1 Like
18

I think itā€™s difficult to follow the flow in the GITLab threads. Itā€™s something about the layout which makes me dizzy.

19

Itā€™s an art to write well described bug reports. Itā€™s not always easy to include whatā€™s obvious for one self, but leaves the reader clueless. Practice makes perfect, and it helps to take time and read through it a few times. Make it a habit to read through it in preview mode before posting.

20

No, on the contrary, thatā€™s very easy. :grin: But in case you meant it on the contrary: itā€™s actually exactly the same as here in the forum, or anywhere else, when asking a question. Tell exactly what you have tried, what happened, what you expected to happen, all the relevant details and nothing more, give a repeatable example, attach screenshots/video/project but as terse as possible to show the problemā€¦

The only important difference is that in case of bug report you already should know that thereā€™s some lacking feature or the software works in a wrong way and you didnā€™t use it in a wrong way.