Seve - The traces arent correctly routing in th...

which has a messing sgement ?

the one in the bottom looks like its doing 180 deg turn

Yeah, something looks weird. I am taking a look

let me know if u want me to take a look

<@757706909351411845> It's because of effortLevel, I removed the `10x` effortLevel and it solves correctly

Something with the effortLevel is causing this bug

I am removing that prop from the doc now, and taking a look into the bug

Hmm strange

<@809856037376491570> https://github.com/tscircuit/footprinter/pull/659

<@757706909351411845>

<@809856037376491570> https://github.com/tscircuit/kicad-mod-cache/pull/24

I used eval in the dev dep to render the foot print generated from this pr is this a good repro for the issue ?

or can u give me a better way if this is not the right way

Yeah, I don't like this. This test was failing in eval. So, just use that footprint string and snapshot the test output

This was gettting flipped, just make sure that footprint's silkscreen text is not getting flipped

so the issue is not the kicad-mod-cache ?

No

oh ok mb

I will check it rn

<@809856037376491570> I managed to repro in eval and this should fix the issue in kicad to circuit json https://github.com/tscircuit/kicad-to-circuit-json/pull/150

but not sure if we can push the kicad mod code to our repo ?

maybe copyrighted, I can remove it after u take a look

<@809856037376491570> wehn u got time plz take a look

Taking a look

After you merge the kicad-mod-cache migration PR, also run the test Ci in eval after that

OK

can we merge the kicad mode code or I should remove it ?

Remove it I guess

k

<@809856037376491570> can I get another review on this so we can merge https://github.com/tscircuit/kicad-mod-cache/pull/24

<@809856037376491570> https://github.com/tscircuit/kicad-mod-cache/pull/24

<@809856037376491570> can I get a reivew ?

<@809856037376491570> so the text is bigger now for kicad Ref In kicad-to-circuit-json, the footprint text path does: const fontSize = kicadFontSize * KICAD_TEXT_HEIGHT_TO_CIRCUIT_JSON_FONT_SIZE `The old kicad-component-converter used the KiCad font size directly: font_size: fp_text.effects?.font?.size[0] ?? 1` So a KiCad silkscreen ref text with size 1 used to become font_size: 1, but now becomes font_size: 1.5. The reason in the new converter is documented in its comment: it is trying to be inverse-compatible with circuit-json-to-kicad, which apparently divides by 1.5 when going the other direction.

should we change kicd to circuit json to use the kicad font size or keep the current 1.5 ?

I think we should keep the size to be inverse compatible. Not so sure. <@757706909351411845> ?

Hmm, i dont really know whats reasonable here but if you convert kicad to circuit json it should be the right size in the snapshot (after unit conversions)

Anything else is strange no?

<@809856037376491570> I think I should just make the font as it was before ( that looks better imo)

but also figure out why the conversion scale is not 1.5 times, this might become an annoying bug

why do we sacle the text I'm not sure ?

https://github.com/tscircuit/kicad-to-circuit-json/pull/154

also can u review <@809856037376491570>

Scaling text makes sense for the schematic's cause what we see in our schematic viewer and what we see in the schematic's in the A3 size or something then it does needs scaling

I see so will this create bugs later for sch ?

I am not sure, run tests

we have another issue <@809856037376491570> Some KiCad cache requests return 500 Internal Server Error during footprint conversion. Example failing URLs: https://kicad-mod-cache.tscircuit.com/Package_TO_SOT_SMD.pretty/SOT-23-3.circuit.json https://kicad-mod-cache.tscircuit.com/Package_SO.pretty/SOIC-8_3.9x4.9mm_P1.27mm.circuit.json should we Update kicad-to-circuit-json so fp_poly parsing does not require uuid or tstamp. If both are missing, generate a deterministic fallback id from the polygon data, Then update the cache service to use the fixed converter ?

Yeah, repro this inside `kicad-to-circuit-json` and then create a fix for it

After that update the kicad-mod-cache

<@809856037376491570>

https://github.com/tscircuit/kicad-to-circuit-json/pull/155

bun linked to kicad mode cashe and tested it works

<@809856037376491570> turns out the issue is in kicadts rejects valid KiCad fp_poly nodes that lack both uuid and tstamp

should we make FpPoly.fromSexprPrimitives allow missing uuid/tstamp, same as KiCad itself does ?

wdyt ?

but should we generate a random id or not <@809856037376491570> <@757706909351411845>

or just parse it without one

Yeah, kicadts should be the place where you should be fixing it. Don't generate one

The file is the source of truth, don't add anything extra

ok sounds good

<@809856037376491570> https://github.com/tscircuit/kicadts/pull/55

<@809856037376491570> can i get another review on this ty https://github.com/tscircuit/kicad-to-circuit-json/pull/155

<@809856037376491570> https://github.com/tscircuit/kicad-mod-cache/pull/27

<@809856037376491570> <@757706909351411845> I checked the difference between the old `tscircuit/kicad-component-converter` and the current `kicad-to-circuit-json` parsing for KiCad reference text. The old converter had special handling for the font size of `property "Reference"` text. Instead of using the property’s own KiCad font size, it looked at `fp_text` entries: - Prefer reference-like `fp_text` on `F.SilkS` - If not found, fall back to reference-like `fp_text` on `F.Fab` - Use that `fp_text.effects.font.size` as the font size for the emitted `pcb_silkscreen_text` That matters for footprints like `R_0402_1005Metric`, where KiCad has: - `property "Reference" "REF**"` on `F.SilkS` with `(size 1 1)` - `fp_text user "${REFERENCE}"` on `F.Fab` with `(size 0.26 0.26)` The old converter would use `0.26` from the `${REFERENCE}` `fp_text` fallback. The current `kicad-to-circuit-json` preserves the `property "Reference"` font size directly, so it emits `pcb_silkscreen_text` with `font_size: 1`. Then `@tscircuit/core` consumes that footprint text and adds `+0.2` via `_footprinterFontSize = elm.font_size + 0.2`, making the rendered refdes `1.2mm`. That’s why example 18’s `R1` is much larger now. So the core behavior difference is: Old converter: `property Reference` font size came from small reference-like `fp_text`, often `0.26`. New converter: `property Reference` font size comes from the KiCad property itself, often `1`. This is why the ref text changed size after moving to `kicad-to-circuit-json`.

should we change kicad to circuit json to do the same ?

on the left is when we used kicad component converter

this is a nice analysis, i mean what does this look like in kicad? I think KiCad has ridiculously large fab text

if kicad has giant fab text, then the right side with the large fab text is correct

likewise, silkscreen is often much bigger than people would expect for small components. This is because silkscreen often cannot print very small

so ultimately the answer is however kicad displays it!!!

I will check kicad but I do believe big is right , u can also ask Sangit when debugging the pico small fps like 0402 silkscreen in unreadable

kicad is using big font

<@757706909351411845>

Then thats it

sounds good, will see if anything needs updating