mirror of
https://git.mirrors.martin98.com/https://github.com/Ultimaker/Cura
synced 2025-08-12 03:49:00 +08:00
Fix loading machine specific materials
The container registry was incorrectly being searched with a variant_name == None, which always returned an empty printer-specific materials list. As a result, the generic material settings were always being loaded if there was no variant specifically indicated inside the fdm_material file. The printer specific values were consistently being ignored. This commit fixes that by removing the search with a variant_name==None which correctly returns the printer-specific materials list while loading the materials from the variant nodes. CURA-7087
This commit is contained in:
parent
601a765f73
commit
d5cfca4df0
@ -51,7 +51,7 @@ class VariantNode(ContainerNode):
|
||||
# Find all the materials for this variant's name.
|
||||
else: # Printer has its own material profiles. Look for material profiles with this printer's definition.
|
||||
base_materials = container_registry.findInstanceContainersMetadata(type = "material", definition = "fdmprinter")
|
||||
printer_specific_materials = container_registry.findInstanceContainersMetadata(type = "material", definition = self.machine.container_id, variant_name = None)
|
||||
printer_specific_materials = container_registry.findInstanceContainersMetadata(type = "material", definition = self.machine.container_id)
|
||||
variant_specific_materials = container_registry.findInstanceContainersMetadata(type = "material", definition = self.machine.container_id, variant_name = self.variant_name) # If empty_variant, this won't return anything.
|
||||
materials_per_base_file = {material["base_file"]: material for material in base_materials}
|
||||
materials_per_base_file.update({material["base_file"]: material for material in printer_specific_materials}) # Printer-specific profiles override global ones.
|
||||
|
Loading…
x
Reference in New Issue
Block a user