ronvanvliet

Thanks for the reply I'm currently printing with a 60 degree angle, Tough pla and BVOH combo. Works great, expect for Cura that creates these towers. Tried to increase the angle, but the towers remain. I don't want to share the file unfortunately due to it being a new product for my company. Perhaps Ultimaker should update Cura so that the support blockers always override any type of support placement- which it doesn't do now.

to add to the above. Cura seems to want to print a support structure for an overhang above it, but it's not functional as there's a large gap between the two support placements. Even if there wasn't, I wouldn't want it to be there. See the pic attached.

Afternoon gents, and ladies Cura tends to place useless support towers in my prints that I don't want to have in there. They have no function. I can't support block them out of the print. Also, 'use towers' option is disabled. see some pics attached. Any ideas how to get rid of them? Thx

Hi Onno, it's solved. I had downgraded the firmware to the stable variant, and this solved the issue. I was just testing and I now noticed that the material switch worked fine again. I'm printing Ultimaker tough pla and basf BVOH (have been printing this combo for the past year). You will see nothing special on the touchscreen display. Just the regular pause menu with turning wheel that keeps turning indicating that it's switching materials. It also indicates in the material menu that the spool in question is empty, which is correct at that point. So, to solve the issue, downgrade to the stable firmware 👍

I have the exact same issue. But, I only ran into it since updating to firmware 8.3.. I'm running 2 ultimaker S5 printers with material stations, both have the same issue since updating. Have contacted support and will let you know what they say.

Hi, I'm running 2 Ultimaker S5 with material stations. Since firmware update 8.3 the device does not switch empty spool by it self anymore mid-print. This is happening on both my devices so I reckon it's not an isolated issue for one device alone. Anyone else having the same issue? I will downgrade back to the previous firmware in the meantime to see if this solves the issue. Any other solutions?