ahoeben

The USB printing support is unmaintained by Ultimaker, because no current Ultimaker printers (officially) support printing over USB. So if it works for your printer, it works. If it doesn't you are somewhat on your own. My best advice is that if Pronterface works, slice with Cura and print with Pronterface.

The Materials you download from the Marketplace basically only have profiles for Ultimaker printers.

If you want to bulk-enter the weight and cost fields, there's a neat little plugin to create a CSV file you can edit in your favorite spreadsheet application and import back into Cura: https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/MaterialCostTools

I don't see this post as particularly trollish. Not everyone knows there's a plugin for this, so why not be helpful and say spread the word? (if only for others who find this post through some search). https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/ZOffsetPlugin

Export just includes the model. The idea of a "project" is that it includes the whole state of your Cura session: the model(s), all settings, and even your Cura preferences. A link would be nice, so I don't have to go searching for it.

The profiles you create in Cura always reference the default quality profile you started with. Apparently in your case, you started with the "super" profile ("Super Quality"). That way, Cura combines what you set in the profile you created with the settings in the "Super Quality" quality profile. However, there is no "Super Quality" profile for the 0.6 mm nozzle variant. If you want to experiment, you can change the default quality type your profile refers to by editing the .inst.cfg file in the "quality_changes" folder of the cura configuration folder. Look for where the file refers to "super" and change that to "standard".

There's a plugin for it in the Marketplace.

Without logs it is hard to tell what is happening. One thing that could be going wrong is that you have an old version of the Printjob Naming plugin installed. Check the Marketplace for updates.

I have made a minute pull request to make the description of the Simulation View plugin more clear: https://github.com/Ultimaker/Cura/pull/11092/files

It is not a good idea to just willy-nilly disable plugins which you don't know what they are used for. Many functions of Cura are implemented as plugins which ship with Cura. Go back into the Installed tab of the Marketplace, and make sure the "Simulation View" plugin is enabled.

With issues like this, it is really hard to guess what is going on without having a look at your logs. In Cura, go to Help -> Show configuration folder. In the folder that opens, locate the file named cura.log. Upload that file somewhere and post a link to it here.

I think you are looking for the "propertyChanged" signal of the "global stack". To connect to it, you first need to connect to the "globalContainerChanged" signal of the machine manager. So something like this (untested code, there may be typos): def __init__(self, parent: Optional[QObject] = None) -> None: (...) self._global_stack = None # type: Optional[GlobalStack] machine_manager = cura.CuraApplication.CuraApplication.getInstance().getMachineManager() # Reconnect all signals when the active machine gets changed. machine_manager.globalContainerChanged.connect(self._onMachineChanged) (...) def _onMachineChanged(self) -> None: if self._global_stack: self._global_stack.propertyChanged.disconnect(self._onPropertyValueChanged) self._global_stack = self._machine_manager.activeMachine if self._global_stack: self._global_stack.propertyChanged.connect(self._onPropertyValueChanged) def _onPropertyValueChanged(self, key: str, property_name: str) -> None: if key == "layer_height": Logger.log("d", "Layer Height changed")

Please save a project using File -> Save project... That way we know exactly what settings you use, what printer, etc. Unfortunately there is little to nothing I can tell from the low quality photo you attached.

If you save a project (File -> Save project...) instead of an stl, we'll be able to see what settings you currently use that lead to this result.

It is rather hard to see what your problem is, especially since the forum scaled down your images. Can you please describe (better) what your problem slicing is, and possibly highlight the problem in your screenshot?

No. You seem to have gotten the folder from C:\Users\<your username>\AppData\Local instead of C:\Users\<your username>\AppData\Roaming To diagnose this, we really need the folder from Roaming, as @nallath requested.

Looks like the bottom of the text that is going to be on the next layers has some vertices that are not at the exact same height as the other vertices. Hard to tell without having a look at the model.

Saving a gcode file for dual extrusion is no different from saving a file for single extrusion. "Error 0" is as undescriptive for us as it is for you, but in all likelihood the cura logs files have more information than that, To diagnose this, we need to see your Cura.log. The cura.log file can be found via Help -> Show configuration folder.

Unfortunately "modern" Cura will not let you update the firmware unless Cura connects to the printer. That means a functional firmware must already be present. The old Cura 15.04 will let you upload firmware to a more "bare" board.

you are welcome!

Once installed, the Auto Orientation plugin can be found in Extensions -> Auto Orientation

Something that may help if you find that having "a ton" of parts on the buildplate slows things down, is to "preassemble" the buildplate in your modeling program. So instead of loading one stl and multiplying that in Cura, you would multiply the model in your modeling software of choice and load it into Cura as a single stl.

I use a Core i7-7500U with 16 GB, and nothing but the integrated graphics as my main development machine for Cura, and even that works just fine.

I have never used other slicers, so I don't know how other slicers do it. I just use the tools that I have at hand.

This is how cutting meshes work. Cura can not apply settings to a part of a model only, so internally it has to cut the model into parts. One way to get much closer to what you want is to not use a support blocker cube, but load a custom piece of geometry that is modeled to overlap on precise areas only. So for example if you had a cylinder object where you only want a section in the middle to be fuzzy, you could model a "sock" tube as it were that has an inner diameter that is a fraction smaller than the outer diameter of the cylinder. Then use that as a cutting mesh.