#3 falcon projects tasks archive#
#3 falcon projects tasks code#
#3 falcon projects tasks plus#

#3 falcon projects tasks code#

Using neopixel circular arrays for both models would mean we could scale the code and everything else pretty easily.

#3 falcon projects tasks plus#

We were delighted (see what I did there?) to discover that the Adafruit Neopixel 7-element Jewel fit perfectly into the 1/24th engine, and the Jewel plus the 12-element Ring fit the 1/12th – a convenient way to scale up our solution. The main objective of the first sprint would be to decide on what lighting components we’d build around. As with much of the project, we start with the 1/24th model. This post will be about the lighting (and mechatronics) solution we’ve started working on for the 1/12th. Onward! Posted in Master Model, Sean The Stu Brown Show Six years later, we are more confident than ever that what we’re divining is dang close to the original. 3D surface data reprojected onto photo and rendered. When we re-render our tracked surface data over our Falcon photoset (we have a little over 130 photos that we use for our Falcon 3D tracking) we have pretty tight alignment – original model’s idiosyncrasies not withstanding. Being able to make hypotheses, and verify that those hypotheses were correct as a scientific control to prove the fundamental method gave us greater confidence in what we’ve been doing with the Falcon. We’ve been using a similar process on the Falcon all along, but the X-Wing project really allowed us to tune our process, and verify that process against known fuselage dimensions since Jason had original X-Wing parts in-hand.

X-Wing digital model and photo composite as seen in X-Wing Part 1. Below shows one of a dozen reference images we used for the X-Wing to track points in 3D space, extract them to CAD, and the use them as reference for final surfacing in Alias. The X-Wing project really helped Andre and I refine a workflow to truly nail the proportions of a model and the tracking points for reference. Or in some cases the Sean model, or the Stu model, etc…

#3 falcon projects tasks archive#

Fusion 360 keeps internal version numbers – but that is every single save – otherwise, we do our own mile-stoning duplicate the working file, and dump it into an archive to have more discrete checkpoints. I thought it would be fun to superimpose all our key milestones. And then there’s the quad-cannons, docking arms, jaw boxes, docking rings, and on and on. And hundreds more if you factor in the progression of the subassemblies – I think our upper gun platform revisions alone were in the upper-fifties before we were happy with them. In aggregate we’ve done hundreds of iterations over the six years. I keep a digital twin reference model of every team members’ build in case we need to go back and pull a specific dimension or reference. That’s version 17 of his Falcon model (which currently sits a v22). Stu mentioned he was using version seventeen. Yearly (or more) snapshots of our iterative process He reworked as much as he could in real-time, but otherwise plowed through as only Sean can, and we rolled as much knowledge into the next rev of CAD in his wake. As he built, he let us know where we were wrong (and right).

Millennium Falcon by Sean Sides premiering next to the restored Dykstraflex motion control camera used to film the original Star Wars miniatures. We did most of this on Slack – and some 50,000 messages (mostly “LOL”) and several gigabytes of photos and files later, Sean has a fully realized Falcon, and Stu (by his own best guess) is three-fourths through his. Identifying new donor parts, trying to figure out the proportions of things, etc.

Sean Sides, Stu Brown, Doug Maio, Andre Bustanoby, and myself would spend the next six years together chatting about all things Falcon. This got the attention of a few fellow Falconers and our little family was born.

In April 2015, Andre and I “published” our first drafts of a blueprint for the Falcon.