nallath

The UM3 profile isn't there yet. You will have to wait a bit for that, sorry.

But at that point it is an explicit action by you, right? The point is that it having printers that can go above 360 are pretty rare. 99%> of the machines simply can't reach those temperatures and if they did, it would cause safety issues. To give a bit more information about this; We have a security company doing regular audits for our software. This was one of the things that they noticed. They came up with the following scenario: If a malcious actor makes a project file / profile with extreme high temperatures, they could use that to cause a lot of damage to the machine (or even burn it down). Certain materials are even toxic at this temperature. So in order to decrease the impact of this attack vector, we set the max to what Marlin itself sets, which is pretty much what most firmwares handle. Cura should do that already. It doesn't upgrade quality files, but the definition files should be migrated. The reason that this isn't an issue for the build volume enclosure is that it can't actually reach those temperatures. But you are probably right that we should add a max temperature there as well. Anyhow; If it's one printer that you constantly print for (and others use that same printer as well), the best option would be to contribute those files. That way they are always there and everyone can use them.

It's not up to me to give an answer to that (being an engineer). But if a party would be interested in this, I'm fairly sure that Ultimaker would at least be willing to discuss / consider such an arrangement.

You're not doing something wrong! I also don't quite now what is going wrong for you. Could I ask you to report this issue on our issue tracker? You can find it here: https://github.com/ultimaker/cura/issues/

What do you have loaded in your second extruder? Try disabling it. The profiles you see there are formed from what both extruders support.

Your firewall / VPN is preventing the connection to the engine. Try disabling those (or preferably; add an exception).

You can find that here: https://github.com/Ultimaker/Cura/wiki/Profiles-&-Settings

Well, yes, that's because there is no quality profile for the CC core and ABS. The not supported basicly means that it doesn't have a pre-defined quality profile and will fall back to more generic results (hence "not supported" and not "not allowed")

Without logs, there is really nothing we can do to help you. As i've said before; Please report issues on github and fill in the bug template. We ask people to do that because you need to help us in order for us to be able to help you.

Sorry, but this has nothing to do with upgrading at all. Anyhow; What is going on is that each machine can define a set of qualities that it supports. If you create a profile, you basicly create a "delta" profile (eg; Take the 'draft' profile and apply these changes to it). As such, that profile is tightly coupled with the profile it was based on. If you try to load that profile on a different printer and that printer does not have that quality type, it can't apply that profile (because it doesn't exist for that printer!)

https://github.com/andrewmolyuk/cura-cli

The IDEX system won't work with 4.9.1 (or well, any version of Cura released by Ultimaker). BCN3D hacked that into their version and I think that's why they don't update.

That's definately not part of the solution. We bundle cura with a specific version of python and that is the one it uses. Could you also report this on our github? It's a lot easier for us to keep track like that.

Your firewall is blocking connection to the slicing.

Your graphics card is probably outdated (or the drivers are). If cura is running in compatibility mode, you won't see the horizontal slider.

What does the g-code look like? At first glance i would also blame coasting.

This shouldn't be a problem for 4.9.1 anymore

4.9.1 is out with a fix.

Cura isn't compiled for ARM, so apart from compiling Cura yourself, there really isn't a trick.

If the UM2+ suffers from underextrusion you should probably replace the teflon inset. As far as the spiralize, we've not gotten any reports that it was broken. Could you share a project file that exhibits the problem?

Yes, but unfortunately, other things have been inserted above it. If people want this faster, the only thing that can be done right now is writing a pull request.

That's not a fix. We've disabled one at a time on purpose if you use more than one extruder, since we didn't implement the extra algorithms that it needs to work.

We missed the dual extrusion issue. It's something that we should have caught but didn't. Since a lot of people have also reported this on github (thanks for that!), we already have fix for this and have changed the tests that we run per release so that this shouldn't happen anymore. We do print a dual extrusion model every release, but the model that we used didn't exhibit the problem (Which was unfortunately one of the few models that didn't have the issue...). As people might have noticed, we also didn't get any reports about this during the beta (which is unfortunate, but the primary responsibility for it not being found is with us and not with the beta users!) We've also found a fix for the X:/ drive issue, which should also prevent the slowdown that some people experienced. As you might have noticed, it's a bit hard to keep track of things on the forum, so please provide bug reports on our issue tracker on github (and again thanks to those that did and helped us find out what was going on). An update for 4.9 is almost done and should be out soonish.

Maybe those people used Cura 4.9.0? We upgraded a number of things so big sur would be supported better. Also; as a developer, knowing that it doesn't occur with everyone is actually a helpful bit of information.

Yeah, we messed up there. Even though we test dual extrusion models for every release, the model that we used to test it didn't show the issue. We've fixed the issue for 4.9.1 and have updated our test procedure so we will catch it next time. I expect that 4.9.1 will be released this week.