Getting from the raw slice contours to the final toolpaths
Loading parts into
Slices generates a stack of its contours. Process these contours to generate the actual toolpaths and exposure patterns suitable to your model and machine.
What is it?
- Processing
takes existing slice stacks and uses the contour and hatching information contained in them to
generate new stacks with new contours and hatchings.
- Only
one generation method is performed at a time.
When should I use it?
When your machine is not supported by other toolpath generation functions in
Netfabb, such as machine workspaces, or when you do not want to use them.
Pros and Cons?
Pros
Cons
- Processing actions must be run separately and manually unless chained in a Lua script.
- Processing results are always added to the project even when they are just intermediates for further actions and are themselves not used during exposure, so they must be cleared before, or separated during, slice file export.
- Working in 2D may skew geometry as each layer is processed individually regardless what angle against the Z axis the surface had from which the current layer's contour was generated.
Where do I do this?
Use the commands in the
main menu while slice stacks are selected, or use the
context menu of slice stacks directly.
Notes
- You can use
Undo and
Redo to revise steps at any time.
- The result from copying and pasting a generated slice
maintains the link to the parameters used for the original.
For example, you create an offset, and then clone the offset. Modifying the distance value in the original offset also adjusts the distance value in the clone. If you do not want this link, you must create a new offset independently, not through
copy & paste.
- Use
on slice stacks to finalize them for the next steps if performance becomes an issue during toolpath animation or general processing. While this removes the option to adjust the generation settings for those stacks, you can still use
Undo to get them back.
Tip: Create working copies for stacks meant to be input stacks before actually processing them.
- Some operations (EBPAs, for example) may be computationally expensive. To speed up rendering and animation, especially during toolpath preview, you have the option to postpone displaying and applying the results.