alexrj/Slic3r — Issue #179: duplicate should copy sliced and filled layers rather than 3d data
Author: triffid
Created: 2012-01-28 09:20:16+00:00
State: open

Just found a good reason to do this- I have a fairly detailed yet small model which I need lots of. (It's a new printable bushing)

If I slice one, slic3r works fine.
If I slice 4, slic3r consumes all available memory on my machine, then churns for a while and eventually produces gcode.

I'd like to do 12 or more at a time, but this is impossible, slic3r doesn't even create a surface for the first layer before oom-killer nukes it for eating 3GB of memory.

I think if it just sliced one, then duplicated the result, there would be no such problem.