thanks and don’t stop!
I just wanted to make sure you do not think I am ignoring your advices. This being clarified, and since we are between gentlemen, let’s skip all form of disclaimers and assume no offense is meant nor taken.
I have a CS and Physics, chemistry, mechanics etc background too (Civil Engineer specialized in CS) - I only started in machining with the Nomad and take any chance to meet experienced people when I can. I have understanding but little knowledge yet.
I full agree with your comments and understand the background.
@mbellon, the precise trouble is that the MC license we received with the Nomad is locked for the Nomad burnt-in post processor. As such, it behaves as implicitly implying CM. I do not think this was intentional, even less evil… it just is the way it is. What I would gladly fix with a post-processor (learned from @Randy), I simply can’t.
I make small tools and equipment for my home science lab (cogs and gears, enclosures, lens holders etc.), make stuff (maker style) like PCB’s, fix my kid’s toys or simply muse around the software architecture trying to discover what I have not read about yet. In a nutshell: I play with it.
I started learning Fusion360 and got somewhat ok at it but I am slow with it, it is a beast to handle and upgrades on its own for the better and the worst (dear cloud…). For my use case, I like OpenSCAD as it is lightweight, was a breeze to learn and is fundamentally program driven etc. I was planning to test Fusion360 python scripting when I can get a little time. We’ll see if the Fusion CAM helps but quite frankly, I like the idea behind MeshCam.
WRT the fancy geometries, I have opened a separate thread to avoid polluting this one:
thanks!