Cuq

Yes your right . Nozzle size is used to define the minimum value and maximum value of the line_width . So it could be a problem if you want to print a 1. mm line width with a 0.4 nozzle . It will be not possible to change the value . But changing the Nozzle size will not change necessary your parameters. "line_width": { "label": "Line Width", "description": "Width of a single line. Generally, the width of each line should correspond to the width of the nozzle. However, slightly reducing this value could produce better prints.", "unit": "mm", "minimum_value": "0.001", "minimum_value_warning": "0.1 + 0.4 * machine_nozzle_size", "maximum_value_warning": "2 * machine_nozzle_size", "default_value": 0.4, "type": "float", "value": "machine_nozzle_size", "settable_per_mesh": true, "children": { Unless you have in your config at the level of one of the containers a parameter that will link the line width to the nozzle size. But it's not totaly true for every parameter since Cura have switch to Arachne Engine , then some parameter like : "Wall Transitioning Filter Margin", "Outer Wall Wipe Distance" , "Outer Wall Inset", "Minimum Wall Line Width" ... are now changed by the Nozzle Diameter

If you decide to change the size of your Nozzle Size in Cura : Then the Nozzle size will be change in the Nozzle Container of your Extruder ... And finaly at the End ( Or at the TOP in the Profil Analyser representation ) the Nozzle Value is equal to 0.6.

You have a specific parameter for the Nozzle Diameter ... Most of the time it's hidden because it's in the Printer Settings section . And to have access to these parameters you need to use a specific plugin . https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/PrinterSettingsPlugin But Cura don't really care of this data , except for some specific parameter, the main parameter is the Line Width . However if you look at the inheritance scheme above and use the profile analysis plugin looking at your active configuration. You should see that this parameter is certainly defined at the printer level (as default parameter). That it may be redefined at the extruder level again as a default setting for that extruder and finally at the nozzle level which will give the real value that you can see in the Cura interface if you have installed the PrinterSettings plugin

Read the documentation : https://github.com/Ultimaker/Cura/blob/main/docs/profiles/profiles.md Use the plugin ProfilAnalyser https://marketplace.ultimaker.com/app/cura/plugins/5axes/ProfilAnalyser To analyse why the settings ( generaly the temperature ) set in the material are not updated in the Global Values. !spoiler alert! it's because these parameters have been change by the user, store in the Profile container (Custom in the bellow figure) and the value overwrites the parameter defined in the Material section.

It looks good. As 5.3 Alpha and Beta share the same configuration folder. It's good for the 5.3 Alpha Xmas version and good for the 5.3 Beta 1 version. Thanks for this update.

Test File NautilusGearCrash.3mf NautilusGearCrash.zip

Yes I'm Sorry I was Wrong this Field exists also in a regular release. And in the Beta certainly due to my Profile Issue . This parameter is Empty. So when I try to load an existing file then Cura Crash .

Because this error and this key "0.4mm Nozzle" makes me think to this field. Is it a specific value managed by the plugin? Or a Container already manage by Cura. I'm not sur but it's like if the key got a space in their name Cura 5.3 Beta crash. But it's not an issue for the other Cura Release ?

I have also with this release some crash ... when I try to load some existing 3MF file. Could have a link with the Sidebar GUI plugin (Even if it is not installed on this relase ) ... Got a message regarding a keyError "04mm Nozzle " ? Note : I have no issue with the 5.3 Alpha.

For the Windows distribution the team also forgot to include in the installation program (I installed with the exe) the language folders in I18n resources directory. So the software is only in English (even if the language setting is well adjusted.

Attention, it is in my opinion better to make a backup of your configuration if you use the version 5.3 alpha Xmas. It is possible that some profiles have compatibility problems with this new version. As the new beta and the Xmas alpha share the same Configuration folder. could be dangerous.

perhap's a begining of solution with QTimer() and isActive() but I don't know if it's really better than time.sleep

from UM.Application import Application global_container_stack = Application.getInstance().getGlobalContainerStack() or from cura.CuraApplication import CuraApplication global_container_stack = CuraApplication.getInstance().getGlobalContainerStack() Should give the same Result , But I think it is better to use CuraApplication

Certainly something wrong in your code but without relation with your analyse. It works event if Z hop are not Enable. from UM.Message import Message from cura.CuraApplication import CuraApplication global_container_stack = CuraApplication.getInstance().getGlobalContainerStack() extruder = global_container_stack.extruderList[0] retraction_hop_enabled = extruder.getProperty("retraction_hop_enabled", "value") Message(text = "retraction_hop_enabled : {}".format(retraction_hop_enabled)).show()

from UM.Application import Application extruder_count=Application.getInstance().getGlobalContainerStack().getProperty("machine_extruder_count", "value")

Hello, I'm sure there's a more elegant way to get the end of Slicing event. But I can't find it. Note : This code works but the use of timers is really not clean. If you could suggest me a more elegant way to recode this little piece of code. Goal : Load an STL file -> Start slicing-> Export the gcode and read it back into Cura import time from typing import cast from cura.CuraApplication import CuraApplication from UM.PluginRegistry import PluginRegistry from UM.Mesh.MeshWriter import MeshWriter from UM.Message import Message FileName="C:/Temp/Tube.stl" FileGcode="C:/Temp/Tube.gcode" Me = CuraApplication.getInstance() # Me.deleteAll() Me._openFile(FileName) # time.sleep(1) print("File loaded {}".format(FileName)) Me.backend.forceSlice() Me.backend.slice() i=0 while Me.backend._slicing: time.sleep(1) i+=1 print("Wait ! {} s".format(i)) gcode_writer = cast(MeshWriter, PluginRegistry.getInstance().getPluginObject("GCodeWriter")) # open wt Write and text mode with open(str(FileGcode), "wt") as stream: success = gcode_writer.write(stream, None) print("Save Gcode Ok {} !".format(success)) Me._openFile(FileGcode)

Because only the parameters it's not enough , Postprocessing can also have a influence on the final Gcode. Output at the End of the HTML file.

It's official I'm a plugin addict.

V2.0.0 To add Recycling Symbol :

You can try this script : https://github.com/5axes/Cura-Postprocessing-Scripts/blob/master/ZMoveG0.py Add A Zhop on every G0 (Retraction should be desactivated)

Use a PostProcessing Script

Note: If you also have some money and you don't know what to do with it, you can also use the services of a specialized company to do the work. But be careful about the amount for this plugin that represents about 700 files to translate and 146000 words. The rate (in France) of a translation is between 0.07 and 0.10cts/word for a common language that should not cost you more than 12000€.

The plugins are mostly created by people who are not part of the Ultimaker company, they are open source software and if people need or want to translate them, they can offer their contribution via the Github where their source code are located. As they often offer a limited graphical interface, it is often not absolutely necessary to translate them. In your case I assume you are referring to the excellent https://github.com/Ghostkeeper/SettingsGuide plugin maintained by @ghostkeeper. The text of this plugin has already been translated into some French/German/Czech languages. The texts are in editable MD format (Simple Text format) and easily translatable. Now you know what you have to do.

As you haven't give any information about your Printer I suppose that it's an Anycubic i3 Mega X and the culprit is called NilsRo : https://github.com/NilsRo That's the only printer limited to 120 mm/s and for them we have a modification between 4.13 and 5.0 New definition : "speed_travel": { "value": 100.0, "maximum_value": 120.0 }, and he made the modification here : https://github.com/Ultimaker/Cura/commit/435e9a7924cda621eb04bd9048a09df05bd9cfd2 So if you have any question ask him why he made this 'stupid' modification . 'Stupid' because at it is no longer linked with Maximum Speed X & Maximum Speed Y you need now to modify this limit in the json file ( and certainly modify for every futur release of Cura)

Note : If you want to use the postprocessing Script after the linear Advance it's certainly because you want to modify the code generate by the Linear Advance . In this case the best solution would be to modifiy the linearAdvance plugin or send a [Feature Request] to @ahoeben