LeoCAD is an application that I use somewhat frequently. It is available for Linux, Windows and even Mac but I don’t have a Windows or Mac machine of which to compare to Linux. I have written about the joys of using LeoCAD before if you are interested in that blathering and at that time I used the AppImage to run the application. Now am using the openSUSE community repository instead and I installed it from here:
The downside of using this source is, you do have to manually install the parts library to a location on root.
The latest parts library can be found here.
I did have some issue getting LeoCAD to find my library but but renaming the complete.zip library.bin and placing it in the aforementioned location made the parts available for use.
What I particularly enjoyed about using it from the openSUSE repositories is that LeoCAD now respects my dark desktop theme which is much easier on my eyes and more enjoyable in which to “work.” Okay, I realize, I am “playing” and not “working” but it is also a fantastic teaching tool.
The version of LeoCAD I am using at the time of writing is 18.02. It works very smooth, has yet to crash and is a joy to use.
Designing my be a stretch, actually, more like modification of existing designs. A little back story, 8 year old me was incredibly enamored with this LEGO space theme called Blacktron. I didn’t like that LEGO considered them the “bad guys” and that idea has perpetuated with, for what I can tell, no variation on that meme. So, I have decided that I wanted to introduce that idea, that they are not still the “bad guys.” I did this by making a couple Rebrickable.com submissions with a different idea, here.
One of my first “designs” was just making this first Blacktron LEGO set the way I wanted it as a kid. It included reversing the connections and modernizing it with the newer small parts to add more interesting detail that is now available.
One of the features of this and the Blacktron vehicle sets was this modularity that was advertised on the back of the instruction manual. I didn’t like that the Invader connectors were “backwards” from the other vehicles so reversing it was a must which also made for some space to add some other details below the wings.
In changing the direction of the Technic connectors, I was able to make the interaction with the other models more to my liking. The original intent was fine but I just happen to like my revision better.
Since there is this modularity as part of the design with the Invader it essentially giving you two options of play with this set: with the cargo module and without, a “scout mode,” I thought, “what if the Invader was a multi-purpose, multi-role craft?”
So, I took another existing design from another space theme and incorporated the elements into the Invader as a module. Another theme I enjoyed as a child was this M:Tron theme. They had all these cool magnet features that I think was far more popular than what the Blacktron Theme had ever been. The process I used to build this was to cobble together the idea with the parts I had than take the design to the CAD to optimize the design and order more appropriate parts.
Upon receiving the parts, I made the adjustments and the final test was giving it to my 4 year old to see how long it would stay together. The good news is, it appears to be a success and brought a lot of smiles to my kids. The Crane portion does seem to get ripped off a bit more than I would like but no more than the original model, perhaps a little less than the original model but not my much.
I have other “designs” that have been inspired by Star Wars but those will have to wait another day. This blathering about playing with children’s toys has gone on long enough.
Using LeoCAD and the real thing allows me to teach my kids the product design process but in a much shorter cycle and in a more fun way, with LEGO. We will build an idea, take it to LeoCAD and go back and forth between real LEGO to the CAD and back to the LEGO again to test and refine the design. I can demonstrate what it is like going through a product development cycle but with a much, much shorter design validation cycle. That design validation is, will it hold up long enough in the hands of a 4, 6 or 8 year old.