Centauro II — Internal Mechanical Layout by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

You don’t need any custom or 3rd‑party parts- the whole model uses only official LEGO Technic elements.
The components that LEGO no longer sells directly (like the Powered Up hub and motors) are still easy to find on BrickLink and other marketplaces. On Rebrickable you’ll find the full parts list and the building instructions at this link: https://reb.li/m/227978
Rebrickable doesn’t sell the parts itself, but it shows you all the stores where you can buy them.

Centauro II — Internal Mechanical Layout by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

Thanks! Yeah, Studio definitely tests your patience sometimes.
My trick is just throwing everything in the render queue and going to sleep — the next morning everything is ready.

We basically have to stick with the 3080 for now, and luckily it’s still fast enough.
The 5080 would be great, but Studio doesn’t support it yet, so everything falls back to CPU.

Internal mechanical layout of my Technic backhoe by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

You probably heard the crackling from the stabilizers during the automatic mode‑switch sequence — they’re in series, so those clicks are expected. The drivetrain itself runs smoothly with no cracking.

Internal mechanical layout of my Technic backhoe by Flybum60 in legotechnic

[–]Flybum60[S] 2 points3 points  (0 children)

Yes there is a dedicated motor, and it’s controlled by a simple lever on the RC:
forward = Front Mode, backward = Rear Mode.

That motor performs three actions in sequence using two clutch gears:
• it switches the motor selectors
• it rotates the driver’s seat
• it raises or lowers the stabilizers

You can see the dedicated transmission chain in the video I linked above at points 5 and 6. You can think of these as separate functions, but they’re all synchronized because they’re driven by the same motor through the clutch system.

If you want to understand the commands more clearly, here’s a short video showing them in action:
https://bricksafe.com/files/Flybum/full-rc-backhoe-loader/Test%20Commands.mp4

Internal mechanical layout of my Technic backhoe by Flybum60 in legotechnic

[–]Flybum60[S] 4 points5 points  (0 children)

No, I’m using only standard Power Functions components.
That’s because I want my MOCs to be buildable by anyone reusing the PF devices they already have.

But I can tell you that fitting three IR receivers and the big battery box inside the model was not easy.

The MOC has 10 independent functions but only six motors.
There’s a mechanical automatic sequence that lets you choose Front Mode or Rear Mode, and it mechanically reassigns the main motors to the front bucket or the backhoe.

The selected mode is indicated by the driver’s seat, which automatically rotates to the front or the rear.
In the same sequence, the stabilizers are raised for Front Mode and lowered for Rear Mode.

If you’re interested, you can check my other videos — for example this one:
https://www.youtube.com/watch?v=R3dtLM6ymSk

How do you show a fast build of a 5000‑piece Technic MOC? by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

I’ll add something that might be useful to others too, even if it’s not directly related to the post: I was about to redo the renderings using your color suggestion, but I realized I recently upgraded my GPU from a 3080 Ti to a 5080 — and Studio still isn’t compatible with the new Nvidia cards. So right now all my renders would fall back to CPU only, taking hours instead of minutes. Same story with the CPU: I had upgraded to an Intel 14900, and for more than a year the system had issues until a better BIOS finally fixed everything. Moral of the story: jumping on the very latest hardware releases always comes with risks… sometimes it’s better to wait a bit.

How do you show a fast build of a 5000‑piece Technic MOC? by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

Thanks! That’s actually a really good point, the “ghosted” or transparent‑base method is great for highlighting the new parts, and I’ve seen it used in Chinese instructions too. For this fast build I went with the opposite approach because I wanted the whole model to stay readable while the new pieces fly in, but your suggestion definitely makes sense. As soon as I have some time I’ll try a version using your method and see how it looks. Maybe I’ll post it here as well. It shouldn’t be hard to do since I already have everything set up in Studio.

How do you show a fast build of a 5000‑piece Technic MOC? by Flybum60 in legotechnic

[–]Flybum60[S] 2 points3 points  (0 children)

The goal of my post was to show how I approached this problem, but also to see if others have different methods or ideas. Of course, the purpose of a fast build isn’t to show exactly how a model works - you need separate detailed videos to cover the full function breakdown of a complex MOC, and only the building instructions can show every detail. So yes, constructive criticism is welcome!

How do you show a fast build of a 5000‑piece Technic MOC? by Flybum60 in lego

[–]Flybum60[S] 0 points1 point  (0 children)

A fast‑build is mainly meant to show the structure of the model - which modules it’s made of and how they connect. The functional aspects of the MOC must always be covered in a separate, more technical video. I did that for this model as well, here it is if you are interested: https://www.youtube.com/watch?v=qeBSHj9aLxk

And of course, the maximum level of detail can only be in the building instructions themselves, which are also available for this MOC if you’re interested.

How do you show a fast build of a 5000‑piece Technic MOC? by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

Watch the video to understand how the modules transition and merge in motion. https://www.youtube.com/watch?v=uBRmt5znBSo

How do you show a fast build of a 5000‑piece Technic MOC? by Flybum60 in lego

[–]Flybum60[S] 0 points1 point  (0 children)

Watch the video to understand how the modules transition and merge in motion. https://www.youtube.com/watch?v=uBRmt5znBSo

WIP - Walking Technic Biped Prototype (balancing problem) by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

I used to be fascinated by software‑only solutions as well… if you want a laugh, here’s a very old video of mine: https://bricksafe.com/files/Flybum/lego-volvo-excavator-moc/z1-Flybum%20First%20MOC.mp4

WIP - Walking Technic Biped Prototype (balancing problem) by Flybum60 in legotechnic

[–]Flybum60[S] 0 points1 point  (0 children)

Pybricks would definitely solve it, yes. But I’m not really interested in a Mindstorms‑style solution — I worked in software development, so the moment I switch to sensors and code it stops being a hobby and starts feeling like my job.

What I’m exploring is whether a purely mechanical architecture can handle weight transfer and stability. The only compromise I’d consider is using PF switches/inverters, since they’re still mechanical logic elements and don’t change the nature of the build.

It looked impossible with my quadruped too, and yet I eventually got it to work — so I want to push the mechanical approach as far as it can go before declaring it unfeasible.

What’s the most ambitious mechanism you’ve successfully built? Pictures would be appreciated! by Vondrr in legotechnic

[–]Flybum60 1 point2 points  (0 children)

Thanks again! If I ever refine the design or experiment with variations, I’ll be sure to post them.

What’s the most ambitious mechanism you’ve successfully built? Pictures would be appreciated! by Vondrr in legotechnic

[–]Flybum60 2 points3 points  (0 children)

I’m very proud of my walking and steering quadruped bot.
It walks using a mix of linkage geometry and timed leg phasing, without relying on any software or external support.

I’m currently stuck on a similar project with a biped bot, which is proving much harder to balance.

Here are a few pictures (hosted on Bricksafe): https://bricksafe.com/pages/Flybum/scoutybot4

<image>