Applies the velocity correction from drift compensation (if any).

Calculate the force of gravity, using drift compensation if in orbit and the compensation is better than not. Ease gravity coming off rails while landed/splashed.

< convert inertial to rotational reference frame

< Calculate gravitic acceleration as difference between current velocity and velocity after integration (i.e. at start of next fixed frame).

< for use in GotRotFrameVel

Will calculate center of mass and total mass, mass-weighted average linear and angular velocity, moment of inertia, and angular momentum Depends on FlightIntegrator setting part.physicsMass. If vessel is unloaded, use traditional calculations based off stored values and root part.

< set by FI based on physicsless children

< add the part inertiaTensor to the ship inertiaTensor

< add the part mass to the ship inertiaTensor

< add the part distance offset to the ship inertiaTensor

< was just set before.

< was set at start of our run

Called by Vessel.GoOffRails

Called by Vessel.GoOnRails. Clears any post-integration velocity offset.

Does the main physics calls. Run from fixed update. Bits run in Update.

Parameters

doKillChecks

Do we check if the vessel should be killed?

< if it's already queued, don't worry about it

< Handle orbit fixups and rails positioning and anything from the prior frame

< Clean up state from the prior frame

< assume we don't have to correct

< Calculate vessel COM and velocity for the current pos and rb velocities.

< Calculate the gravity that will be integrated (or just stored if on rails) this frame.

< Calculate the gravity that will be integrated (or just stored if on rails) this frame.

< Run Vessel's fixedupdate code that checks if we should die

< reset so if >1 fixed frame per update loop we don't skip the above!

< in case we set this and we die but orbitdriver doesn't.

Run when a vessel initializes in flight

This will update pos/rot if landed/splashed and on rails

< don't set pos here since we set pos right after.

Used for loaded/unpacked vessels so display matches physics. Runs most of what FixedUpdate does. However, it does so with zero time offset and does not calc gravity (that happens in next fixed frame). Finally, it signals to next fixed frame it doesn't have to rerun this stuff

The fictitious forces for when in a rotating frame

Tell Pre to correct velocity on the next frame (or in Update)

Are we easing?

The proportional increase in g each tick. Default: 1/16th, so 16 frames of easing.

Did we set a control lock?

Acceleration passed to Vessel for calculating perturbation/g force

The true acceleration of gravity at this instant, minus any fictitious or drift-correcting force

The acceleration passed to PhysX (when not correcting drift)

The last UT the Update() update ran in. For detecting pause.

Was the vessel packed in the last fixed frame?

If true, runs phys calcs in FixedUpdate, if false we already did them in Update (post-integration) and don't need to rerun.

The velocity changes to apply, pre and post integration (if correcting drift)

The reverse: did we do them in Fixed this frame?

Were we correcting drift?

publicly accessible Easing property