Debugging Bark Beetle tricks

[uomou]

In my view Bark Beetle is the easiest toolpath software on the planet,
but you have to be strict and consequent with your geometries in order to make it work properly
I used Bark Beetle since it exists, and came across a lot of strange errors that I had to figure out,
and many times I coulden't, so I asked Jens the creator of BB to help me out.
Basically every time with great success. I cannot wish for better support!

This document aimes to help you debugging bark Beetle yourself. It's a collection of fixes
that worked great for me, please feel free to contribute to this list, it might also help with future updates.

If this list should live somewhere else, feel free to change it.
Debugging Bark Beetle.txt

[JensDyvik]

Thank you for documenting and starting work on a troubleshooting guide! I am pasting the content of your .txt file here for those too lazy to open it:

This document aimes to help you debugging bark Beetle yourself. It's a collection of fixes
that worked great for me, please feel free to contribute to this list, it might also help with future updates.

2d milling - drilling pocketing cut outs tabs

• make sure all geometries are a 100% on the Cplane and always check bevor starting to program your toolpaths.
  It can be dangerous to machine paths that are not on the Cplane, but did get computed.

• use the command "projecttoCplane" and delete the originals

• if its stil not computing, check if your paths are closed

• most easy (use with caution) command "close curve"
  Rhino proceeds and may change the resolution if nesserray, so check your geometry after.

• command "offset path"
  Rhino generates a fresh offset of your path. Delete the original,
  then offset again back in other direction to keep your original dimensions.
  Use a small offset of <1mm to not destroy your geometries.