Is there an existing issue for this problem?
Snapmaker_Orca Version
2.3.1
Operating System (OS)
Windows
OS Version
Windows 10 / Windows 11
Additional system information
N/A
Printer
Snapmaker U1
How to reproduce
NOTE FOR Snorca V2.3.5 :: There is a SHIFT + LFT Click + DRAG command to remove paint from an object (ERASE). While this does not fix the issue, it can be used as the primary method of removing paint spillover.
- Import the "Adorable Baby Dragon" STL into the slicer. (This is the default "benchy" for the U1)
- Assign the model a default filament, but select one of the FullSpectrum virtual filaments.
- Using a real or virtual filament, paint some of the features on the baby dragon, e.g. the horns and spiny ridge.
- Because the paint tool does not have an eraser feature, it cannot remove the over splash of the paint where it appears on the other parts of the baby dragon, e.g. the dragon hide. Instead you have to select the same virtual filament of the default filament to paint over the other paint.
- When you slice the object, the tool path of the painted area is separated from the default tool path.
- The physical effect is that the same tool extrudes along the default area, stops, then extrudes separately, the painted area. The result is an unwanted seam between the same virtual filament.
- This does not occur with physical filaments.
Attached is the test cases I created. Note: I abandoned the cubes because the top layer is considered a special case that is handled by @Neotko's "sandwhich" designation. Instead I designed the same test cases with hemispheres and added two cubes for testing the "Cycle" feature in FullSpectrum to see if a solid third wall could act as a dimensional background for a CMY filament set to appear more bold instead of a pastel. Those results are not pertinent to this bug analysis.
Actual results
Here is my first notice of the issue during printing:
Notice that Control 2 (virtual filament as default filament, no painted areas) acts just like Control 1 - it has three perimeters and gyroid infill. However, Test 2 (virtual filament as default filament, painted areas with same virtual filament) is showing signs of a painting tool path process like Test 3 and Test 4 are using two different filaments (real and virtual). This is expected for 3 and 4 and would have stood out more if the two colors were not so close together.
The finished test cases:
Expected results
Regardless of being a real or virtual filament the slicer should detect and create tool paths for identical tool heads (filament) at layer. The GCODE of Test 2 should be identical to Control 2.
Project file & Debug log uploads
Dragon Textured_PCTG_10h14m.zip
Checklist of files to include
Anything else?
No response
Is there an existing issue for this problem?
Snapmaker_Orca Version
2.3.1
Operating System (OS)
Windows
OS Version
Windows 10 / Windows 11
Additional system information
N/A
Printer
Snapmaker U1
How to reproduce
NOTE FOR Snorca V2.3.5 :: There is a SHIFT + LFT Click + DRAG command to remove paint from an object (ERASE). While this does not fix the issue, it can be used as the primary method of removing paint spillover.
Attached is the test cases I created. Note: I abandoned the cubes because the top layer is considered a special case that is handled by @Neotko's "sandwhich" designation. Instead I designed the same test cases with hemispheres and added two cubes for testing the "Cycle" feature in FullSpectrum to see if a solid third wall could act as a dimensional background for a CMY filament set to appear more bold instead of a pastel. Those results are not pertinent to this bug analysis.
Actual results
Here is my first notice of the issue during printing:
Notice that Control 2 (virtual filament as default filament, no painted areas) acts just like Control 1 - it has three perimeters and gyroid infill. However, Test 2 (virtual filament as default filament, painted areas with same virtual filament) is showing signs of a painting tool path process like Test 3 and Test 4 are using two different filaments (real and virtual). This is expected for 3 and 4 and would have stood out more if the two colors were not so close together.
The finished test cases:
Expected results
Regardless of being a real or virtual filament the slicer should detect and create tool paths for identical tool heads (filament) at layer. The GCODE of Test 2 should be identical to Control 2.
Project file & Debug log uploads
Dragon Textured_PCTG_10h14m.zip
Checklist of files to include
Anything else?
No response