Anth

That's in response to your video with the TR4 wheels.

@Jaypeg Moved this out of the archive. @dandoesstuff merged yours with this one, though I don't think its off center but that its just missing part of the bar on the right side.

Swapped a few comments/bug reports between this and the following:

Swapped a few comments/bug reports between this and the following:

@Abelinoss Pulled this bug report out of the archive.

@talon jasra and @Skorgarim Moved your bug report out of the archive. @ShadowZone Merged yours with this one.

@Jeq Moved this out of the archive. @Abelinoss merged yours with this one. Discord changes its links so your pictures will only work for a little while. Can you please reupload them in a new bug report and and mention me in the bug report and link to here?

This appears to be fixed. Moving to the archive.

Jool was fixed in 0.2.1.0 I split the Jool issue from the moon issues. Moons are still an issue which is here:

There were two issues: Jool blocking solar panels when they shouldn't be. Moons blocking solar panels when they shouldn't be. Jool is fixed. The moons aren't. I have moved any Jool related issues into the following and set it as fixed: I am sorry to say that the votes were lost on splitting these two issues.

@theplanetmercury Changed the title and added a few screenshots. Thanks for submitting.

@Nenovike Thanks for the bug report. I have added a video following your steps.

@SuperBoots There's two bugs. One is the landed bug which you are demonstrating in that video, and there is one where the AP/PE indicators that are still showing (which is what this bug report is about). Here is a link to what I believe you indicated:

Using the save file supplied by @The Space Peacock I found that retracting the transmitter on his rover actually restored communications. Might not be the only way that this bug is occurring though.

@Davidian1024 Thanks for the information. Sorry I was overseas and didn't log into the forums over that time.

Sorry I haven't responded. Usually I keep up with forum notifications but I didn't have my login while I was overseas. So it has less issues with slower ram? That's weird. If you want to give me that json file, can you please create a new bug report with my name in the title and a link to this bug report?

Was able to reproduce the issue. Added to the original post.

@DaVincGa There are struts on your craft file which some how ended up connected from a part and then were reconnected to the same part. Once I removed those I was able to launch your craft file properly. I will have to play around to figure out how to make struts connect to the same part because that should be impossible.

The memory test does take a while.

@Filed.Teeth The corrupted save file is missing a chunk of information at the end for some reason. This could be a memory issue. Can you please do a memory test? To do this: (according to google) Step 1: Press the Windows key + R to open the Run command. Step 2: Type in “mdsched.exe” and hit Enter. Step 3: Choose between the two options (either to restart and check the RAM now or to check the RAM at the next system startup) and proceed with the diagnostic test.

From the video this looks more like it was a TS-12 separator.

@oro Merged yours into this one. Yours was submitted first so you are counted as the original poster.

@Jeq Merged yours with this one.

@thegreatgonz The game only shows the next 2 closest approaches from the vessel’s/maneuver node’s position. If the maneuver node is placed further along the orbit than the vessel is currently, it may include the next one.

This is fixed as of 0.2.0.0