Parametric TARDIS
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?
None of the Tardises on here were quite what I was looking for, so i decided to make one myself.
I tried to make it as parametric as possible, but you'll still find some things, such as the depth of the face impression, that are static.
I'm working on an accompanying insert that will light up the light on top from the inside, I'll add that as a derivative as it develops.
Let me know if you find any parameters that aren't scaling/re-sizing properly.
EDIT: Per suggestions from Bluemetal and Tbuser I've added leading 0s to my decimal values and added render() to the face module, so it will now compile(F5) properly.
- And, goodness knows, I feel compelled to blog anything Doctor Who related. [↩]
| Tagged with | doctor who, openscad, openscad tip, openscad tutorial, tardis, tips, too many elements | Leave a comment |




