[email protected]

I’m gonna need help, y’all. I’m a single-part amateur hack with a penchant for anything cheap. I don’t know enough to make it what you’ll want it to be, but I am very interested in the broader industry and also its impact on maker hobbies. You want Solidworks advice? To gripe simultaneously about enshittification and the limitations of free tools? Need to dive into Lasering or Machining or CNC’ing stuff and don’t feel like the 3D printing community is quite the right place? Come on over.

I will keep posting stuff that I find interesting, and I will mod as long as doing so doesn’t make me hate life, but if nothing else the name is now parked with an active user.

  • j4k3@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 months ago

    TNI is not about planes. It is about the linearity of the tree, the truncation of infinite numbers, and the loops the tree must patch on in order to break a linear branch of the tree. These breaks create a cascade of problems that are not possible to address because the information required is missing once the initial reference is created and truncated at the register level. It is not a single reference issue. All references down tree are relative and themselves often truncated. Breaking the tree is always the wrong thing to do. Yes it can be done as a hack to do something quickly, but that is just a hack. Stacking hacks is terrible design. This is the difference between a good designer and the bad. It is all about a linear tree and π.

    I can design without any reference planes and just offsetting my sketches. I never use faces or import 3d geometry. I am very intentional about what references I import and those I do not. I also make some sketches as references only, and these are used to alter other sketches down tree. All of this is TNI centric.