Maintainers have been backporting some of the fixes to the v1.1 branch where possible — 27 backports in the past 7 days. The list of changes in this recap applies to the main development branch (future v1.2).
This week in FreeCAD development:
Sketcher:
- PaddleStroke fixed the sluggishness of dragging complex constraint systems (think 500+ constraints, PR#26598). He also fixed Snap to object not working on axis (PR#26558), the handling of autoconstraints in slot geometry (PR#26559), selection and zoom lag in large sketches (PR#26671), sped up large bulk selection (PR#26663), and fixed dimensional constraint text rendered backwards (PR#26554).
- AjinkyaDahale contributed part 5 of his code refactoring work (PR#22951).
- wwmayer added support for Bezier and Offset curves as external geometry (cherry-picked by leoheck, PR#25144).
- tetektoza changed the rendering of constraint text, arrowheads, and constraint icons to be above geometry lines (PR#26703).
PartDesign:
- PaddleStroke fixed the issue where it was impossible to select multiple points on two sketches (PR#26596) and enabled the dragging and dropping of shapebinders (PR#25264).
- kadet1090 fixed the incorrect preview for polar patterns (PR#26563).
- ipatch fixed invalid edge links (PR#26425).
- Krrish777 fixed the Boolean’s operation type drop-down list not updating after recomputation (PR#26582).
- captain0xff fixed the gizmo direction when the calculated point lies outside the face (PR#26616).
TechDraw:
- WandererFan fixed crashes in scripts on CosmeticEdge delete (PR#26646), restored manual control of view frames (PR#26125), and fixed two issues with axonometric length dimensions (PR#26445).
- Lgt2x improved drawing performance; the issue was especially noticeable when TD needed to scale hundreds of items on a page (PR#25898).
CAM:
- Connor added 0.05 um to V‑bit tip diameter to prevent invalid sketch constraints (PR#26535) and fixed duplicate label issues with toolbits (PR#26647).
- jffmichi fixed the Radius Mill Tip Diameter always resetting to 5.0mm when opening a file (PR#26707).
FEM:
- marioalexis84 added support for 2D geometries to SectionPrint (PR#25081). He also added the magnetic flux density boundary condition (PR#25897).
- mac-the-bike added half-cycle animation (PR#24129).
- xtemp09 modernized a function in the FEM code (PR#23743).
GUI:
- Krrish777 reordered the Add Property dialog fields to Name-Value-Group-Type (PR#26567).
- tetektoza fixed broken image plane transparency (PR#26590) and fixed an issue where Selection View — Picked object list would add the whole object to face highlights (PR#26589).
- Krrish777 improved error feedback when a user creates a Mirrored, LinearPattern, or PolarPattern feature (or other Transformed features) without selecting any base features to transform (PR#26565).
Other changes:
- Roy-043 fixed a regression in Draft where an object would be displayed incorrectly when the Draft Object Pattern property is used. He also removed v1.1 Sill Height code in BIM; this was one of release blockers (PR#26641).
- tetektoza fixed an issue where the Selectable property would not work on a Body in a Part (PR#25009).
- WandererFan applied a patch that allows the Measure module to retrieve geometry information for Surface module objects (PR#26479).
- drwho495 fixed another toponaming issue (PR#26691).
- kevinsmia1939 added diameter measurement (PR#24853).

Roy-043, wwmayer, 3x380V, kadet1090, PaddleStroke, TONY8779, YashSuthar983, adrianinsaval, and luzpaz contributed additional improvements and fixes.
If you are interested in testing the latest weekly build, you can grab it here.
PR stats: since the previous report, 78 pull requests have been merged (including backports to the v1.1 branch), and 40 new pull requests have been opened.
Issue stats: overall, there are 3146 open issues in the tracker, same as last week. There are 4 release blockers for v1.1 currently, same as last week too.
4 responses to “WIP Wednesday, 7 January 2026”
Fillet tool allows invalid radius when applied to multiple connected edges
Description
While testing FreeCAD 1.2.0 (development version), I observed unexpected behavior when using the Fillet tool with multiple connected edges.
When a fillet is applied simultaneously to two edges that are both connected to the same adjacent edge, and the specified fillet radius exceeds the maximum geometrically possible value, FreeCAD enters an inconsistent or unclear state instead of properly handling the invalid input.
From a geometric standpoint, such a fillet cannot be constructed with the given radius. However, the tool does not clearly reject the operation, nor does it provide an understandable error message explaining the limitation.
________________________________________
Steps to reproduce
1. Create a solid with three connected edges, where two edges share the same adjacent edge.
2. Select the two edges that meet at the same segment.
3. Activate the Fillet tool.
4. Set a fillet radius larger than what the geometry allows.
5. Confirm the operation.
________________________________________
Expected behavior
FreeCAD should handle this situation more explicitly, for example by:
• Rejecting the operation and displaying a clear error message, or
• Automatically limiting the radius to the maximum valid value, or
• Providing feedback explaining why the requested fillet cannot be created.
________________________________________
Actual behavior
The fillet operation fails or behaves unexpectedly, without clear feedback indicating that the failure is caused by a geometric limitation of the selected edges.
________________________________________
Additional information
This behavior can be confusing for users, especially when applying fillets to multiple edges at once. The limitation is purely geometric, but it is not clearly communicated by the tool.
The same behavior is also present in FreeCAD 1.1 RC2.
________________________________________
References / Visuals
• Fillet tool, radius = 9.99
https://imgur.com/ghPryKI
• Fillet tool, radius = 11.00
https://imgur.com/MG2s4zI
• Visual explanation of the geometric limitation
https://imgur.com/fT05PCR
• Maximum possible radius definition
https://imgur.com/73ClvYl
• Edge selection examples
https://imgur.com/cblv0ss
https://imgur.com/G7xdR0r
________________________________________
I have several pictures that clearly show the situation, but unfortunately this blog does not allow image uploads.
Thank you for taking the time to report this. However, this is a well-known issue without an obvious solution.
Hello,
I am not a developer, but I believe that in this case more could be done to address the erratic behavior of the Fillet tool.
In particular, it may be worth reviewing the implementation of Fillet when it is applied simultaneously to two edges that are connected by a third, common edge. In the usual case, when the fillet radii produce tangent circles whose centers lie on the same side of the common edge, the algorithm appears to work correctly.
However, when a configuration occurs in which the fillets have their circle centers on opposite sides of the common tangent edge, the tool fails, even though the resulting geometry appears to be well defined from a geometric point of view.
It is possible that the approach used for the case where the centers lie on the same side is already implemented and works correctly, but that this same logic is not applied—or does not work properly—when the centers are located on both sides of the common edge. Reviewing whether this approach can be extended or adapted to this second case could help improve the robustness of the fillet algorithm.
This implementation works well.
https://imgur.com/fDUNNJu
This implementation does not work well.
https://imgur.com/rx66YPD
Thank you for your attention.
The addition of diameter measurement (PR#24853) may seem like a small thing, but it will save me much effort. Thank You.