A prerelease version of the Sidebar GUI plugin for Cura 5.2 is available here:
https://github.com/fieldOfView/Cura-SidebarGUIPlugin/releases/tag/v4.4.1-DEV
- 3
- 1
A prerelease version of the Sidebar GUI plugin for Cura 5.2 is available here:
https://github.com/fieldOfView/Cura-SidebarGUIPlugin/releases/tag/v4.4.1-DEV
Thank you sir. I miss it when it's gone.
I see, thanks for testing. These are exactly the type of issues why I have to create a new version of the plugin for each release of Cura.
Probably best to log issues like this at https://github.com/fieldOfView/Cura-SidebarGUIPlugin/issues
edit: fixed the issue here:
https://github.com/fieldOfView/Cura-SidebarGUIPlugin/commit/48bad5e98812757ba47b6bec877912ed265a3feb
Edited by ahoebenBroken, the monotone order of the top layer (((
Hey @qwerty8224,
Do you have a project file for us that illustrates your problem?
To save a project file go to File -> Save project.
If you have a clear example I can bring it up to the team.
Thank you 👼
13 minutes ago, MariMakes said:Привет@qwerty8224,
У вас есть файл проекта для нас, который иллюстрирует вашу проблему?
Чтобы сохранить файл проекта, перейдите в Файл -> Сохранить проект.
Если у вас есть наглядный пример, я могу донести его до команды.
Спасибо 👼
Thanks @qwerty8224, I'll take a look.
@Cuq about the spiralize behavior. We restored the behavior from Cura 4.13. We received a lot of requests to bring the old behavior back, so what you are seeing is intended.
Hello @MariMakes,
Yes you are right, It's the same behaviour. Sorry for the confusion.
@Cuq No worries, we are happy with any feedback.
I had to doublecheck it myself aswell!
Spiralize behavior in 4.13 - 5.1 - 5.2 Beta
Would like to test and give feedback but the linux appimage doesn't slice. There are already a couple of bug reports on the cura git and it also seems to affect MacOS users. So no non-windows specific feedback this version I guess? All I can say is that the latest version of the sidebarGUI-plugin is working fine as always. Thx for that again.
@qwerty8224 we found what caused the issue with the monotonic top ordering and intent to fix it for the 5.2 stable release. Right now it will introduce a lot of unnessecary stringing. Thanks for reporting so quickly 🎉
Hey @ungutknut,
We are aware of the Linux Beta builds not working. 😥
It seems to be because some libraries are not included.
@Piezoid did some excellent investigation work here.
We have our developers working on a fix, you can follow their progress here: https://github.com/Ultimaker/Cura/issues/13422
I am getting""object of type settingfuction not json serializable" when trying to send stl to printer via octoprint
Octoprint is a plugin from a contributor. You can make a bug report or ask him for guidance on his GitHub Page.
2 hours ago, GregValiant said:Octoprint is a plugin from a contributor.
It is, but in this case the bug is in Cura, not in my plugin. The problem is with the creation of UFP files, which the OctoPrint Connection plugin uses when the OctoPrint instance supports that format for displaying thumbnails. Fortunately it has been fixed in time for the stable release of Cura 5.2:
Update for the Linux users encountering slicing troubles.
There are new builds with a fix available here: https://github.com/Ultimaker/Cura/releases/tag/5.2.0-beta
Thanks for reporting 💪 and happy slicing 😄
Unfortunately, the bug regarding the support interface layers still seems to exist.
There are still several places where the outermost layer is sporadically not supported.
the strange thing is, i haven't seen another thread about this yet. you would think that this problem regarding support generation with a dual extruder printer would be reported more often...
I have taken more pictures of this.
I will also attach them to the github thread I created for this.
Bad generated support structure · Issue #12839 · Ultimaker/Cura · GitHub
@Gero could you put up a project file of that? I can't reproduce it just playing around here.
@GregValiant of course! the print settings for the object can be generic or customised here, the problem with the support interface layers exists regardless of any settings.
You're going to love this one.
I can duplicate this with your printer active, and with my virtual Dual Extruder Ender 3.
Here is the image with my printer.
This is with your printer and is a view I'm sure you are sick of.
And here it is all fixed.
I was going to make you look for what I did but I'll be merciful and tell you. I changed the Initial Layer Height to .28. I'll go and leave a note on your bug report on Github.
Recommended Posts
eac 1
I have the same question - Bug or Feature? - but about something else: about monotonic order algorithm...
If until 5.1.1 the moves are in very clear order, in 5.2, the nozzle makes a lot, and I mean a lot, of travel moves.
Of course, this give me longer print times.
Are there any other extra settings now, related to monotonic order of the moves?
Link to post
Share on other sites
GregValiant 1,415
I'm very, very pleased by the release. 5.1 was reminding me a lot of 4.9 and that is not a good thing.
Link to post
Share on other sites