- when more than one scriptpath are enabled in Blender, backgroundop.py_
couldn't be found sometimes.
- medial axis ball cutters didn't work
-version in init file was still 0.8
Update NC library to Heekscnc NC version 1.0
- feed now accepts 6 axis parameters
- tool_defn function now uses a params list instead of individual param
names
- improved drill cycle
- improved number formating - better rounding
- block numbering now automatic - no longer need to call
write_blocknum().
- dwell works now
Before, it was going always in the middle which was non-sense...
now, it can be combined with a reasonably set pocket operation for
milling stamps and similar.
Old version didn't support tabs - now there's a tab called Blender CAM
where we can add various usefull tools.
now there are:
booleans
intarsion
overcuts
Silhouette offset (works also for meshes)
remove doubles
I will welcome if this gets added to docs ;)
Generates overcuts on a curve.
- inner, or also outer polygons.
-has threshold for angles to consider
the overcuts are optimal - done so that the radius of the cutter only
touches the corner, but doesn't go behind it.
this optimizes chunk sorting a bit, by not iterating over too many
children - some chunks could be checked many times.
For parallel operations with layers, this fixes something that was
rather a bug - because too many relations were created and this could
lead to exponential computation times relative to count of layers.
the memory limit is a new feature, preventing crashes when ppl. e.g.
compute path on the default size obects, and also any other cases with
non-exact mode.
otherwise, big, happy removal of polygon library residues. This library
is NO logner a dependency of blender CAM. Shapely library works far
better in most cases. Sometimes it's slower but this can be compensated
with optimizations almost always quite easily.
Infinite loop was caused by don't merge paths option. This option can
cause chunks to intersect, and then seemed for the algorithm as one
inside each other, thus causing a parent-child loop.
Important to mention is the fact, that don't merge outlines is an exotic
option which is there ONLY for milling PCB's,...
bridges code had some really stupid redoing - it was getting the bridges
polygon for EACH chunk which was supposed to be computed... this proves
again my old rule - if I write something very badly , I can then enjoy
optimizations by several hundred percent :)
the way curvers are subdivided before voronoi processing matters - lines
are now subdivided from both ends, to get same distances to the corner,
this makes carving of shapes with straight vectors much better.
with a better voronoi, this would be what it's supposed to be. Now with
V-carve tool it allready looks ok for first test, however always with a
tuning parameter, to not have many short lines in the voronoi graph.
optimized pack algo, works same speed as with polygon or a bit faster.
Did this mainly to learn how to optimize shapely code a bit to get
better faster results...