Parts & Vessels Disengaging Timewarp Causes a Directional Jarring Visual/Movement Glitch After a Recent Docking Between Two Crafts and Also Undocking Straight After

[Anth]

KSP2 Version: 0.1.0.0.20892
KSP2 Version: 0.1.1.0.21572
KSP2 Version: 0.1.2.0.22258
Operating System: Windows 10
CPU+GPU+RAM: i9 9900K+3070ti+32GB
Mods Used: None

Important:

• To be Clear the Docking Happens in Normal Time. Then Timewarp is Used and Disengaged Afterwards.
• I Don't Believe that the Movement in the Videos is the Cause.

Report is Broken up into three parts:

• Glitch Moving Up with Disengaging Timewarp After Docking.
• Showing From Left and From Right in Separate Videos.
• Docking and Then Undocking Staight Afterwards and Disengaging Timewarp.

Glitch Moving Up with Disengaging Timewarp After Docking:
 

Spoiler

This is a screenshot of the moment that KSP2 registered the docking:

This Shows the Docking from the Craft Moving up and Docking with the Craft Above it and that the Glitch is in the Same Direction after Disengaging Timewarp:
https://youtu.be/gpoOfG6rj-A (17 Seconds)

Important Information:
I believe the distance when KSP2 registers the docking is directly related to the glitch that is happening.
Its like the active vessel (which is on the bottom) is teleporting to the other craft and then disengaging timewarp later on ends up being the distance of the glitch (or close).

Showing From Left and From Right in Separate Videos:

Spoiler

Look for the Left and Right where the docking ports are when KSP2 registers the docking:

Glitch Moving Left with Disengaging Timewarp After Docking:
https://youtu.be/dqQSGDwkZY8 (24 Seconds)

Glitch Moving Right with Disengaging Timewarp After Docking:
https://youtu.be/sTPy0n0GTMo (19 Seconds)

Docking and Then Undocking Staight Afterwards and Disengaging Timewarp:

Spoiler

This is a teleport more than a jarring effect.
https://youtu.be/LpGq2QnW0ro (59 Seconds)

Save File From Videos for Testing:
https://www.dropbox.com/s/4xnijmi6bh1ta57/DockTimeWarpDirectionalTestSav.zip?dl=0

Additional Information:

• Using the save from 0.1.2.0 it appears that this issue has been in the game since 0.1.0.0

Work Around:

• Quick Save then Quick Load (F5 then F9)

Edited June 1, 2023 by Anth12