sdfx

I wrote this (in golang) to satisfy my need to generate STLs for 3d printing. https://github.com/deadsy/sdfx In general I like to write code to define objects, but there are some situations where a graphical editing UI would be nice. ie- Curve and polygon design. You can sort of imagine a hybrid approach where you could crack open a mini editor to design a curve and then use it to generate code (table of numbers) which you could then extrude/sweep/loft or whatever.

Nice to see sdfx [1] there, this project is impressive. deadsy built some rather sophisticated models, be sure to check out the renderings in the github README! https://github.com/deadsy/sdfx

As soon as I saw the first frame, I knew that was an Inigo Quilez video, very interesting work. His website inspired me to switch to an SDF approach to modeling for 3d printing: https://github.com/deadsy/sdfx.

Well, I looked at the linked page[0] and it says STL files. 0. https://github.com/deadsy/sdfx

I started with OpenSCAD but: a) found the language to be clunky b) had a hard time doing chamfered unions between objects (needed for sand casting patterns). So - I wrote my own tool/library in Go and it's essentially replaced my OpenSCAD usage. https://github.com/deadsy/sdfx

I wrote a CAD package in Go that has a function for it. https://github.com/deadsy/sdfx func InvoluteGear( numberTeeth int, // number of gear teeth gearModule float64, // pitch circle diameter / number of gear teeth pressureAngle float64, // gear pressure angle (radians) backlash float64, // backlash expressed as per-tooth distance at pitch circumference clearance float64, // additional root clearance ringWidth float64, // width of ring wall (from root circle) facets int, // number of facets for involute flank )

>Even something seemingly simple such as saying "is point C to the left or right of the line A->B" is very hard in floating point. Is it? ie - construct a normal and take a dot product. That'll work the vast majority of the time. Near the line you'll start running into the FP precision limits. With 64 (...or even 32) bit floats that sort of distance is likely way smaller than anything that represents a practical distance, so just call it and say you are on the line. Of late I've been messing about with problems of this nature and I can't say it's been all that difficult. https://github.com/deadsy/sdfx