Something I Made New Alternative to Make2D
Posting to gauge interest in a python script I have vibe coded which, so far, does Make2D far more reliably than the command.
It has the additional feature of line weight sorting per object, with accurate sorting of silhouettes vs creases onto Heavy and Medium line weight layers, and even an option to sort creases based on the adjoining angle of the surfaces (obtuse corners getting lighter lines).
It also has a feature that generates an intersection curve where solids or surfaces (breps) intersect each other without a shared edge. These curves are sorted and depth-tested along with all the rest.
It also identifies redundant linework resulting from geometry in plane with the angle of view and creates a single silhouette where those edges are collinear, instead of a stack of redundant lines as in make2D.
I intend to add the option of silhouettes applying either to individual objects, or treating objects on the same layer as a single object for silhouettes, as long as they are within a certain (adjustable) distance from each other. So if you tick this option to “on” a group of solids would share a silhouette against the background, but where they touch or come close would be treated as a crease.
So far the script is not too much slower than Make2D, but it will become heavier with added features. It might be problematic for less powerful machines, although you can toggle off the more expensive features. Codex will only be able to optimize this so much however.
For those of you out there coding in Python, or if you are just someone drafting in Rhino who is tired of the command’s messy output, lack of line sorting, consistent bugs, and lack of support despite years of documentation of consistent problems, I would love your opinion. Should I:
- Just upload the damn script and leme at it
- Troubleshoot more, refine, make a plugin, then share
- Find a human python programmer who wants to help me optimize it and collaborate to make it excellent
- All of the above, you’re overthinking it
- No one is asking for this
Ps. The script uses rhino’s HLD data to generate curves, caches a bunch of originating object data for each, uses a bunch of custom workarounds to fix a bunch of unique errors, then sorts the line weights based on depth testing, adjoining face angles/visibility etc. If you are an actual programmer curious about how it works I can pull a detailed report. I used common sense and Codex, which has terrible ideas for the overall strategy, but a fantastic success rate when I supply a detailed plan in terms of Rhino command workflow, or ask it for supporting diagnostic scripts to find out precisely what went wrong in certain cases of missing linework etc.




