You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: since Freerouting doesn't appear to have a way to force 90 degree routing via the CLI (as opposed to the GUI), I had to modify trace_angle_restriction below to force it to always be AngleRestriction.NINETY_DEGREE.
2025-02-06 19:10:55.910 [main] INFO Freerouting v2.0.2-SNAPSHOT (build-date: 2025-01-24)
2025-02-06 19:10:57.236 [ForkJoinPool.commonPool-worker-1] INFO New version available: v2.0.1
2025-02-06 19:10:57.340 [Thread-7] INFO Auto-router pass #1 on board '1b575aaf9b0e794f2e9428200ff7fe38' was completed in 0.12 seconds
2025-02-06 19:10:57.389 [Thread-7] INFO Auto-router pass #2 on board 'a458a7ea65d54434e2593994bd7e7469' was completed in 0.04 seconds
The text was updated successfully, but these errors were encountered:
Describe the bug
Freerouting leaves nets unrouted in 90 degree mode. The design is 90-degree routable and a proof-of-concept routing is provided.
To Reproduce
Steps to reproduce the behavior:
test.kicad_pcb
in KiCAD.test.dsn
.freerouting
via CLI as per the below.Expected behavior
I expected Freerouting to either route the nets or provide more information about why it gave up/quit.
Screenshots
Freerouting output:

Manually routed proof-of-concept:

Environment
Note: since Freerouting doesn't appear to have a way to force 90 degree routing via the CLI (as opposed to the GUI), I had to modify
trace_angle_restriction
below to force it to always beAngleRestriction.NINETY_DEGREE
.freerouting/src/main/java/app/freerouting/rules/BoardRules.java
Line 38 in 5b1c365
Command line arguments
Project files
If applicable, include project files like .pro, .kicad_pcb, .dsn.
See https://github.com/edwardcwang/freerouting-90deg-bug
Logs
The text was updated successfully, but these errors were encountered: