Msuurmond

It now serves the right version, sorry for the delay

No we have our own repo for packages

Hmm indeed that is wrong. I have asked to see why master isn't served.

Was still waiting for a review. Just review&merged it, should be online in 5 minutes.

Why do you think this is the case?

CuraEngine is even more separate from Cura than a plugin. That is why we can have Cura with LGPL and CuraEngine AGPL

No it is not planned for the near future.

No the engine is a separate program so the AGPL doesn't 'infect' programs that use it. For Cura every contributor but 1 agreed on our proposal to move from AGPL to LGPL. Once this was done, we didn't need to change the license of the Engine anymore because plugins work together with Cura and not the engine.

Could you share your whole config folder as a zip-file? Than we can use that to reproduce it on our development machines.

I don't see anything weird in the log file. It stops after initializing the shaders so maybe see if there is an update for your videocard drivers. We hope to start Cura 3.4 Beta in a week or 2.

That Cura has to work harder to show (render) the model and gets more laggy and that you might have tiny lines of GCode that might cause buffer-underruns in you printer. This might be the case when the line of GCode can be executed faster than a new line can be put into to buffer.

We investigated this issue and it was indeed the maximum resolution setting. To make it work please change the 'Maximum Resolution' to 0.01 and than it will work. We use the default of 0.04 which helps on less powerfull hardware and is prevents buffer underruns on the printer.

@Drdave That is the correct content! I used it to run Cura 3.3.1 and it works here (on my MacBook). I also see you have some plugins installed, it might be that your Octoprint plugin needs an update. To get Cura running again you could try to delete the folder OctoPrintPlugin: When Cura runs again you can redownload it from the plugin browser.

Got the file, but this is still only the cache folder. We need this folder: $USER/AppData/Roaming/cura/3.2/

Ok I got the files, but I only see a 'cache' folder in the zip-file. We need the whole 3.2 folder e.g.:

A few options: - You could use https://wetransfer.com/ to upload the zip to and share the link here so we can download it. - Rename the zip-file so it doesn't end on .zip but on .3mf for example

We can only help you further if you can give us the complete config folder. With that we can extract it on our development machines and create the exact same situation as you have. If anything goes wrong we can than see it and fix it.

We just released a bug-fix: https://ultimaker.com/en/products/ultimaker-cura-software

We just put Cura 3.3.1 on the server. Please update https://ultimaker.com/en/products/ultimaker-cura-software

Can you try: https://stack.mybacklog.info/s/OdSi5xGBeTjwNAf ?

Could you please send the whole 3.2 folder?

It looks like Cura 3.3.0 thinks your profiles are not correct/compatible. Could you zip and share your profiles folder?

You could check this to see if your config is still there: https://github.com/Ultimaker/Cura/wiki/Cura-Preferences-and-Settings-Locations

Could you create a bug report https://github.com/Ultimaker/Cura/issues ? That makes it easier to fix for the devs.

Yes we just found out of this bug after the release and are working on a fix. Sorry!