Geographic reannotation, i.e. reannotating based on the component positions on the board.
Tools -> Reannotate PCB
EDIT: separate post here: Geographic Reannotation Now Included in PCBNew
Geographic reannotation, i.e. reannotating based on the component positions on the board.
Tools -> Reannotate PCB
EDIT: separate post here: Geographic Reannotation Now Included in PCBNew
Hatched zones now get aprons around connected pads and vias.
There’s a new UI for managing the appearance of layers and objects in PcbNew.
Featuring:
If you use a color scheme where you set your copper layers to have less than 100% opacity, I highly recommend you try setting copper back to 100% and use the opacity controls per object type. I personally think it’s a lot easier to see when tracks are fully opaque and other items are translucent.
Demo of per-type opacity:
Demo of net and netclass colors:
There’s a lot of new stuff here, so please report bugs!
…but not here.
General discussion about the features should have their own threads, and Net classes in Eeschema (5.99) and New Net Tools in pcbnew 5.99 are fitting for the net system related discussion.
I liked the “eye” icon instead the checkbox for layer hive/visible (like AutoCad, Inkcape, …) and the new opacity control! Just two observations:
Hello all, it was merged this new feature I developed for 3D-Viewer: light parameterization …with some improvements in the rendering:
Beautiful, marketing will love this
Excellent, I really needed this feature!
With these improvements to the viewer being made, would it be possible to support opacity for the board material, e.g. polyamide / PET?
Would you like to open a wish request on KiCad gitlab ? and provide some examples on what you would like to achieve?
Few people know that KiCad 5.99 has some invisible advanced configuration possibilities. You probably won’t need them but it may be good to know. See https://gitlab.com/kicad/code/kicad/-/blob/master/common/advanced_config.cpp where it’s documented.
It’s possible to group board items together.
screencast_group-2020-08-20_12.54.25
At the moment it’s just a “geographical” group which locks items together so that they can be selected, moved, deleted etc. together.
Compressed 3D models are supported, see KiCad will support compressed step and vrml models in the future. Yeah, I could use those gigabytes for something else.
Yay! Configurable origin and axis direction has landed, courtesy by @RRPollack. See User-selected PCBnew display origin (5.1.x) for background, but that thread is closed. (Please no bug reports or wishes here.) The feature won’t be integrated into 5.1.
EDIT: I wrote a FAQ article about the origins and coordinate system, Coordinate system, grid and origins in Pcbnew (especially version 5.99). It shows these new features.
All feature requests need to go to the bug tracker (https://gitlab.com/kicad/code/kicad/issues) Search for your suggestion there first (I think it might be implemented but not sure)
Hopefully one of our hard-working admins can move this hijack over the the #community:feature-request
Apologies, I deleted the post.
Alternate pin definitions.
A library symbol can now define alternate definitions for individual pins, and a schematic symbol can chose which alternate to use.
There’s a new tool that lets you convert lines/tracks to polygons/zones/keepouts and vice versa.
I think it’s pretty handy for creating zones from imported DXFs, replicating some copper traces on the silkscreen layer, and things like that.
It doesn’t support curves/arcs yet but will eventually.
convert_shapes
Great,
As usually curves are not handled. Why are curved tracks and rounded corners zones not yet implemented in Kicad? is there implementation that problematic? or is the Kicad code base inapropriate for handling such geometric primitives?
Curved tracks are implemented now (but some of the editing tools for them are still a WIP)
Seth is working on curved zone/polygon support: https://gitlab.com/kicad/code/kicad/-/merge_requests/375
Once that is merged I will update my tool to support it.
Historically the geometric primitives in KiCad did not support arcs very well, but, we’re working on fixing that for V6.