yesbird wrote: ↑Sat May 28, 2022 7:41 am
While experimenting with multicolor printing I found a strange issue, that might be a bug:
I have two processes in my factory and second contains commands for filament changing:
{REPLACE "; layer 50" "M600\n; layer 50"}
{REPLACE "; layer 80" "M600\n; layer 80"}
While using only one process, commands invoked as expected.
In a case of two processes they are not woking and I am missing the point of filament changing.
Put those commands into the first process used for slicing. Replace commands are put into
the post processing commands and will beexecuted after the whole gcode file using all processes
has been created.
Layers are counted continously from 0 - end. So if your first process is set to 6 bottom layers,
stops after 4 and the next process is also set to 6, it will print another 2, 6 in total.
Many settings like 1st layer settings from the second process will simply be ignored, they will
also be taken from the first process.
One thing you absolutely should NOT do, but I've seen people doing on the forum:
Never create multiple processes for a single object and slice them on their own. To get
reasonable results all processes used must "know" what the ones before are doing.
Consider adding factory files to your posts, so others can check settings/features.
Another completely different question would be if it's worth it, digging through a slicer
that hasn't seen any updates/bug fixes for over 3 years...
Edit, related to multiple processes:
viewtopic.php?t=15180
(trying to use supports on a process starting mid-air... ^^)
viewtopic.php?t=15124