ahoeben

Yes, that’s intended behavior

It is also unnecessary because the Initial Bottom Layers setting does what you need. It is meant for this specific scenario.

Check the "Initial Bottom Layers" setting. The Bottom Layers setting also affects parts of the model higher up (basically anything that overhangs even slightly); the Initial Bottom Layers only affects the part of the model touching the buildplate.

You will only “get the settings” if the file was sliced with Cura, and if you open the gcode file as if it were a profile.

Cura can’t show the weight of the model because it does not know what material you will be using on your printer. If you want to be able to select materials in Cura, go to Machine Settings and change the gcode flavor to Marlin.

What printer do you have, and how did you add it to Cura? Did you use the "Custom FFF Printer" option, or a predefined printer? Can you save a project (File -> Save As...), upload it somewhere and post a link here so that we can see what settings you use?

I don't know what you mean by this. Did you install it through the Marketplace on 4.5 or not? If you installed it manually from github then you did not put it in the correct location because the plugin is not seen by Cura at all. Best course of action is to undo what you did in Cura 4.5 and just install the plugin from the Marketplace. This should work as expected on Windows. If it doesn't, post a new version of your cura.log after installing from the Marketplace and restarting Cura.

No, the UM S5 does not have the ability to resume after the printer has lost power.

Thanks for the log. In that log, there is no trace of the Settings Guide plugin being installed or its files being on your system. Did you install it from the Marketplace?

Your timing is unfortunate. Yesterday someone at UM pushed a wrong button for the wrong reason, which removed the plugin from the Marketplace. It is not recommended to download versions of the plugin from other sources, because often the versions posted are development snapshots or older versions that may no longer work with newer versions of Cura. A new version of the plugin will be available from the Marketplace shortly. I am sorry if tinkering to install the plugin may have contributed to corrupting your installation. If you could zip up the entire configuration folder (Help -> Show configuration folder) and DM me a link to it, I will see what I can do to repair the damage. Again, I am sorry you have to run into this.

The issue identified and solved in this thread sofar is specific to OS X. If you are experiencing something similar on Windows, we need logs to see what is going on. See Help -> Show configuration folder. Locate the "cura.log" file and upload it somewhere. Then post a link to it here.

Writing .hvs instead of .gcode is not something that can be done in a Cura profile. It can be done with a plugin, but writing plugins isn't for everybody; there's no guide or tutorial to follow for this exact usecase.

The file you posted looks like a normal gcode file to me. The only thing that makes it a little special is the very first line of the file. Could you try the following: * slice a file with Cura * save it as a .gcode file * rename it to .hvs (make sure it does not become .hvs.gcode!) * open the file in a text editor (eg notepad) * as the very first line, insert the following: M911 3DP-310F * save the file and try to print it

Your printer definition is incomplete; it does not have an extruder definition. Cura creates one in the background, but apparently there's something conflicting with my code when it does. I'll fix future versions of my plugin to be robust against this.

What printer definition do you use for your Lulzbot Taz? It is not a printer that ships with Ultimaker Cura. The reason I ask is that while your logs pointed me to what is going wrong, it is strange that it is not going wrong for the printers that do ship with Ultimaker Cura. I'll make future versions robust against this issue, but there may be an issue with the printer definition you use. About static text: You can type any text instead of {machine_nozzle_size} or other replacement patterns.

Have you tried printing at a lower temperature? Lower temperatures normally cause less stringing.

@Scotty-G, could you post a link to your cura.log file (Help -> Show configuration folder, cura.log is in the folder that opens)? For your printer that supports multiple filament diameters, I would set up two different printers in Cura, one for each filament diameter. Then you can just add a different static text to your custom prefix for each printer/material diameter if you want.

Please try the 4.5 beta. It has some changes in it that could fix this issue.

@imcarterschmidt could you check the Cura 4.5 beta, with that plugin enabled? A third party component in that plugin has been fixed/updated by UM, which hopefully fixes these performance issues.

I'm not sure if I love or hate that trick with the Cyrillic S. Probably both 😉

Now I'm curious. What did I do?

Perhaps if you post a link to a working .hvs file, we can have a look if writing to or converting to that format can be easily supported.

An updated version of Sidebar GUI (4.0.7) has been posted to the Marketplace, which adds compatibility with Cura 4.5, fixes a couple of bugs and adds a toggle to switch between perspective and orthographic projection. Subtle changes. Edit: See the shiny new web-based Marketplace: https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/SidebarGUIPlugin

Aww, thanks for mentioning me 😉

What is happening is that the model is broken/unsuitable for 3d printing. I'm guessing the model has infinitely thin walls, ie the walls show white on one side and blue-ish on the other (in sketchup; did I guess correctly?). All walls need to have thickness to be printable, or Cura will get confused about being inside the wall or outside the wall.