nallath

Ok. Have fun with Prusa Slicer.

No, it's the name of the profile on disk without the extensions

I don't think so. If you add an exact match to the ID in that list it should be excluded. But a custom material can have any ID, so there isn't really a way to know for sure that you "got all of them"

I've just approved a new version of the plugin. The developers of thingiverse seem to have broken someting (yet again) that required a fix from the plugin side.

You probably need to upgrade your graphic card drivers or make sure that the right graphics card is used by Cura. Laptops tend to switch to the slower (but more energy efficient) graphics card. These often don't support as advanced features, which is why the slider bar isn't shown anymore.

_populateMetadata is being called in the pluginRegistry. It's used in "getMetaData" and in "loadPlugin" I don't know what you did in your code, so i can't really help out entirely with what is going on. If you have a public repo somewhere, I could have a look. You could have a look at the https://github.com/tetonsim/is-cura-ui/blob/master/SmartSlicePlugin/ if i recall correctly, they also use multiple views.

Have a look at the "combing strategy" setting. If you set it to "not in skin" it should be a lot better.

If you have flat top surfaces, those are the areas that you want supported by infill. Otherwise you might get sagging areas. The bottom generally doesn't need this as it's printed on the bed.

https://support.ultimaker.com/hc/en-us/articles/4402996140946-Ultimaker-Cura-crashes-when-opening-any-file

Yep, this is a known issue. Objects lower than the initial layer height are not sliced.

If you have feature requests, this is not the place to put it. Please read the original post. Cura won't provide support for Resin printers.

The warnings disappear after 30 seconds. If they don't, please report it on https://github.com/ultimaker/cura/issues/

You can hide them. This is what my plugin does for a view that needs to be hidden from the users. This is part of the getMetadata() of the root init of the plugin "view": { "name": "Chop", "view_panel": "", "visible": False }

Not entirely, but it's an area where one has to tread carefully yeah.

If the printers are of the same type, currently the best solution is to reload the project file. We are working on a better flow for this.

It's the first time I've heard about this. What makes you think it's the duplicate functionality? This looks more like a bed leveling issue. If your bed isn't entirely flat, the center of the bed (aka; the first item) will print best.

If you don't provide logs, there is no point in reporting issues. This might sound a bit harsh, but we really need them to figure out what is going on.

Did you check if "support brim" is enabled?

1) See See https://github.com/Ultimaker/Cura/issues/10548 for more info 2) Yes. If you have a .curaplugin file, you can manually drag it into cura. 3) The Meshtools plugin also allows you to do this. Those slicers can not read your cura profiles. Cura can also not read their profiles.

Well, we've formally stopped supporting windows 7 as it's end of life (it's not getting any support / updates from Microsoft either).

See https://github.com/Ultimaker/Cura/issues/10548 for more info

Bridging settings are under experimental. The language of the application can be set under preferences.

Yes. It seems that not all windows machines got the new certificates (https://twitter.com/hmoffatt/status/1443848907893592072). It worked on my own windows machine after i installed the pending updates, but i'm not entirely sure that was it, since one of my colleagues has an up to date windows where it didn't work.

Because you use the {material_print_temperature} instead of {initial_material_print_temperature} replacement tag in the g-code (or well, that's what I think is going wrong)

That's because your start-gocde probably sets the printing temperature and not the initial printing temperature.