nallath

If you can report this on github (and provide logs), I can have a look at what is going wrong.

Yes. It's been end of life since January 2020, which means that it's been more than two years that microsoft has stopped supporting it. Would you care to finance the development of Cura to continue supporting windows 7? I would guess no. If I am wrong about that, I can get you in contact with the right people to discuss the payment options. I am sure that everyone would be very happy with your generous support of open source 🙂 Simply put; We had to chose between making Cura secure, faster and making it work on new apple machines or continue to support an outdated operating system. Not only that, it would mean a continued burden of keeping it maintained. We're not talking about a few hours of work here, but hundreds of hours. I entirely understand that it's frustrating that 5.0 doesn't support windows 7, but I don't really see a different choice.

Cura already has this, it's called "cubic subdivision". See https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/infill/sub_div_rad_add.md Profiles from machines and materials from third parties (eg; Not Ultimaker) are added because the manufacturer or a community member contributes them to us. We don't have the resources to create and add those profiles.

If you want to add new infills, you indeed need to add those in Cura Engine. You would only need very little (if any) changes to the frontend of Cura. We recently had a huge overhaul for our build system as we've had to switch a lot of things around to update certain dependencies. As such there are probably quite a few outdated instructions on the wiki, sorry for that! We are going to work on cleaning these things up. cura-build-environment is not something that I personally use when building from source. We use this to create base images for buidling our distributables. As for building things from source, I can strongly recommend you to do this on Linux, as it's so much easier to do it there.

It's impossible to say without sharing a project file. There are just too many things that could cause this.

Yes. You can already get the curapackage from https://github.com/nallath/CuraOrientationPlugin/releases Since it's a plugin that I made, I don't want to approve / review it myself. So we will have to wait until one of my colleagues does for it to be visible in the Marketplace.

Please report issues on github. You can find the link in the help menu. Thanks!

I assume that you're printing with PVA, which is a tricky material to print right. If the material stays in the nozzle for too long, it can degrade and cause the nozzle to clog. Because of that, we set the "support horizontal expansion" to 3 mm. This ensures that a minimum amount of support is printed every layer, which should prevent this from happening. It also ensures that the support that it prints doesn't fall over (as is another tendency of PVA). You can decrease that number for certain models, but it does come at the increased risk of clogged nozzles.

There is also absolutely no advantage for printers to use an ultimaker profile as the base.

His implementation is 2471 commits behind the main line of Cura. I don't know how easy it would be to port it to main Cura. If he would do that, we would love to consider his contribution! The results are very interesting as far as I am concerned.

No, not a bug. All the plugins need to be updated for the new version. I've reviewed the plugin and it still had some bugs. I expect it to be released soon 🙂

Cura 5.0 can't run on windows 7, sorry. Windows 7 has been end of life for over two years now and in order to continue to support newer systems, we have to drop support for older stuff. The python version that we need (also for security reasons) can't run on windows 7. I would strongly recommend you to upgrade to at least windows 10, as windows 7 is a security issue waiting to happen.

Download the appimage from github (https://github.com/Ultimaker/Cura/releases/tag/5.0.0) Right click on the downloaded file. Select "properties" from the context menu GO to the "permissions" tab Select the "Allow executing file as program" checkbox Double click the appimage Cura should start

That's because we don't support windows 7 anymore. It's been EOL for 2 years now, so we had no other choice but drop support.

We don't maintain or support the snap package (We also don't even control it in any way). If you want the 5.0 version, you need to use the appimage.

https://github.com/Ultimaker/Cura/issues/8229

I don't think it's so much the engine being optimized, but the profiles to slice with it that will need tweaking as well.

Qt might have been "some shit" software 20 years ago, but I don't really see what that has to do with anything. There was an issue with the performance of the beta, which is why we have a beta in the first place. That issue has been fixed for the stable release that we just had an hour ago.

Well, you don't have to call it that. But it is the build that we consider stable.

The model is likely non-manifold. It's not a guarantee that the model will fail (as you've already found). These areas can be very small, making it hard to see them.

Ah, that is a bug. But not to worry, it won't actually update any of the built in settings. It will create a new profile called "empty" (which is incorrect, but not as bad as updating the built in profile!) I didn't make the designs, i'm just repeating what part of the rationale I heard from our designer.

The rationale here is that the items in the "hamburger menu" are things that you do to the actively selected profile. The import isn't something that you do to the active profile.

Try to slice it with Cura 5.0 beta. The areas look really thin, so depending on the rounding errors, it might get too thin. In 5.0 we have changed large parts of the slicing allowing much better variable line widths.

You can.

Cura 5.0 doesn't work on windows 7