While both tools exist separately their destinies remain intertwined. We work hard to keep parity while experimenting with varying approaches. Hard Ops is a lego sandbox of workflow and optimization with the aim of becoming an all in one toolkit while Boxcutter is just a cutter. It just cuts. While this seems limiting, it has been a fun experiment on working within constraints. We wanted to structure Boxcutter in a way where we made the hard choices and kept the user working without issue. Hard Ops however can feel daunting due to the amount of capabilities at your disposal. While we target the defaults for everyone we also pride ourselves on having workflow adjustments capable for those who want to tinker and experiment with their result.
Of course such speed comes with risks and occasionally… crashes. But let’s go over a particular case I find as a nice point of illustrating how hops and boxcutter differ on their pathing.

https://hardops-manual.readthedocs.io/en/latest/faq/#what-is-the-difference-between-hard-ops-and-boxcutter

New to hopscutter? Confused on where to start. Try the new user playlist!
Try… anywhere. Just try.

Documentation
Boxcutter – https://boxcutter-manual.readthedocs.io/en/latest/getstarted/
https://hardops-manual.readthedocs.io/en/latest/getstarted/

Accessing previous orders.
Gumroad – https://gumroad.com/library
Blendermarket – https://www.blendermarket.com/account/orders

Support Channels

View post on imgur.com

View post on imgur.com

– Gumroad
https://gum.co/hopscutter
https://gum.co/BoxCutter
https://gum.co/hardops

– Blendermarket
https://www.blendermarket.com/products/hard-ops–boxcutter-ultimate-bundle
https://www.blendermarket.com/products/boxcutter
https://www.blendermarket.com/products/hardopsofficial