Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop #16

Merged
merged 15 commits into from
Jul 24, 2014
Merged

Develop #16

merged 15 commits into from
Jul 24, 2014

Conversation

Peppie84
Copy link
Owner

Leave a comment

Starstrider42 and others added 15 commits June 11, 2014 18:28
Does not prevent unnecessary rolls yet. Required changing interface of `SteerShipToward()`, Required adding some memory code to `FlightComputer` that may best belong in some other module.
Conflicts:
	src/RemoteTech2/FlightComputer/FlightCore.cs
This fix consists basically only of a gimbal vectoring calculation update. The old code seemed to be from an earlier version of KSP.
The bug manifested itself in a craft that would not cahnge orientation whatsoever when the Flight computer was enabled. It only started to jerk around and kept facing the orientation it was facing in. This was independent of the mode of the Flight Computer. The bug can be easily reproduced by adding the following .cfg file and using the Flight Computer on the Stayputnik probe core:

@part[probeCoreSphere]
{
  !MODULE[ModuleReactionWheel]
  {}
}

I encountered this bug while playing with the RealismOverhaul mod, which removes from the reaction wheels from essentially all early tech probes.

I also fixed a divide by zero bug that crashed KSP, when using the above setup.

No mod other than RT2 and the custom .cfg file mentioned above are required to reproduce the bug.
Peppie84 added a commit that referenced this pull request Jul 24, 2014
@Peppie84 Peppie84 merged commit 0206a6a into Peppie84:development Jul 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants