[FIXED] Variable settings support generation troubles

[Zapp]

When using the variable settings feature to split the model into multiple processes there is a problem with supports, where if they encompass more than one process then there will be a 1 layer gap between the processes. Reducing the separation layers doesn't fix this.

Also, somewhat connected, when using the variable settings wizard, the upper processes should have the temperature and cooling settings automatically removed or modified, because right now if I have temperature X for the first layer and then temperature Y for latter layers, the temperature X will be set again when the latter process begins even though it is not the first layer anymore. I have to manually modify the temperature in each process.

@EDIT
After some more testing it seems my first issue only happens when the layer height is changed and is not properly aligned with the height at which te process starts. I still would be nice to have a warning of some sort telling the user of this.

[ScottyMakesStuff]

+1 for me on this problem and upgrade to the feature.

I already did this for many of my prints but the missed layer is a deal breaker.

As Zapp has also mentioned, there are a number of other changes that should happen alongside the layer change to give a consistent result that doesn't cause banding or weaknesses. I'll always use 2 solid top layers to finish off the first process. My key points to ensure this for subsequent layer changes are:-

• The fist layer width to 100%
• first layer speed to 100%
• use 2 solid layers top and bottom (but not if it's the last process)
• Turn first layer cooling on

[S3D-Alex]

I’m happy to state that this issue should be resolved now in the latest 4.1.0 release. Our team successfully tested three factory files from threads mentioning this issue. These small vertical gaps in supports when using processes with differing layer heights will not occur anymore. This was just one of many improvements to the software. All of which are detailed on our Release Notes page.

Thank you for your help reporting this issue!