Adjustable thrust vectoring for engine parts #1807
Conversation
Adjustable thrust vectoring value for engine parts, as thrust changes to mts physics system with thrust vectoring has proven to be a headache for me and other PAs, especially those from GAP. There are no LCs for defaulting the value to 1.0, as a majority of people who ive asked in mts were in favor of defaulting the value to 0 when thrust vectoring is not found.
| @@ -1305,7 +1311,7 @@ public double addToForceOutput(Point3D force, Point3D torque) { | |||
| engineForce.set(engineAxisVector).scale(thrust); | |||
| force.add(engineForce); | |||
| engineForce.reOrigin(vehicleOn.orientation); | |||
| torque.add(localOffset.crossProduct(engineForce)); | |||
| torque.add(localOffset.crossProduct(engineForce).scale(currentThrustVectorMultiplier)); | |||
There was a problem hiding this comment.
You mentioned this There are no LCs for defaulting the value to 1.0, as a majority of people who ive asked in mts were in favor of defaulting the value to 0 when thrust vectoring is not found.
This means that torque will never be added by default, where it was before, since all engine torque will be scaled by 0, and multiplying anything by 0 makes it 0. Are folks SURE they want to remove thrust-torquing by default? This will result in jets with an engine out behaving differently than propeller craft with engines out, since propellers will apply torque but jets won't.
There was a problem hiding this comment.
you wouldnt believe the storm of complaints about GAP right now due to engines being located away from model origin points. even though they shouldnt vector. the amount of torque being applied is huge in some cases leading to planes doing wheelies or stoppies just by throttling up and stationary
There was a problem hiding this comment.
well i think the problem may also due to mts doesnt take into account the moment generated by lift and gravity, the list and gravity force are lift force are apply at the same position, so if the engine are lower or higher than z0, the thrust vectoring will make the plane pull its nose up or down even at very speed, maybe we need a CG system?
big thanks to conman for helping me fix up my jank ass code cause he knows java and i dont
Adjustable thrust vectoring value for engine parts, as thrust changes to mts physics system with thrust vectoring has proven to be a headache for me and other PAs, especially those from GAP. There are no LCs for defaulting the value to 1.0, as a majority of people who ive asked in mts were in favor of defaulting the value to 0 when thrust vectoring is not found. Also, this jet thrust vectoring is VMable Please let me know in MTS if theres any issues or code oversights.