Jump to content

Cuq

Expert
  • Posts

    672
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by Cuq

  1. Yes You can have the same issue for the same printer. If you take the example of the Ender-3 the Qualities defined for this machine are based on the Nozzle Size. As you can have a nozzle from 0.2 to 1 mm a profile define for one nozzle is not necessary compatible with an other nozzle and it's not a question of Nozzle_Size but only of quality avalable for a Configuration Ie : Nozzle 0.2 quality_type = ultra quality_type = super Nozzle 0.4 quality_type = super quality_type = adaptive quality_type = standard quality_type = low Nozzle 1.0 quality_type = draft So a profile define for the 0.4 cannot be used or even imported for a 1mm nozzle
  2. Just for fun I have made a quick chart of the existing "Quality" in Cura 5.3.
  3. There is no rule to define the qualities, but globally what we find most generally is (basic quality of a general FDM printer in Cura) : quality_type = high quality_type = fast quality_type = normal quality_type = draft quality_type = coarse quality_type = extra coarse Actualy if a printer does not have a basic profile with a quality announced then the import of profile does not work (in the current case of the code of Cura). Note : that Ultimaker has also had fun creating qualities that come out of a "standard" with some machines quality : quality_type = extracoarse quality_type = slightlycoarse quality_type = superdraft quality_type = verydraft And then we have all those who have invented qualities that penalize the exchanges . Clearly the one who made the Anycubic Kobra configuration with its PLA, ABS etc qualities. had not understood anything and then penalizes the users of these machines. The other case is for Creality machines. It is a very popular printer and many profiles are based on this config, unfortunately at the time of the update of these profiles by the author of something call the CreawsomeMod the qualities defined were : quality_type = super quality_type = ultra quality_type = standard quality_type = adaptive quality_type = low This leads to most of the current problems since there is no correspondence between these names and the standard qualities. Changing these values in the current settings would not solve anything on the contrary since all user profiles would become invalid for these machines.
  4. If you cannot import the Profile it's because your printer does not have the defined quality type existing in the profile. A solution is to edit the profile by opening the curaprofile ( it's a zip file ) And by editing the Quality files which are text files. Replace quality_type = normal by = standard or one of the quality types of your printer. Some plugin can also help you. But you should keep in mind that a profile represents only a limited number of parameters, so a profile defined for a printer used on an other printer doesn't have really signification.
  5. I'm using : To find some container of a defined type . The first use of this Method is very very long and I got a lot message in the log file of the type DEBUG - [MainThread] cura.Machines.Models.CustomQualityProfilesDropDownMenuModel._update [33]: Updating CustomQualityProfilesDropDownMenuModel. Then the next use is really fast ? What's wrong and how to solved this issue ?
  6. Most of the times you can just "Disable affected profiles" it's not a perfect solution but it's still better than "Reset" : the kill button
  7. First of all try with the "Release" and not the Beta : https://github.com/Ultimaker/Cura/releases/tag/5.3.0 Then Share your project for analyse. Identical Profile doesn't mean Identical parameters
  8. Not a Bug just a normal behaviour for Cura as well for OpenScad. If you want to get a complete Cube and a complete text your must generate 2 models and merge them into Cura .
  9. Yes looks like a Bug or a Feature ? Don't know how the developpers of Cura will consider this result coming from Cura 5.3 Beta. Unchek the option "Brim Replaces Support" to temporarily solved this problem. This new behaviour looks like linked to this Parameter + a New one Call Brim Inside Avoid Margin. Brim Inside Avoid Margin.
  10. I'm very surprised that you still live in 2003 🤣 I'm sure that in 20 years you will be able in Cura to create a non repetitive pattern. By using a "Discrete Lines" definition.
  11. Even if you should not use the Tab in this case ( no need to use it) it's certainly an issue with your settings . On a basic similar case there is no issue.
  12. Bug.. Share your project for analyse .. And WorkAround solution in this case Use just a Brim and if you want to get a Brim with Several multiple layer use the postprocessing Script Call MultiBrim provided with this plugin. https://github.com/5axes/TabPlus/wiki/Postprocessing-Scripts
  13. V2.1.0 Possibility to add Name IT as context Menu . https://github.com/5axes/NameIt/releases/tag/V2.1.0 Option to Show/Not Show this menu :
  14. Yes retraction of 1.5 mm in the Gcode compatible with the parameter visible in the HTML documentation.
  15. No It's Ok for me ... Perhaps hardware dependant
  16. Same type of discussion on the same subject : One request on the Github : https://github.com/Ultimaker/Cura/issues/14564#issue-1585708583
  17. As I said if you don't want to modify the existing profile you have to Create a New Profile, then reactivate your Profile in Cura and delete the newly created profile. Or eventually use the profile analysis plugin to see the differences between the two and decide which one you will keep. If Cura proposes a new profile, it is because it detects a difference between the project data and the current profile in Cura.
  18. Here you are on the biggest problem of Cura and the point that confuses all users, both novices and experienced ones. You don't really know which settings exist in your current profile and which ones exist in the project. What you know is that the current profile is usually the most up-to-date with your latest settings, so you don't want to destroy it by overwriting this data. So you will create a new profile and 10 days later you will have 50 profiles called Best-Profile#10, Best-Profile#20, Best-Profi#39 ... But without knowing where the Best Profile is. Cura is developed by Ultimaker for UltiMaker. In this world the workflow makes sense, you use a software created by Ultimaker, on UltiMaker machines and Ultimaker filaments with profiles validated by UltiMaker, Theoretically no need to update the profile. This policy makes sense and is defensible. Now if you are not in this scheme it is more complicated. The Beta 5.3 version should improve this a bit but without conviction.
  19. Finally decided to use it via a specific plugin : Acces to the function via a Right Clic on the part (Thanks @fieldOfView ) for the sample code via his Mesh-tool Plugin. And two new Orientation Function toward the X direction - Rotate in the main direction (X) - Rotate the side direction (X) And also allows in this case to have a faster access to the functions by using keyboard shortcuts as discussed here [#22](https://github.com/nallath/CuraOrientationPlugin/issues/22)
  20. IF you don't want to define a Print Speed at the material Level .. Supress the Print speed in the Material Settings by unchecking the parameter in the list. Note : I'm not sure but it could be also a function available via a plugin : https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/MaterialSettingsPlugin And YES when you need 3 or 4 plugins to manage correctly your settings in a software there are certainly a problem of UX in Cura... But some peoples are not agree with me 🙂 The "easy-to-use 3D printing software trusted by millions of users" cannot be wrong 🤣
  21. 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
  22. 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.
  23. 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
×
×
  • Create New...