gmcnew
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by gmcnew
-
-
Sorry, I actually use 3.3
For ascent.py nothing seem to happen: I press f5(from the IDLE window) and the program seem to finish instantly.
For learn-ascent.py: I get this(copy-pasted):
usage: learn-ascent.py [-h] [-a accel] [-d drag] [-p poolSize]
[--profile filename]
planet alt0 alt1
learn-ascent.py: error: the following arguments are required: planet, alt0, alt1
...
What you should be doing is running learn-ascent.py (from the command line, not IDLE) with arguments, as shown in the example in my Reddit post:
> python learn-ascent.py Kerbin 0 100
Let me know if that doesn't work. =)
-
Which version of python do I need to use the codes?
I tried with version 3.4 (the one I use for coding) but I know that there is no backward compatibility: do I need to use the version 2.7.3?
It works fine for me using Python 2.7, 3.3, or 3.4. What happened when you ran it with 3.4?
-
I actually wrote some Python code to help answer this exact question! =) It simulates a bunch of ascents and reports the attributes of the best one.
One thing the script taught me is that limiting your acceleration (to a fixed number, not just to terminal velocity) can help. If you achieve a high apoapsis too soon, you miss out on the benefits of a slow and steady horizontal climb and end up spending a lot of delta-V to circularize.
You can run the script for yourself, but I'll go ahead and tell you that your gravity turn is ending too high. Assuming your ship has a drag coefficient of 0.2 (MechJeb can show you this), try limiting acceleration to 2.2 g's (21.6 m/s) and using a turn from 8.12 to 45.64 km, with a shape of 57.1%. (Your final flight path angle should always be 0 degrees.) My script says this'll result in a delta-V of around 4399.76 m/s (with losses of 1415.29, 902.19, and 44.14 m/s to gravity, drag, and steering) to get to a 100 km orbit.
(Note: My script also assumes you have MechJeb's "corrective steering" setting -off-, though it doesn't make a huge difference.)
-
Ok, I think this is possibly my fault in the 2.0.7 version >.< It would appear that in my attempt to balance RCS thrust, I'm actually causing some issues. 1, The control body and its internal gyros are very near or at the CoM (cannot be negated as the payload is a 3t solar panel array at the top) and the RCS system comprises only 4 blocks also at CoM, I can't place RCS thrusters forward of the CoM due to the SPA. I reworked the lifter to use 2.5m parts instead and it worked.
However...... MJ drank the RCS fuel like freaking crazy, even on a transit to another attitude, and is really bad about 90 turns. Even if it was settled on the desired attitude, it didnt stop. I dont recall this problem in MJ1 :/
1. Is there a reason you're using RCS for rotation? Pod torque is slower but uses no fuel, and it sounds like this might be a small ship anyway, so a probe core's torque might be enough.
2. Instead of having one set of thrusters very near your CoM, have you tried using two sets (one ahead of CoM and one behind)?
Once again, if you can file a bug and upload your ship, that would be helpful.
-
Both, .4 never gave this problem, not sure on .5 but .6 this bug popped up, and I've been frustrated ever since. Kill Rot will work, kinda, except it takes a lot of time to do it, and uses pretty much all your RCS (80) to do it. I cant figure it out though, its fine with SAS and/or internal gyros, but if thats not enough and you throw in RCS (bigger ships), it cant get itself fixed, and will overcorrect. Each overcorrection gets larger and larger. I've noticed it keeps thrusting until it hits the desired direction, but doesnt bother correcting for the momentum its built up by firing the RCS thrusters, causing an overshoot. It then tries to correct that, with the exact same results as before. Let it go long enough (about a minute or two) and it eventually will flip, and goes all screwy.
edit: hang on, lemme clear the Saved settings from .6, see if that clears it up (doubt it).
edit 2: Negative, no affect at all, messing with the new RCS settings also did not help either. If anything its worse.
Can you upload your .craft and file a bug report containing a very clear list of the steps you take to see this behavior? https://github.com/MuMech/MechJeb2/issues
-
Well, the RCS bug is still there. It cant freaking cope with RCS and the S.A.S.S. attitude hold features. 2.0.4 didnt have this bug, but boy, does .6 have it
whats weird is if it can steer with the internal gyros it does fine.Are you using version 2.0.6? 2.0.7 is the latest.
-
wow its weird seeing all the old posts, also 2.0.6, what is the change from 2.0.5
Did you read the very first post? The version history is linked immediately after the line that says "2.0.6":
Current version: 1.9.8 / pre-release 2.0.6
whats weird is if it can steer with the internal gyros it does fine.
MechJeb Ascent
in KSP1 Mods Discussions
Posted
You seem to be running this from IDLE, not from the command line. You need to run it from the command line.
1. Open a command prompt. (On Windows, this is cmd.exe.)
2. Browse to the directory where these python scripts are.
3. Run "python learn-ascent.py Kerbin 0 100" (with no quotes).
If this doesn't work, please take a screenshot and attach it.