AVCampos

Personally I think it's a good choice! It's a great parts pack of electronics, track elements and rubber inserts. The common colours to MOC with are also nice, but I'm still not sure about those Vibrant Yellow parts.

For me, the only disadvantages are lack of physical controls (once again... but that can be solved with BC2 or Pybricks) and low ground clearance, but that's expected from the "flip" feature. Also, for single-set MOCs I'd prefer the gears to be double-bevel instead of spur, to allow for changes in the direction of movement.

Sometimes LEGO changes the ID for an already-existing element.

Whatever the case, we should know for sure in less than a month.

Right-click -> "save as" (or equivalent).

As long as the motors have PF plugs, yes. But (at least some some) CaDa servos only have 3 positions (full left, full right, and centre), so they may work erratically when the SBrick and software controlling it are expecting a LEGO servo with several intermediate positions.

That would be a welcome addition indeed. But not in this set, as having only spur gears instead of their bevel versions limits the potential for single-set MOCs due to their inability to change the direction of movement. This is also why I think the 42095 would have benefited from having pairs of 12T-20T instead of 16T-16T (that, and being able to configure for speed or torque by swapping gears).

From the product description:

Did you try connecting from BrickController 2? Its hub testing function doesn't require a gamepad.

That's my understanding as well. To me, the gears that rotate freely are called "clutch"... even though that's not the best name: the only true LEGO clutch gear is the white 24T.

The most likely reason I see is, as folks have written here before, that they'll be required in a future set and this is an opportunity to more easily have them. As for being more fragile, well, TLG doesn't always make the sturdiest mechanisms. Example: the rear axle of the Zetros.

Y'all will miss good ol' Powered Up by the time its successor comes, mock... I mean mark, my words! I remember people bashed PF left and right when it replaced 9V, and I bet people would have bashed 9V when it replaced 4.5V if the Internet were widespread in those days, yet PF is now beloved. Anyway, regarding the specific problem at hand... @leonema if location is on but its icon in the app is greyed out, did you allow the app to access the location services when it first asked to? If you refused, you need to re-allow it in the app's properties page, in your device settings.

Actually, to be pedantic, hubs and (some) sensors are even more expensive than motors, but your argument is still valid here.

51515 costs €360 for 949 parts, so that PPP isn't that unrealistic.

You can also use the test function in BrickController 2 to see if you can connect to the hub and run the motors. You don't need to have a gamepad for that.

Unlike UCS supercars, I see here a clear path of Technic evolution: cyclic and collective controls.

On the other hand, I'm quite becoming a fan of it! It would be a lot either harder or cumbersome to do with PF or EV3 my M:Tron "monorail" being able to roll around and automatically stop for a few moments on specific areas of the track.

Context is for the weak!

Hmm, I didn't know that. Odd, considering the number of tiltrotors TLG has launched over the years, and that's also the technique Hasbro uses to make Transformers with unlicensed alt-modes.

TLG please take note: Lengthen the nose, replace the windscreen with a bubble canopy, change the rudders into ruddervators, and I won't see an Osprey there any more without having to drastically re-engineer the structure or the mechanisms. Oh, and while you're at it, please also have the gearbox fixed out-of-the-box.

8043 already does something like that, with three 2-position gearboxes switched by a single motor. Actually, it has two disadvantages: the function doesn't run as soon as you press the button (the mechanism has to switch to it first), and still only one function (per gearbox) can run at a time.

Any BT controller that works with Android apps should work with BC2. Just to be sure, you can ask someone with a PS4 controller to lend it to you for a few minutes, and then try out BC2's controller test feature. But, if you intend to buy a controller specifically for BC2, it doesn't have to be an expensive PS4 gamepad: any generic one should do.

A cross between 42028-B and 42055-A? Yes, that could be interesting. But, please, with the hoops in a more common colour!

Bluetooth and glove usability aren't related. What you probably mean is on-screen controls vs. physical controls, and that can be remedied by BrickController 2 or Pybricks.

LEGO produced the PF E motor, and only found use for it in a single Education set.