Project

General

Profile

Bug #13272

Random Radial (in) Acceleration of Orbiting Crafts and Kerbals

Added by dalmationblack over 7 years ago. Updated over 4 years ago.

Status:
Closed
Severity:
Normal
Assignee:
-
Category:
Physics
Target version:
-
Start date:
11/20/2016
% Done:

100%

Version:
1.2.1
Platform:
Windows
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

This has been happening to be since I installed 1.2, and seems to apply when near a large body like Kerbin or the Mun. Anything that isn't the 'original' craft launched from KSC gets accelerated, whether it be a deployed satellite, a lander, or an EVA kerbal. Screenshots here: http://imgur.com/a/KzS2m

History

#1 Updated by JPLRepo over 7 years ago

  • Status changed from New to Needs Clarification

Hi there. Unforunately we cannot look at bugs from an install that has mods installed.
Are you able to produce this bug without any mods installed?

#2 Updated by Azamorn about 7 years ago

I believe I am seeing the same issue, It is some mod that is messing with the orbits and currently I have no way at all to determine which mod is causing the problem to appear.
It usually happpens to me when I am burning my orbit to transfer to a different planet/moon, or when I do my circularization burn. A recurring theme of what is happening goes like this:
1. I am doing a burn prograde/retrograde.
2. Suddenly the burn will stop having any effect on the orbit.
3. The orbit will stay unchangeable or will change on it's own, sometimes radial out, and sometimes radial in.

I would love to get to the bottom of this but I am not seeing any errors on my debug console, and I have no clue where to start to debug this issue, should I provide my modlist?

#3 Updated by Azamorn about 7 years ago

After uninstalling a whole bunch of mods I added recently, the issue was still occurring on the craft I wanted to do a transfer to Mun with, I scratched the probe and rebuilt it with different parts and did not toggle physics warp during the burn and was able to circumvent this odd bug.

#4 Updated by chris.fulton over 4 years ago

  • Status changed from Needs Clarification to Resolved
  • % Done changed from 0 to 100

#5 Updated by chris.fulton over 4 years ago

  • Status changed from Resolved to Closed

Closing, QA has not been able to reproduce this issue for some time and in effort of the database cleanup that is underway this bug is being closed.

Also available in: Atom PDF