Browse Source

Fix whole output of nest2d was translated.

By default, the alignment would cause the entire mass of objects to have its center of gravity to be at the origin, including any fixed object. So there was an unwanted 'whole space' translation that we didn't take into account could occur beforehand. Fortunately, there's an option to just set it not to re-translate the whole space. It's unlcear to me how this would've worked in 5.2.2 and prior (and it did ... somehow), since we didn't change anything, including that default, as far as I can see. Anyway, the arrange function can handle 'fixed' objects again (as in loading them in one by one, or loading in a whole bunch of files instead of just 'arrange all').

CURA-10476 -- should fix #14838
Remco Burema 1 year ago
parent
commit
6a5a9e70af
1 changed files with 1 additions and 0 deletions
  1. 1 0
      cura/Arranging/Nest2DArrange.py

+ 1 - 0
cura/Arranging/Nest2DArrange.py

@@ -99,6 +99,7 @@ def findNodePlacement(nodes_to_arrange: List["SceneNode"], build_volume: "BuildV
 
     config = NfpConfig()
     config.accuracy = 1.0
+    config.alignment = NfpConfig.Alignment.DONT_ALIGN
 
     num_bins = nest(node_items, build_plate_bounding_box, spacing, config)