I tried restarting it and the problem persist, just to be a bit paranoid I also reboot the system, but it insist in 2 unconnected nets, I will check the bug report method.
The weird zone is due a not so well draw exclusion zone, I’m trying ground planes with different ground zones to minimize contamination of the reference ground of the IC with the ground of the zone with big currents (this is a DC-DC converter).
If you separate gnd zones you should not have any signal crossing the gab. Otherwise you could create a gab antenna.
(I’m not sure if this applies in your case. It seems something is crossing the gab on b.cu if this is a signal and not a gnd pour it could create a problem.)
Version: 4.0.5-e0-6337~49~ubuntu16.04.1 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC 5.4.0,wx containers,compatible with 2.8)
Platform: Linux 4.4.0-62-generic x86_64, 64 bit, Little endian, wxGTK
Boost version: 1.58.0
Turning on/off all layers and searching a bit seems like the right info was on ratsnet, there was two tracks with ‘unconnected’ ends (track are there and they are touching each other but the end of one is not the exact point of the beginning of the next).
So DRC ‘sees’ a everything is connected and ratsnet ‘sees’ a no-so-precise connection, who is right?
thanks Andy_P and Indir_Okanovic, but you are missing the point here, the post is not about how to solve this particular case or how to avoid the problem, but if I need to inform to the developer team if there is a bug, like its the case since ratsnet says there is connections missing (true) and DRC don’t think this is important, one is wrong and the other should say the same.
In this case I think ratnest should be more flexible with the connection points of the tracks.
I already submitted the bug.