Map & Tracking Station In Map Mode the Collision Trajectory with Mun Causes Locked PE Information to Drop its Pin When Corrected Back to a Non Collision Trajectory (Maneuver Node or Not)

[Anth]

KSP1 Version: 1.12.5.3190
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

Expected Behavior:
Look to video evidence below for KSP2 0.1.1.0 (and KSP1 1.12.5)
Observed Behavior:
Look to video evidence below for KSP2 0.1.2.0

How to Replicate:

1. Extract Attached Save folder to the appropriate location.
2. Load 0110SaveKerbinMunEncounter.json (used for the video evidence below)
3. Find the PE that is in the videos below for KSP2 for the Mun and pin/lock it to show the actual distance information.
4. Right Click on Kerbin and focus.
5. Get close to Kerbin for finer movement of the node around Kerbin.
6. Move the node around Kerbin to move the Periapsis (locked info) until it collides with the Mun.
7. Move the node in the other direction to get the PE to show again.

Results of Testing:

• KSP1 video is there to show how it was done before KSP2
• 0.1.1.0 appears to act the same as KSP1 which is good
• 0.1.2.0 is dropping the information when the PE shows up again. Following image (rough I know) shows what it's going from and to.

             

Video Evidence:
KSP1 1.12.5 (Good):
https://youtu.be/54x8IBEsNgw (8 Seconds)

KSP2 0.1.1.0 (Good):
https://youtu.be/skEDT-TOh6Q (16 Seconds)

KSP2 0.1.2.0 (Bad):
https://youtu.be/6VF9UrSpBo4 (11 Seconds)

Save Folder:
https://www.dropbox.com/s/8b79cmim05yct4p/Maneuver%20Node%200110.zip?dl=0

Additional Information:
Maneuver node isn't necessary to cause this to happen.
 

@Dakota For your consideration.

Edited June 1, 2023 by Anth12
Slight Adjustment of the title

[Anth]

I also did the following bug report with concerns over multi version bug testing (like this one) with all the settings/saves etc all being put into the same appdata folder.

 

No problem with the appdata folder being created by  0.1.2.0 with 0.1.1.0 in regards to the regression issue here as far as I know. It acted exactly how I expected.

Also the supplied save file was created in 0.1.1.0. Then tested in 0.1.1.0 and then 0.1.2.0.