Possibly for the next heli, a CH-53E? The only ones on the site are far outdated
Oh yeah that could work, but that still wouldn't solve the problem of them being unsynchronized. Aka, 2 blades don't stay at 180*.
Where can i get that heli?
@asteroidbook345 I didn’t even realize lmao. Thanks too
Sadly, my theory does not work. The helicopter rotors, no matter how you attach them, cannot calculate the force of their torque to spread across two parts. This causes the drive shaft to pull out of the swash plate because of the Gs it experiences with one blade. That looks like this. In theory it could work, but only if you could blend SP's part physics together with other parts via connections (dang, whoever thought of that?). However, there was one other potential solution: I want through the Helicopter Rotor's Xml file in Overload, and found a few things I could try. These being: Changing collectiveTorque to 0, cyclicMotorDragTorque to 0, gyroscopicLag to 0, rotorTensor to 0, and gradually increasing the gyroscopicStabilization. Sadly, even with a combination of all those inputs, it did not improve. The blades did not even make lift until I entered Slow Motion (for some reason the physics work different there). I think the real solution is to update the stock rotors so they can fold, or whatever 2Papi2Chulo did.
Hope I saved you some time,
I'll test it on an old chopper of mine and let you know if it works!
@switdog08 no but thats clever. I made a custom rotor and engines to make it spin
By any chance, to create the blade folding affect, did you use 4 one-bladed helicopter pieces attached to rotators, thus allowing them to be balanced when in use by all having the same stats?
I commented on your YouTube