ahoeben

You can have 5.2.x and 5.4.x installed on your computer side-by-side. When you install a new version of Cura, it will make a copy of your configuration in the previous version, and the new version will start using that copy. The configuration of the older version will stay intact. In previous versions of Cura, installing a new version of Cura would ask you if you wanted to remove the previous version(s), and if you told the installer to uninstall an older version that uninstaller would ask you if you wanted to remove the settings from that old version. If you choose both to uninstall the older version AND to remove all its settings data, then you would loose your previous configuration. TLDR: if you want to have both versions side by side, then don't uninstall the older version, and whatever you do DO NOT let the uninstaller remove the settings from the older version.

Coasting is the answer. You can read about the setting here: https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/experimental/coasting_enable.md

The prefix is normally derived from the printer type (Anycubic Vyper in your case, I guess). There are a couple of plugins in the Marketplace that let you customize the prefix and the rest of the printjob name. As the creator of the Printjob Naming plugin, I am partial to that one: https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/CustomJobPrefix

I don't know why that would be happening to you, but you can always download the latest release of the plugin here: https://github.com/fieldOfView/Cura-MeshTools/releases Download the MeshTools_v3.7.2_Cura5.0-current.curapackage, and drop the file onto the buildplate in Cura as if you were opening a 3d model.

Not all ABS is created equally (really!), so this is hard to say. (Color) additives may play a big role. UV light is also not the only enemy; 3d printed objects can have many nooks and crannies where moisture can build up and either create a nice atmosphere for algae and moss, which may speed up deterioration, or which will lead to mechanical stress when temperatures go below 0.

So, did it work?

But do you really want to risk the failure of a big print over the cost of a new sd card?

Anything you change or add should ideally be outside of the application bundle. The reason there are no def.json files in the configuration folder is that you have not made any (in the proper way). Adding and editing files in the application bundle has a number of disadvantages: * If you ever want to use a newer version of Cura, you have to remember what changes you made to the application bundle and you have to make them again. The configuration folder should be automatically copied and upgraded by the new version of Cura. * If you make an error when editing files in the application bundle, there is nothing Cura can do to repair this. If you make an error editing files in the configuration folder, at worst you have to reset your configuration. * You have to be an elevated user ("administrator") to edit files in the application bundle. Editing the fdmprinter.def.json file is a bad idea because it applies to ALL printers. The fdmprinter.def.json file defines all settings in Cura! Copying the fdmprinter.def.json file is a bad idea because you would have to figure out what changed in fdmprinter.def.json when you want to use a new version of Cura and apply them to your copy. You do you, I am not going to stop you.

If they were the same, then why would we need to have both? Here's a good article from the Settings Guide plugin on the subject of missing parts: https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/troubleshooting/missing_parts.md Either the details are too small to print with your current configuration, or your model is faulty ("non-manifold"). From just the screenshots, it is hard to see which of these two options is the problem here.

I think you may want to try grouping instead of merging. In Cura, merging is functionally mostly the same as grouping and putting the origins together.

The 3mf is in a different orientation than the gcode. Is the gcode the actual gcode you printed?

Try lowering the "Maximum Resolution" setting (under Mesh Fixes) to 0.2 or even 0.1.

Out of curiosity: who is this "we"? I mostly see you saying this. Cura 5.4 works fine for my prints. That does not mean that it does not have any bugs, but those bugs don't warrant a "don't use 5.4" response on every unrelated issue people run into.

Copying the fdmprinter.def.json and starting from that is a bad idea (almost as bad as editing fdmprinter.def.json directly). Don't do it, you are only making your life harder. Instead, you are much better off by making a copy and editing a simple definition like the 101Hero or the 3dator. They reference the fdmprinter.def.json file. You don't need to add variants (and "has_variants" is false by default), but you should really create an extruder (even if your printer only has one). See the corresponding .def.json file for the 101Hero or 3dator you started with (and see how it is referenced in the main .def.json file).

The supports you make in Meshmixer are not really designed for FDM printing, but for resin printers. Ofcourse you can try them out, and your mileage may vary, but they are not great for printing with filament printers.

It means that the printer is actively connected to Cura and you can send gcode files to it (as opposed to a printer that is not connected and you have to manually transfer a gcode file to it).

Try lowering the `Maximum Resolution` setting (under `Mesh Fixes`) to 0.2 or lower.

If - like me - you cannot get the 5.5 alpha to slice anything, you may want to try disabling the new CuraEngineGradualFlow plugin.

Yes, but it is not up to Cura to decide which GPU to use. You can normally select which GPU to use via the driver of the GPU. This should be a helpful article: https://helpdeskgeek.com/how-to/how-to-switch-between-dedicated-gpu-and-integrated-graphics/

This should help you: https://support.makerbot.com/s/article/1667417981430

Actually the path does not go outside the buildplate.; the brim and skirt are now truncated to the buildplate, precisely to prevent those grey areas that people did not understand. It is a feature, not a bug.

The "Save as TFT File" functionality is provided by a 3rd party plugin, and it seems that that plugin does not let Cura apply its postprocessing to the output.

I am sorry, I actually have no experience with the Conan workflow.

I will try to reproduce your issue and see why this is happening. Do you have any other plugins enabled?