# Iggystlev - Hey folks. I am still rather new to... Channel: #support Source: https://discord.com/channels/1233487248129921135/1535064342741913631 Started: 2026-08-06T23:17:39.844000+00:00 Last activity: 2026-08-07T02:04:12.302000+00:00 ## Iggystlev — 2026-08-06T23:17:39.426000+00:00 Hey folks. I am still rather new to tscircuit so if I am asking this in the wrong place lmk where I should ask. I have finished laying out a circuit in tscircuit and it seems to be working well for everything I need so far, except for traces. The autorouter seems to be creating some odd traces here and there, which normally I would try to clean up by hand but I am running into some friction getting that to behave. Using the `pcbPath` attribute seems to work, but the way I am currently using it is too clunky. I have been typing in a number, watching the live pcb view update, seeing if that is right and continuing on. Coming from KiCad's trace editing tools makes me feel like there must be a better way, even if it is just exporting to kicad to do trace routing and then getting importing the trace coords back into tscircuit's `pcbPath` array. Can anyone shed some light on better ways to layout traces? ## Iggystlev — 2026-08-06T23:18:34.154000+00:00 Here are some examples of the odd traces i am seeing Attachment: Screenshot_from_2026-08-06_18-10-37.png — https://community.tscircuit.com/media/1535064571084144660 Attachment: Screenshot_from_2026-08-06_18-10-12.png — https://community.tscircuit.com/media/1535064571402915910 Attachment: Screenshot_from_2026-08-06_18-09-55.png — https://community.tscircuit.com/media/1535064571729936384 Attachment: Screenshot_from_2026-08-06_18-09-24.png — https://community.tscircuit.com/media/1535064571977408563 ## Seve — 2026-08-06T23:48:58.786000+00:00 welcome!!! ## Seve — 2026-08-06T23:49:01.487000+00:00 this is the right place ## Seve — 2026-08-06T23:49:30.802000+00:00 can you create an autorouting bug report? We are also struggling with this and doing our best to improve it ## Seve — 2026-08-06T23:49:45.398000+00:00 we don't want manual specification of traces but yes it is hard to get the autorouter to do the right thing ## Iggystlev — 2026-08-07T00:59:37.221000+00:00 I will make a github issue. What is the recommended way to work around this issue while waiting on the resolution? ## Iggystlev — 2026-08-07T01:00:50.809000+00:00 Is https://github.com/tscircuit/autorouting the correct repo for the issue? It is marked as archived. ## Seve — 2026-08-07T01:27:53.111000+00:00 https://github.com/tscircuit/tscircuit-autorouter, you can also report directly in app ## Seve — 2026-08-07T01:27:55.070000+00:00 one sec... ## Seve — 2026-08-07T01:28:02.638000+00:00 https://docs.tscircuit.com/contributing/report-autorouter-bugs ## Seve — 2026-08-07T01:28:38.358000+00:00 for working around it, yes pcbPath is the only option we currently offer for fixing it- most of the other options would cause too much data to be committed ## Seve — 2026-08-07T01:28:44.153000+00:00 ## Seve — 2026-08-07T01:29:50.471000+00:00 if you are at the stage where you're ordering, a lot of people will export out into KiCad for small final adjustments they aren't able to make with pcbPath ## Seve — 2026-08-07T01:30:52.201000+00:00 we have very good reasons for not manually routing- having that data inside the TSX "makes the ai dumber" (it's super token inefficient). You may want to consider using calc strings as well ## Seve — 2026-08-07T01:30:58.777000+00:00 https://docs.tscircuit.com/guides/tscircuit-essentials/relative-positioning ## Seve — 2026-08-07T01:31:13.266000+00:00 i think pcbPath supports those ## Iggystlev — 2026-08-07T01:53:04.375000+00:00 I tried making an issue in-app but it returned an error said I was trying too many times after trying once, so I assumed it was not setup. Thank you for the other links. ## Seve — 2026-08-07T01:53:26.359000+00:00 !! ## Seve — 2026-08-07T01:53:35.359000+00:00 Do you have a screenshot ## Seve — 2026-08-07T01:53:40.813000+00:00 I wonder if there’s a bug ## Seve — 2026-08-07T01:53:46.289000+00:00 Appreciate all this btw ## Iggystlev — 2026-08-07T01:53:52.149000+00:00 [attachment] Attachment: image.png — https://community.tscircuit.com/media/1535103654426841128 ## Seve — 2026-08-07T01:53:53.017000+00:00 Very helpful!! ## Seve — 2026-08-07T01:54:30.030000+00:00 Oh interesting, maybe use github directly? Or that doc allows you to create a link to the autorouting problem, you could share it here ## Iggystlev — 2026-08-07T01:58:22.396000+00:00 the tscircuit-autorouter repo seems to be for the newer "capacity-autorouter". I dont think that is the one I am using, I am using the default one. I tried setting that one up the other day but ran into a package issue. Unfortunately I dont have a screenshot of that error, I want to say it was something to do with object-hash subpackage?. Ok I'll try to organize these issues and see what I can get reproductions of. I appreciate the effort on your end. ## Seve — 2026-08-07T01:59:28.391000+00:00 Ofc we want everything to work by default!!! The capacity autorouter is the same as the tscircuit autorouter/default autorouter ## Iggystlev — 2026-08-07T02:00:55.406000+00:00 I thought the default was `sequential-trace`. I think I had some llm output that indicated some other issues I was running into with routing were typical of sequential-trace, maybe it hallucinated. ## Seve — 2026-08-07T02:01:24.666000+00:00 Yea we deprecated sequential trace recently because it was almost never able to successfully make a board ## Iggystlev — 2026-08-07T02:02:28.325000+00:00 ahh, that makes sense. I am using tscircuit@0.0.2229 right now, would that mean I am definitely using the capacity-autorouter? ## Seve — 2026-08-07T02:02:39.110000+00:00 Yep! ## Iggystlev — 2026-08-07T02:03:55.368000+00:00 Perfect, then ill make that ticket about this routing issue next chance I get at my computer. Thanks again! ## Seve — 2026-08-07T02:04:12.302000+00:00 Thank you! We are always looking for bugs!!!