Parts & Vessels Rovers are Hitting a Physics Glitch Every 1000m from the Location of Rover Being Loaded into the Game With Disastrous Results

[Anth]

Reported Version: v0.1.2 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB

Smaller Rover to Show Severity:

Spoiler

Video Evidence:
Smaller Rover Spinning out at Approximately 1000m.
https://youtu.be/kbh2DyfRzb4?t=26 (starts at 26s)

To Replicate:

1. Load SmallerRoverTestSave
2. Move forward to just after the first Kerbal at 25-30m/s. Don't Timewarp to get there.

Save File: SmallerRoverTestSave.json
Craft File: SmallRoverTestCraft.json

Larger Rover to show its at each 1000m interval:

Spoiler

Kerbals standing at 1000m, 2000m, 3000m, 4000m, 5000m, 6000m, 7000m, 8000m

Video Evidence:
Larger Rover Reacting to some sort of glitch at 1000m intervals.
https://youtu.be/ruS_RwW27xs (Use the time stamps to skip the travel between if desired)

Note: Didn't happen for the second to last Kerbal. Last one was unreliable because the rover flew over onto the beach

To Replicate:

1. Load LargeRoverTestSave
2. Be about 30m/s at each Kerbal. Don't Timewarp.

Save File: LargeRoverTestSave.json
Craft File: LargeRoverTestCraft.json

Additional information:

• Quicksave and Quickload and the 1000m glitch will reset the distance and will now happen from 1000m away from that new Load point.
• Physics Warp appears to resets the 1000m glitch point as well.
• Why the Large Rover didn't end up on its side or on its back is because it wasn't travelling fast enough.
• I tried it on Minmus and it did do it at 1000m but I couldn't get consistent results because the surface wasn't flat enough.
• The game is reporting the Kerbal 2000m (not 1000m) away as being on a crash trajectory each time the large rover glitches

[kdaviper]

I wonder if this has to do with the Self-righting quality the wheels seem to have; they appear to attempt to stick to the ground when you roll the craft.

[Sitting Duck]

Old news, but I can definitely confirm this. I tested a new rover out on Eeloo, and every 1000m it wanted to spin out (or did)... This happened every kilometer for 49km because I am an idiot. So this occurred nearly 49 times in a row.

RECOVERY: I finally tried immediately turning on SAS and selecting Prograde each time this happened (and then disabled SAS), which really helped with recovering from the events. Note that I had a reaction wheel inline with the rover.

Edited January 27 by Sitting Duck