Main­tain­ers have been back­port­ing some of the fix­es to the v1.1 branch where pos­si­ble — 27 back­ports in the past 7 days. The list of changes in this recap applies to the main devel­op­ment branch (future v1.2).

This week in FreeCAD development:

Sketch­er:

  • Pad­dle­Stroke fixed the slug­gish­ness of drag­ging com­plex con­straint sys­tems (think 500+ con­straints, PR#26598). He also fixed Snap to object not work­ing on axis (PR#26558), the han­dling of auto­con­straints in slot geom­e­try (PR#26559), selec­tion and zoom lag in large sketch­es (PR#26671), sped up large bulk selec­tion (PR#26663), and fixed dimen­sion­al con­straint text ren­dered back­wards (PR#26554).
  • AjinkyaDa­hale con­tributed part 5 of his code refac­tor­ing work (PR#22951).
  • wwmay­er added sup­port for Bezi­er and Off­set curves as exter­nal geom­e­try (cher­ry-picked by leo­heck, PR#25144).
  • tetek­toza changed the ren­der­ing of con­straint text, arrow­heads, and con­straint icons to be above geom­e­try lines (PR#26703). 

Part­De­sign:

  • Pad­dle­Stroke fixed the issue where it was impos­si­ble to select mul­ti­ple points on two sketch­es (PR#26596) and enabled the drag­ging and drop­ping of shape­binders (PR#25264).
  • kadet1090 fixed the incor­rect pre­view for polar pat­terns (PR#26563).
  • ipatch fixed invalid edge links (PR#26425). 
  • Krrish777 fixed the Boolean’s oper­a­tion type drop-down list not updat­ing after recom­pu­ta­tion (PR#26582).
  • captain0xff fixed the giz­mo direc­tion when the cal­cu­lat­ed point lies out­side the face (PR#26616). 

Tech­Draw:

  • Wan­der­erFan fixed crash­es in scripts on Cos­met­icEdge delete (PR#26646), restored man­u­al con­trol of view frames (PR#26125), and fixed two issues with axono­met­ric length dimen­sions (PR#26445).
  • Lgt2x improved draw­ing per­for­mance; the issue was espe­cial­ly notice­able when TD need­ed to scale hun­dreds of items on a page (PR#25898). 

CAM:

  • Con­nor added 0.05 um to V‑bit tip diam­e­ter to pre­vent invalid sketch con­straints (PR#26535) and fixed dupli­cate label issues with tool­bits (PR#26647).
  • jffmichi fixed the Radius Mill Tip Diam­e­ter always reset­ting to 5.0mm when open­ing a file (PR#26707).

FEM:

  • marioalexis84 added sup­port for 2D geome­tries to Sec­tion­Print (PR#25081). He also added the mag­net­ic flux den­si­ty bound­ary con­di­tion (PR#25897).
  • mac-the-bike added half-cycle ani­ma­tion (PR#24129). 
  • xtemp09 mod­ern­ized a func­tion in the FEM code (PR#23743). 

GUI:

  • Krrish777 reordered the Add Prop­er­ty dia­log fields to Name-Val­ue-Group-Type (PR#26567). 
  • tetek­toza fixed bro­ken image plane trans­paren­cy (PR#26590) and fixed an issue where Selec­tion View — Picked object list would add the whole object to face high­lights (PR#26589). 
  • Krrish777 improved error feed­back when a user cre­ates a Mir­rored, Lin­earPat­tern, or PolarPat­tern fea­ture (or oth­er Trans­formed fea­tures) with­out select­ing any base fea­tures to trans­form (PR#26565).

Oth­er changes:

  • Roy-043 fixed a regres­sion in Draft where an object would be dis­played incor­rect­ly when the Draft Object Pat­tern prop­er­ty is used. He also removed v1.1 Sill Height code in BIM; this was one of release block­ers (PR#26641). 
  • tetek­toza fixed an issue where the Selec­table prop­er­ty would not work on a Body in a Part (PR#25009). 
  • Wan­der­erFan applied a patch that allows the Mea­sure mod­ule to retrieve geom­e­try infor­ma­tion for Sur­face mod­ule objects (PR#26479). 
  • drwho495 fixed anoth­er topon­am­ing issue (PR#26691).
  • kevinsmia1939 added diam­e­ter mea­sure­ment (PR#24853).

Roy-043, wwmay­er, 3x380V, kadet1090, Pad­dle­Stroke, TONY8779, YashSuthar983, adri­an­in­saval, and luz­paz con­tributed addi­tion­al improve­ments and fixes.

If you are inter­est­ed in test­ing the lat­est week­ly build, you can grab it here.

PR stats: since the pre­vi­ous report, 78 pull requests have been merged (includ­ing back­ports to the v1.1 branch), and 40 new pull requests have been opened.

Issue stats: over­all, there are 3146 open issues in the track­er, same as last week. There are 4 release block­ers for v1.1 cur­rent­ly, same as last week too.


Discover more from FreeCAD News

Subscribe to get the latest posts sent to your email.

4 responses to “WIP Wednesday, 7 January 2026”

  1. Usuario Avatar
    Usuario

    Fil­let tool allows invalid radius when applied to mul­ti­ple con­nect­ed edges
    Description
    While test­ing FreeCAD 1.2.0 (devel­op­ment ver­sion), I observed unex­pect­ed behav­ior when using the Fil­let tool with mul­ti­ple con­nect­ed edges.
    When a fil­let is applied simul­ta­ne­ous­ly to two edges that are both con­nect­ed to the same adja­cent edge, and the spec­i­fied fil­let radius exceeds the max­i­mum geo­met­ri­cal­ly pos­si­ble val­ue, FreeCAD enters an incon­sis­tent or unclear state instead of prop­er­ly han­dling the invalid input.
    From a geo­met­ric stand­point, such a fil­let can­not be con­struct­ed with the giv­en radius. How­ev­er, the tool does not clear­ly reject the oper­a­tion, nor does it pro­vide an under­stand­able error mes­sage explain­ing the limitation.
    ________________________________________
    Steps to reproduce
    1. Cre­ate a sol­id with three con­nect­ed edges, where two edges share the same adja­cent edge.
    2. Select the two edges that meet at the same segment.
    3. Acti­vate the Fil­let tool.
    4. Set a fil­let radius larg­er than what the geom­e­try allows.
    5. Con­firm the operation.
    ________________________________________
    Expect­ed behavior
    FreeCAD should han­dle this sit­u­a­tion more explic­it­ly, for exam­ple by:
    • Reject­ing the oper­a­tion and dis­play­ing a clear error mes­sage, or
    • Auto­mat­i­cal­ly lim­it­ing the radius to the max­i­mum valid val­ue, or
    • Pro­vid­ing feed­back explain­ing why the request­ed fil­let can­not be created.
    ________________________________________
    Actu­al behavior
    The fil­let oper­a­tion fails or behaves unex­pect­ed­ly, with­out clear feed­back indi­cat­ing that the fail­ure is caused by a geo­met­ric lim­i­ta­tion of the select­ed edges.
    ________________________________________
    Addi­tion­al information
    This behav­ior can be con­fus­ing for users, espe­cial­ly when apply­ing fil­lets to mul­ti­ple edges at once. The lim­i­ta­tion is pure­ly geo­met­ric, but it is not clear­ly com­mu­ni­cat­ed by the tool.
    The same behav­ior is also present in FreeCAD 1.1 RC2.
    ________________________________________
    Ref­er­ences / Visuals
    • Fil­let tool, radius = 9.99
    https://imgur.com/ghPryKI
    • Fil­let tool, radius = 11.00
    https://imgur.com/MG2s4zI
    • Visu­al expla­na­tion of the geo­met­ric limitation
    https://imgur.com/fT05PCR
    • Max­i­mum pos­si­ble radius definition
    https://imgur.com/73ClvYl
    • Edge selec­tion examples
    https://imgur.com/cblv0ss
    https://imgur.com/G7xdR0r
    ________________________________________
    I have sev­er­al pic­tures that clear­ly show the sit­u­a­tion, but unfor­tu­nate­ly this blog does not allow image uploads.

    1. Aleksandr Prokudin Avatar
      Aleksandr Prokudin

      Thank you for tak­ing the time to report this. How­ev­er, this is a well-known issue with­out an obvi­ous solution.

      1. Blaise Pascal Avatar
        Blaise Pascal

        Hel­lo,
        I am not a devel­op­er, but I believe that in this case more could be done to address the errat­ic behav­ior of the Fil­let tool.

        In par­tic­u­lar, it may be worth review­ing the imple­men­ta­tion of Fil­let when it is applied simul­ta­ne­ous­ly to two edges that are con­nect­ed by a third, com­mon edge. In the usu­al case, when the fil­let radii pro­duce tan­gent cir­cles whose cen­ters lie on the same side of the com­mon edge, the algo­rithm appears to work correctly.

        How­ev­er, when a con­fig­u­ra­tion occurs in which the fil­lets have their cir­cle cen­ters on oppo­site sides of the com­mon tan­gent edge, the tool fails, even though the result­ing geom­e­try appears to be well defined from a geo­met­ric point of view.

        It is pos­si­ble that the approach used for the case where the cen­ters lie on the same side is already imple­ment­ed and works cor­rect­ly, but that this same log­ic is not applied—or does not work properly—when the cen­ters are locat­ed on both sides of the com­mon edge. Review­ing whether this approach can be extend­ed or adapt­ed to this sec­ond case could help improve the robust­ness of the fil­let algorithm.

        This imple­men­ta­tion works well.

        https://imgur.com/fDUNNJu

        This imple­men­ta­tion does not work well.

        https://imgur.com/rx66YPD

        Thank you for your attention.

  2. Michael Mulligan Avatar
    Michael Mulligan

    The addi­tion of diam­e­ter mea­sure­ment (PR#24853) may seem like a small thing, but it will save me much effort. Thank You.

Discover more from FreeCAD News

Subscribe now to keep reading and get access to the full archive.

Continue reading