Open henrylzy opened 2 years ago
I have literally the EXACT same issue. I had a lander on the mun from a previous early mission. And when i was inserting a comm sat into a polar orbit around the mun, the pop up would appear and it would switch to the lander, but the lander this time was in free fall. Then, it switched back to the comm sat, before "reloading a save" and then it would get stuck in this loop of constantly reloading saves. The only way to get out of the loop was to pause when i could and go to the tracking station and terminate the comm sat or the lander. I don't know a fix for this, it's either reduce the range by a lot or uninstalling the mod. I'll go with the latter, to avoid stability issues.
I have the exact same issue as well, and it would seem the range only determines the magnitude of the problem, i.e. <25km means the craft I was in disappears and I'm forcibly switched to the "landed" craft now falling 8000m to its inevitable death. Having PRE ON but set to 2.5km allows my controlled craft enter the range of the landed craft without switching, but the landed craft is still placed about 20m off the ground and takes considerable damage. PRE OFF gives normal behavior.
@SnowFeetus Can you try to disable the TerrainExtender option in the PRESettings file?
I was doing another Mun mission with stock Planets. When my orbiter was on a low orbit(30ish km) and close to the landed spacecraft, PRE notified 'Extending Terrain, Focusing Landed Vessels', the game then switched to the landed spacecraft, which somehow was in mid-air(or mid-space in this case), in a free fall where it's nowhere near the original landing site. I have no way to perform a controlled landing due to lack of electricity and propellent, I used the debug menu to bring it back to the surface, then the game switched back to the mission vessel.
When the mission vessel was about to pass the same landed spacecraft for the second time, the same thing happened. This time, however, I've applied time accelerations before switching to the landed spacecraft, which caused the landed spacecraft to be shot into deep space, instead of in a free fall. During this time, all the readings from KER about the vessels went crazy, and after a few seconds of traveling at lightspeed(metaphorically), the game went into loading then repeating the whole thing, again and again, makes the game unplayable. The game never switched back to the mission vessel.
I've done some research on this and you've mentioned about strange behaviors would occur if the range was greater than 100km. I was using the default config, in which the range was set to 100(I assume that's in km). I then changed the number to 90, but it doesn't help.