Jump to content

AVCampos

LEGO Ambassadors
  • Posts

    1,475
  • Joined

  • Last visited

Everything posted by AVCampos

  1. Well, to be honest, I don't detest Control+... it lets us do nifty things beyond simple remote control (like a truck that I'm designing, that uses the gyro to optionally stabilise an onboard camera), with Pybricks there's no need for lugging around a phone, and it's actually usable outdoors. But I agree with the detestation of one peripheral per port (edit: which could have been averted if TLG adopted something like CAN Bus), the absence of "plug and play", and the rather small number of controls available in the LEGO physical remote controller.
  2. Maybe Boeing got angry at TLG for all the kerfuffle surrounding the Osprey, and Airbus jumped at the chance? Anyway, TLG appeasing two bitter rivals has been seen before, with Ferrari and Lamborghini; I don't think it's entirely coincidental that the very next 1:8 Technic supercar following the Lamborghini was a Ferrari.
  3. An authentic-working tail rotor needs collective control (thankfully no cyclic), so, judging from the size of the mechanism in the collective-only 9396, and unless new specialised moulds are created, a LEGO helicopter with collective tail would have to be huge.
  4. That's probably used only for small rotors, as anything spinning doesn't like to have its orientation changed (due to conservation of angular momentum), and the larger the rotor the harder it is to change its orientation.
  5. An alternative to that could be an "upload" button in Pybricks, which the user could use to directly import a .py file into the hub (with an "install with firmware" option). Not sure about the security aspect of dealing with unknown code without letting the user see it, though.
  6. Are you sure it's neon (I'm still undecided between calling it "neon" or "vibrant")? It appears regular yellow to me, but, then again, the photography process is a bit ambiguous.
  7. TLG should put a "screwdriver required but not included" disclaimer on the box, just like it does for the smart device. Better yet, start including a tiny screwdriver, just like many screwdriver-requiring Chinese toys do.
  8. I admit that, as an M:Tron fanboy, I really like the new Vibrant Yellow (it glows under UV! ) and want more parts in it, but in the helicopter I could do without either it or one of the other colours. Not that it matters much, though, since sets to me are parts packs and technique tutorials, not final models.
  9. That's also what I thought when I first saw it. Three main colours in a single model is to me a bit too much; other examples of that are the 9398 crawler and the 42128 tow truck.
  10. I agree that Pybricks has the large advantage of only requiring LEGO hardware (and allowing sweet stuff like auto-reversing the 42140's controls when it flips over), but, like you said, can't be used for proportional control. It also only works with PU, not PF, SBrick or BuWizz.
  11. Regarding a controller with integrated attachment, from personal experience one that stretches to clamp the phone (some larger models exist for tablets) between its halves is less tiring in the long run than one with with a holder on top of it, because it doesn't become so back-heavy.
  12. You can get a cheap used phone (BC2 doesn't require new or top-spec devices) specifically for LEGO control. For Android, though, as far as I know it has to run at least 4.4.2 to support BLE.
  13. Amongst the sets already released, the latest is the pullback Mustang. As for designing a set right now, I don't doubt it... but we're not allowed to know any details.
  14. Well, that's indeed not a secret: he is an official Technic designer at LEGO. The difference is that he still does these side-projects as a MOCer AFOL.
  15. I don't think the main issue is the set's price, but more if the interest of it makes up for the effort of writing an article or producing a video.
  16. And/or the Technic team needs to be convinced to produce more non-machinery sets, even if only as B-models.
  17. I have experienced time and again that I'm perfectly fine with the available parts assortment, but then along comes a new part and I think "how was I able to build without this"... The exception is the 4L pin, which I'm sorely missing and TLG insists on not making.
  18. Can't Stud.io import unofficial parts from LDraw's Parts Tracker? It "only" has the flip-flop lengths LEGO makes so far (11 and 15), but at least it's something.
  19. https://rebrickable.com/parts/89679/technic-panel-fairing-2-x-1-x-1/
  20. Maybe the set will be redesigned to avoid having the front springs constantly under strain?
  21. But they do include tiny screwdrivers when they're needed to access battery compartments. TLG should start doing the same, specially now that they switched the C+ hub to the screwed-on lid.
  22. If the rotor has 5 blades, I guess there's a good chance we'll get a new part to attach them (possibly combined with cyclic/collective): traditionally LEGO parts lend themselves only to 2-, 3-, 4- or 6-blade rotors.
  23. Does it also have 6 outputs and connects to a proportional controller? Or am I mistaking it with another brand?
  24. At that point, it might be easier to build a flip tank from scratch instead of adapting this one. I think the double-stickered panels on the sides are there to prevent that.
×
×
  • Create New...