Cuq

Like : https://github.com/5axes/CustomSupportEraserPlus

In such case ( and if the design of the part is the real final design and not a sample part) I would use a Cylinder as Cutting Mesh Modifier for the bigger cylinder.

In Special Modes switch the Surface Mode to Both

When it's a "Bug" in Cura, Cura Master, SuperSlicer, PrusaSlicer BambuLab Studio and IdeaMaker You need to call it "Feature" and "Feature Request" 🤣

You can use the Skin Overlap Value to change the overlap position between yellow and Green line.

As your wall need just two lines to be print, set your Wall Line Count to 2 and it should be OK. And it will not change the strength of your part.

Ctrl + [Scroll]

This models is designed to be print with a maximum of 3 Wall Line Count not 5 . If you use the recommended settings for this model you should not have this issue. https://github.com/5axes/Calibration-Shapes/wiki/Bridge-Spiral-test 3 Wall Line Count

J'en peux plus... 🤣

You are upgrading from version ? To 5.2

As your model is made of small elements, you can split the model into parts ( by using the MeshTool plugin) and remove the defective model (the 46 I think)

Uncheck Remove All Holes in MeshFix

Not exactly what I'm looking for but jut a little step further. def _onSceneChanged(self, source: SceneNode) -> None: new_scene_objects = set(node for node in BreadthFirstIterator(self._scene) if node.callDecoration("isSliceable")) if new_scene_objects != self._scene_objects: Logger.log("d", "New_scene_objects") self.StandardFixed=0 self._scene_objects = new_scene_objects

Very interesting piece of code... @nallath is there any solution to detect if the geometry have changed . I was using in one of my plugin : self._scene = CuraApplication.getInstance().getController().getScene().getRoot() #type: Scene Root self._scene.meshDataChanged.connect(self._onSceneChanged) but it also detect if we change the position of the part position on the buildplate or any modification set on the meshData.

That's normal , it's working as intended , the first layer are print with the value set in your profile. Before this layer this is the normal cura setting condition.

It's the case. You received an email on the email box you have define in your ultimaker account

https://github.com/5axes/Calibration-Shapes/wiki/Retract-Tower#note

Use not a Brim but a Skirt with 0 for the Skirt distance

OpenGl 4.0 Should be ok to get an access to this function.

I don't know if it's still the case but I've notice that the minium release was OpenGl 3.2 to have this function. But a release 4.1 is recommended as minimal configuration. To get more information on the current driver of your graphics card on Windows you can use an utility Tool like GlView : https://www.realtech-vr.com/home/glview If you also use an othe slicer like PrusaSlicer or SuperSlicer in the System Function you can have this information. ( Should be also a function of Cura as many issues comes from this limitation , but it's not the case right now )

Certainly because your graphics card is not compatible, must support the right OpenGl version.

An open discussion on this subject : https://github.com/5axes/Calibration-Shapes/discussions/77 where the user want to use the M109R instruction to measure the "ooze blob diameter" but I'm not very fan because changing the temperature in a print is not a very common situation execpt between the first layer and the other one or on multi-filament peint but in this case it's an other problem.

This type of request doesn't really make sens : In a temptower usualy we start from the higher temperature to the lower and so the changing time in this case as the machine is extruding material is very short. By the time you are printing the inner contour of the first layer you will have reach the new temperature. So you will not see the difference on the part. Using a M109 S code to wait the right temperature is also useless. This code are waiting that the nozzle have reach the programmed value. But as you are always at a temperature higher than the new target value, the machine doesn't wait anything and using M104 S or M109 S doesn't change anything in a temptower print style program. To wait the decreasing target you must use the M109 R code. https://marlinfw.org/docs/gcode/M109.html But this is not the choice I have made in my script because user must be able to fix a negativ or positiv increment (even if on a pratical point of view it's always better to decrease the value )

I don't really understand this needs of two scripts. Anyway concerning the retract tower you need to have two different print, one for the retract length and one for the speed. So you need to modify the script according to the parameter you want to test. It's a normal behaviour. But you don't need two "scripts" ?