Bitsetter hate!

Thank you for that advice, but I really never use the table for my Zero. I was always thinking I would for a 3D carve, but I haven’t needed to do that.

Possible CM bugs aside, I find this topic quite interesting as this seems be pretty much the same workflow the Nomad had from the start (someone correct me if I am wrong - not a SO3 owner) and most of the debate was around the extra time it was taking and I can’t recall (at the moment at least) any complaints about being error prone.

I never considered changing the tool at that point in the workflow but now that you mention it I could see how it could happen. If you are used to a non-Bitsetter SO3 setup I can see it being even a likelihood.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.