nallath

That was a bug, which has been fixed already for the final release 🙂 From wikipedia: " A beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs.[9] Software in the beta phase will generally have many more bugs in it than completed software and speed or performance issues, and may still cause crashes or data loss." The 5.0 beta is feature complete, but as you have found contains some issues that we have not encountered during our tests. Software systems have become so complex that it running on all of our systems is no indication that it runs on the others. That is also why we kindly ask people to test it.

As with all issues reported so far; Please provide log files.

We're going towards a more conan centered approach. Originally we wanted to wait after 5.0 to start on it, but we ran into so many issues that we could fix with Conan that it made no sense to wait. But we are in an in between state right now, so we need to clean that up before moving on. Anyhow; Great idea to do a video tutorial! I will keep that in mind 🙂

That's the next major thing on the roadmap.

If the upper window isn't updating, that's likely a visualization bug.

None. We got a few pull requests from lulzbot in the past. That's it. I would love to have more companies contribute to Cura, as that would also make it easier for me to defend spending time on features that aren't priority for Ultimaker (since we would be getting something back for it).

Aah, yeah. But that doesn't allow you to stream gcode from cura to to the printer. That's what this is about. The first Ultimaker printer originally didn't have a way to load g-code from memory / SD card and needed a PC to constantly stream the g-code to the printer. Almost all of these have had upgrades (the ulti-controller) to no longer need that. The UM2+ was the last printer to even support USB printing in any way, but it was strongly recommended to not do this, as this generally causes a lot of issues. That's also why we're not pouring in the money needed to fix this. We support our hardware and ensure that our software works with that. We can't (and won't) provide support for our software with random third party 3D printers. There is simply a limit to how much we are giving away for free.

No, but I would argue that some of those manufacturers are parasites in the way that they handle things. I fully understand how it's annoying that you're on the receiving end of their shady business practices. I'm also starting to lean towards that yeah. I'm getting really fed up with being called a monster by some people for not fixing something.

I'm working on testing the rest right now!

Correct, but Ultimaker is paying the vast majority of Cura development. So we will focus on on things that benefit our printers.

Does the layerview show anything interesting? There are a number of views there that might help figuring out what's going on. Could you post a project file? That would help us debug it.

The same trick should work. The themes.json file also contains font sizes.

The plugins need a bit of time until they are updated, the arrows have been fixed for the final release. Thanks for taking the time to test it (even if you didn't manage to get far...) 🙂

If someone does have such a profile, please create a PR!

Well, that is the reason, sorry. Our printers don't need the z-offset, so its' simply not something that we are going to spend time on. We have to many things to do, so we have to make tough choices on what to do (and what not to do). As you might imagine, things that benefit Ultimaker printers will get priority.

WHen someone from the comunity or Anycubic creates a pull request to add the support. Cura is maintained and developed by Ultimaker, but we don't create any third party profiles.

You can only edit these in the material files themselves. It's not hard to do if you have some experience with XML. Also note that you will need to update the version number in the profile if you do this, otherwise the machine won't override it. You should also take care when doing this, since if the 3rd party material updates their settings, you will need to manually update them again (since their version nr will be lower as yours due to your changes)

We've had some reports from people that certain virus scanners incorrectly marked the application as a trojan. Perhaps that is what is happening for you?

Since you edited this after I replied: If you want to change this, feel free to contact the Python foundation and ask them to change this. But I personally do not think that we should continue supporting a product that is EOL for over two years, since it costs us a ton of money to do so and, in this case, would actually mean that we make Cura significantly slower for all users. You're free to see this as a FU, but the alternative is a FU to all the other users. If you would like to discuss having a Windows 7 build for Cura and a support contract, feel free to reach out. I'm sure that we will be able to find a price where we could provide a supported build for windows 7. I can't speak for everyone, but I think the community would appreciate this generous donation!

Cura has this, but I agree that we can make quite a lot of improvements to how we handle profiles. It's not as big as people would think. Most of the issues are in the way that the profiles are shown. I think it would be possible without a fundamental change (although it will be a big UI / UX change, wich does bring problems of their own) On behalf of OS developers everywhere; Thanks.

The old plugins are still there, just not via de website. Calm down. You can still download them as normal from Cura. There isn't a nefarious plot to "force" people into the beta or any kind of scorched earth method.

Cura 5.0 will not work on Windows 7. We have stopped supporting windows 7 as it isn't even supported by Windows anymore. This meant that when we stopped supporting it, we stopped testing if it worked (which also saved us a lot of time and effort). It kept working for a bit longer, but for Cura 5.0 we also switched to Python 3.10 (which is also one of the reasons why Cura 5.0's interface is much faster). Python 3.10 does not support windows 7, for the same reasons as us. The support for windows 7 was already ended on January 14, 2020, but we even kept supporting it a bit longer. But at a certain point, we have no other choice than to stop doing so. Updating to windows 10 is a breeze and should even be free. I would strongly recommend doing that, as windows 7 is no longer getting any security updates, which is just putting yourself at risk.

Yeah, sorry. We've been depending on OpenGL 2.0 for some time now. Did previous versions of Cura work for you?

Not without any log files, sorry! We really need those to figure out what is going on

I assume it's because you have "Alternate Extra Wall" enabled.