nallath

That's because your layerview is in compatibility mode. This happens because of two reasons; You either selected this in preferences or your graphics card doesn't support opengl 4.1. It could be that your computer has decided to use the onboard graphics card instead of your "real" graphics card, which could cause this. Most drivers have an option to force that the GPU is used for certain programs, but that is something you need to setup yourself.

True, but it was moved to a high enough prio today so that we could work on it.

Damn, you beat me to it 😉

I can't say more about it than "We're aware of it and looking for a solution", sorry.

Not as far as I know. Cura is created to work as a desktop application. Porting it to web technology is going to be a pretty tough nut to crack.

But did it generate g-code outside of the buildplate? The issue reported is about UM3 and the bounding box it generates, so i'm pretty sure it's a completely different issue.

There is no way to do that in Cura.

If it saves to UFP by default on an ender, that's a bug. Could you report that on github?

I think you seem to not realize how much time it would take to do what you suggest. Ultimaker has grown quite a lot the past few years, but there is a limit to the amount of testing we can do. So that means we have to make choices. Which also means that we don't test on every single setup that we theoretically support (or even close to that). That being said, there have been multiple issues with OSX in the past with speed. Some of them are actually completely out of our control as they were caused by the framework we used (and the smouldering hatred apple seems to have for developers). This in turn leads to us not even being able to support older OSX versions because we can't build for them (or if we did, we'd have to spend so much time and money on it that it would cost far to much). So yeah, I get the frustration. I really do. But calling people out when we are trying to resolve your issue isn't helping (and especially not if they, unlike me, aren't even paid to do so ;))

We're using the default file dialog as provided by your operating system. So if that dialog can't do it, there is little we can do to change that.

Could you report the issue on github (https://github.com/Ultimaker/Cura#logging-issues)

It's still stupid as hell that OSX is basicly not giving you what you ask for. I asked for a cola, not a pepsi 😉

That would be one of the solutions yeah.

It seems like that you have encountered an issue caused by the drivers of OSX. See https://github.com/Ultimaker/Cura/issues/4505

It seems that the print size that Cura generates is a bit too big, so that's likely the culprit. I've added the issue to our backlog!

If you remove the old version first, it asks if you want to remove everything. If you just install the new version this shouldn't happen.

Could you fill in a bug report on Github? You can find instructions on what we need to debug your issue on https://github.com/ultimaker/cura#logging-issues

So you need to add a home command to the start g-code of your printer.

Could you save the gcode locally and share the header of the g-code? (open the g-code in a text editor and the copy the lines between the start and end header label)

You would need to change coded procedures on the machine for that to work. It is something we are working on to improve.

The backups plugin is tuned a bit too paranoid, so right now it only accepts data from the same version of Cura. it's something that is on our backlog to fix and i hope to be able to fix it for 4.1 That being said; there are a few things you can do. The easiest one is clearing your 4.0 data, install 3.6 on the machine that needs to receive the data, restore the backup there and then run 4.0. The upgrader should then try to convert the 3.6 files to 4.0

Nope, this is currently not supported. This is also something that isn't that needed for Ultimaker printers, so it's very unlikely that we will spend time on it (we being "Developers paid by Ultimaker"). But as always; Pull requests are welcome!

There were some fixes, but those were things that have been contributed. @Smithy is right with regards to us not really touching the USB printing.

Could you create a bug report on github and fill in the template? We need a bit more information to diagnose the issue.

Did you click the button to reset your profile because of corrupted settings? If so, cura zipped your settings so they won't cause this corruption. You can find it by going to help-> show config folder and then navigate one folder up. Alternatively; it could be that you selected the option to remove all profiles when uninstalling cura 3.6. In that case, your settings are lost, as per your instructions.