-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Support material adhesion by base type interface layers under soluble supports. #5823
Comments
Just a moment ago I saw, that I uploaded the wrong Class files. Some functionallity is commented, sorry for that! |
Commenting removed and a fix for excess layers done. The index for the top_z/bottom_z discriminators uses the interface layer number. Since indexes usually start at zero, the number needed to be reduced by one. A picture of a first print: Done with a Craftbot Flow IDEX XL. No wipe tower, just used the wipers of the printer. It reduced the number of head preparation and therefore time and material costs by about 50%, even for this narrow top to bottom distances. The tiny dot of polydissolve on the bed is introduced to overcome a bug of PS for the multi extruder toolchange. |
Now provided as pull request combined with changes under #5903. |
At the moment soluble support material adhesion is weak due to sparse support layers under soluble support layers. I reported as issue prusa3d#5823 with pictures, as well. I modified two methods to the SupportMaterial Class including their headers. The new methods add two base type interface layers to the support structure, in case the extruders are different and soluble support is choosen. Since it is conditionally activated, it in general doesn't need a GUI input. But a GUI option number of base interface layers may enabled users to adapt this feature to their needs. This is my second try to provide a pull request on this topic. Reset my fromer repository, because first I merged this and all other changes to my master and couldn't provide separate pull request anymore.
under soluble supports. #5823 Implemented as a pull request #5903 by @spiky2021 and reworked. commit c7993e6 Author: spiky2021 <[email protected]> Date: Thu Feb 11 12:39:25 2021 +0100 Base type interfaces for soluble interface supports At the moment soluble support material adhesion is weak due to sparse support layers under soluble support layers. I reported as issue #5823 with pictures, as well. I modified two methods to the SupportMaterial Class including their headers. The new methods add two base type interface layers to the support structure, in case the extruders are different and soluble support is choosen. Since it is conditionally activated, it in general doesn't need a GUI input. But a GUI option number of base interface layers may enabled users to adapt this feature to their needs. This is my second try to provide a pull request on this topic. Reset my fromer repository, because first I merged this and all other changes to my master and couldn't provide separate pull request anymore.
Implemented with 32db22b, based on a pull request by @spiky2021 |
Version
2.30
Operating system type + version
Win 10
3D printer brand / version + firmware version (if known)
Anycubic I3 Mega, Craftbot Flow IDEX XL
Behavior
At the moment soluble support material adhesion is weak due to sparse support layers under soluble support layers.

Now I added two modified methods to the SupportMaterial Class (.cpp and .hpp attached).
new_SupportMaterial_Class_files.zip
new_support_files.zip
This adds two base type interface layers to the support structure, in case the extruders are different and soluble support is choosen.
Now soluble support adhesion is much stronger.
For someone expired with the GUI implementations, it might be an easy task to add an input for the number of base interface layers.
Though I believe two layers are reasonable for most situations.
By the way, I believe there is a bug in the original generate_interfaces method. The " idx_top_contact_first" is searched under the condition "layer->print_z >= intermediate_layer.print_z", but it should be "layer->bottom_z >= intermediate_layer.print_z" to avoid excess layers by swapping a layer too later to the upper top contact. In other words, compared to the bottom contact code it should be mirrow symmetric.
Is this a new feature request? yes?
I am new to the PrusaSlicer framework and GitHub (1 Week experience). Thus I didn't know how to make a pull request and wasn't interested in binding VS2019 to Github. But I hope someone of you can bring it to the base branch.
Project File (.3MF) where problem occurs
The text was updated successfully, but these errors were encountered: