I’ve never used Timelapse but while doing some research on ways to set a Timelapse or make one myself I noticed there is a setting for Traditional and Smooth and for the A1 Smooth is recommended so in case I forgot I set it to Smooth.
Now when I went to print I didn’t activate Timelapse but it still built a Prime Tower.
I’m guessing if I set it back to Traditional this won’t happen.
Surely it is either a bug or an oversight.
1 Like
It’s unclear as to how your slicer is configured but there is a simple remedy to turning off the prime tower. You don’t mention whether or not you have an AMS but if the slicer senses that there is a call for multicolor, it should default to creating a prime tower. Either way, just uncheck this box:
In Bambu studio 1.10, it’s listed under the “others” tab.
In Orca Slicer starting at 2.0, it has been moved to the multimaterial tab.
Yeah, sorry. No AMS.
I know I can turn Prime Tower off but if I select Timelapse → Smooth it recommends turning it on.
So my main point is why is it building the tower with Timelapse off?
Surely this shouldn’t be happening regardless of what settings you have.
In any case I will set it back to Traditional as it will remind me to set it to Smooth if I turn Timelapse on.
Its not a bug. Once you switch between the timelapses and choose smooth, it automatically selects the prime tower. If you dont deactivate the selection but switch vavk to traditonal timelapse, it will stay toggled for you to print it.
Just pay attention when you slice. If you see the prime tower delete it
Probably not a bug but certainly an omission. Regardless of the setting, IMHO a tower shouldn’t be built if you have Timelapse deactivated. Pretty simple and logical to me.
I’m basically just venting as nothing will be changed by my mentioning it here.
1 Like
I agree that from an end user perspective regardless of the timelapse smooth/traditional setting, if you don’t select to do a timelapse at print time, it would make sense to not print the prime tower.
That said, the prime tower is part of the slicing (part of each layer’s gcode) which is generated BEFORE the “Print” dialog (where you choose to do a timelapse) so to accomplish the desired behavior, either the model would have to be resliced after you complete the “Print” dialog, or it’d have to slice both ways ahead of time (both with and without the tower), store both gcode variations, and send the appropriate gcode to the printer after the “Print” dialog.
Understanding this helped me get past my orig frustration - hopefully it helps others?