If there’s something that’s even better than a regular TARDIS, it’s a parametric OpenSCAD TARDIS. 1 In the true spirit of Thingiverse, the designer Gossamer, shared their designs and source code. Doing so allowed other users to join in, offer suggestions, and Gossamer immediately updated the TARDIS code to incorporate these improvements.
Here are two OpenSCAD pro-tips:
- Best Programming Practices. OpenSCAD for Windows tends to freak out when you don’t add a leading “0” to a decimal. By adding writing “0.5” rather than “.5” you can ensure compatibility across platforms. Thanks Bluemetal!
- Too Many Elements. Sometimes OpenSCAD will complain that there are too many elements. You’ll see this happen a lot more when you’ve got some “for loops” or lots of nested functions. By adding “render()” before a group of code, you force OpenSCAD to render and cache that group of code. Each successive render will be a lot quicker. Thanks Tbuser!
What other OpenSCAD tips do you have to share?
Error - could not find Thing 13109.
- And, goodness knows, I feel compelled to blog anything Doctor Who related. [↩]
|Tagged with||doctor who, openscad, openscad tip, openscad tutorial, tardis, Thingalert, tips, too many elements||Leave a comment|