Maybe, and please don't get this wrong. Without autoslice or with it... umm for example disabling the block on the autoslice for this situations, and enabling a per layer height z area check for the first 4mm might solve some issues.
Also maybe a visual inspection of the resulting gcode lines could show RED areas or some warning and it could block the gcode save/print.
So umm. A basic idea. Force autoslice for the first 4mm and do checks on that info, if that gets an ok the program can continue slicing normally. If that fails the User can see what parts of his gcode are hitting or beyond print area.
Recommended Posts
nallath 1,124
All of that is done because testing something in 2D is way more easy compared to doing it in 3D. It's a whole order of magnitude that you have to add.
It might be possible to add such a thing in the future, but don't expect it soon.
Even if we were to implement it, it would cause other issues besides the whole 3D being hard thing. Your first image for instance will cause issues if you suddenly enable support.
Link to post
Share on other sites