Intersect polygons bug

Hi,

i have a problem with drawing polygons. So i intersected two polygons to create a cooper pour for connecting two leds. after saving the design and reopening the project everything goes to… can someone help me with this?

how it should look

how it looks likeafter reopening

You need to give a little more detail or even better upload your footprint . . .

Its not clear, for example, which polygons you overlapped.

… or even better: Upload a (mini / example) project in which this footprint is used. It looks like this is not just a single footprint, but there is a cluster of 8 footprints (with each 3 pads) on the PCB.

Are you sure about that? In your first screenshot it looks like the circle overlaps with one pad, while I see three in the second screenshot. Did you create multiple circles, and then created intersections with each of the “pad polygon / zones” and one of the circles?

1 Like

at this point I save the project and exit

this is how the project reopens…

do i am creating a cluster of 8 leds in series. im adding larger zones to conduct the heat and 1.25 amp max so thats why it looks maybe odd.

Please give OS and Kicad version. Go to Help > About Kicad. Top RH corner click on Copy version info. and paste into a post in this thread.

1 Like

To avoid multiple posts and upload examples, see: New Member Information in the FAQs to self promote.

1 Like

I assumed you were doing this in the footprint editor but the presence of ratsnest lines, and you saying you saved the project (not the footprint), suggests that you aren’t.

Have you tried making it as a footprint ? I know that is potentially going to give you BOM issues . . . but it might be a way forward.

This Shape Modification / Intersect Polygons is probably a new feature in KiCad V9 (And I’m still on V8), so I can’t reproduce it. But I do notice marko.f is using graphical items to create copper features. KiCad does have support for this (Introduced in V8 I think), but it’s quite different from using copper zones. Filled zones automatically create clearances around items from other nets, while graphical objects simply keep their shape.

Graphical items can have a net name (Probably “” by default). Maybe KiCad gets confused by the footprints and their pads overlapping with the graphic items. What happens if you create the intersection of a rectangle and a circle outside of all those footprints?

I don’t have “Merge, Subtract or Intersect Polygons” in shape modification on 9.0.2, so maybe OP is on 9.99?
This is why I asked for Kicad version above.

no its the pcb editor its not supposed to be exposed… i just wanted to create custom traces

i have 9.03 you can recreate it i think just draw two shapes than right click go to Create from selection than click on Create polygon from selection do that for both shapes. Than select both and go to Shape modification and Intersect polygons

Please try to be more precise. KiCad V9.03 does not exist, the logical assumption would be you meant V9.0.3, but jmk asked you to copy the full version info, and this is about 20 lines of text.

In KiCad the menu’s are slightly different, but If I first turn the circle and the rectangle into polygons, then the Shape Modification / Intersect Polygons also appears in my KiCad V8.0.9.

Doing this in an otherwise empty area creates:

And Save, Exit & Restart KiCad still shows the same shape, (Regardless of whether the shape is filled or not).

Application: KiCad PCB Editor x64 on x64
Version: 9.0.3, release build
Libraries:
wxWidgets 3.2.8
FreeType 2.13.3
HarfBuzz 10.2.0
FontConfig 2.15.0
libcurl/8.13.0-DEV Schannel zlib/1.3.1
Platform: Windows 10 (build 19045), 64-bit edition, 64 bit, Little endian, wxMSW
OpenGL: NVIDIA Corporation, Quadro K2200/PCIe/SSE2, 4.6.0 NVIDIA 516.94
Build Info:
Date: Jul 8 2025 05:19:33
wxWidgets: 3.2.8 (wchar_t,wx containers)
Boost: 1.88.0
OCC: 7.9.1
Curl: 8.13.0-DEV
ngspice: 44
Compiler: Visual C++ 1942 without C++ ABI
KICAD_IPC_API=ON
Locale:
Lang: en_US
Enc: UTF-8
Num: 1,234.5
Encoded кΩ丈: D0BACEA9E4B888 (sys), D0BACEA9E4B888 (utf8)

1 Like

Probably the bug appeared in newer versions… i tried in an empty project just for testing and same problem appears…

1 Like