I use Kicad now and then just out of interest. I am 99% a Linux user so if I do a final design myself then I use the Geda pcb tools, simply because I have used them for many years, and while they have their own problems, the library handling is vastly better than the Kicad system. And I do not see much hope of an improvement in the Kicad library system in the future. Linux default library paths
There is no real collaboration needed on designs in my work (short term entertaiment, shows, exhibitions, films etc.) so If a test piece is passed on to a colleague it is never more than a few pages of A4 and always needs modifying and redrawing so it is no big deal for them to redraw it in whatever software they use. I have seen copies of Altium and Eagle at one end of the spectrum and RS Designspark at the other. The same with Cad software, $olidworks, Rhino cad and me with Freecad
It does not seem to be anywhere near as active as Kicad but development is going on in the background, it just seems that there is no forum for public discussion about the software. The last update to the development branch I got was about 5 weeks ago from an ubuntu PPA https://launchpad.net/~mehanik/+archive/ubuntu/geda-unstable.
It is easy to build from source as well and a lot easier code to hack than Kicad, so modifying it to suit my needs is fairly easy.
The fix is simple. Type ‘B’ and the pours will regenerate except where there are errors where they appear hatched. Note the rats nest netlist name in the hatched error zone. Edit the zone (hit ‘E’ near a zone edge) and change the pour net to the rats net netlist name. (the rats nest name is usually near the top of the selection window). Type ‘B’ again, and the pour will fill. Run DRC and the errors are gone.
I have filed a bug report with the KiCad developers regarding this issue.
The zones are connected in the real pcb: copper over copper.
But jwpartain1 is right, it is potentially dangerous. They are not logically connected. To do so, edit the zone and select GND net.
Then refill the zone.
The ratsnest will only go away if the pour actually connects ALL GND pads OR these pads are connected to GND via tracks…
1,2 are an island
3,4,5 are an island
6 is an island
The red copper pour is not connecting them all together.
Your clearance settings are too wide, to make that possible.
The ratsnest tells you that you still got islands and your layout isn’t connected as your schematic implies/defines.
If you ignore this, your circuit will NOT work.
Just because you can place a GND symbol in your schematic anywhere you need GND, doesn’t mean your physical board has the same ‘option’ of creating GND ‘out of thin air’ at any place on your board. You actually have to make sure (and that’s what the ratsnest is telling you there) that the GND plane/tracks/net actually connects all pads that are supposed to be connected to GND are really connected to it.
The OPs problem was that the visual check showed him OVERLAPPING copper pour with a pad (just not to it’s center) while also showing a rats-nest link, which implies no connection (PCBnew tests to the center, not peripheral overlapping).
From a physical/technical point of view the layout would have worked.
You on the other hand have DISCONNECTED GND zones/pads/tracks/islands and your pcb will NOT work if you ignore this.
PS: If you’re lucky your pcb fabricator will stop your boards before producing them, as the gerbers have NET information in them for testing continuity of the copper tracks (E-Test).
The CAM tool they use will flag these as non connected, or at least should do so.
PPS: personally I have a GND pour on the back of 2 sided pcbs and have ONE via for EACH GND pad with a track to that pad right next to it, no matter if the front pour would have done this already (unless space is of premium):
There is a fix (usually) Type ‘B’ and the pours will regenerate except where there are errors where they appear hatched. Note the ratsnest netlist name in the hatched error zone. Edit the zone (hit ‘E’ near a zone edge) and change the pour net to the ratsnet netlist name. (the ratsnest name is usually near the top of the selection window). Type ‘B’ again, and the pour will fill. Run DRC and the errors are gone. Usually.