MechJeb2

MechJeb2

4M Downloads

delta-v calculations and maneuver node timings fail for rocket with high part count

raygundan opened this issue · 4 comments

commented

I'm not sure what the root cause is here, but I have two similar rockets. One has 630 parts, and while the upper stage is complicated, the lift stages are identical to the simple version with the dummy payload.

The complex payload will fly just fine manually, but MechJeb is weird with it:

-No Delta-V calculations ever display, whether in the VAB, on the pad, or during flight, regardless of whether the cosine loss toggle is checked.
-Any attempt to fly a maneuver node automatically will start the burn exactly at the maneuver node, rather than starting the burn ahead of the node. The burn time calculations in the game appear to be correct, though-- MechJeb is just ignoring the value and starting at 0.

The version with the dummy payload and much lower part count flies fine with MechJeb, and the Delta-V calculations work as expected. I can provide both .craft files if needed, although it appears I can only attach images here.

2014-07-13_00006
2014-07-13_00007
2014-07-13_00008

commented

If this is of any use, this appears repeatedly in the alt-12 debug log:

"[Error]: Too deep hierarchy to perform rigidbody ordering. Nested rigidbodies might look strange."

These errors don't appear with the low-part version. I don't know if it's related or just a red herring.

2014-07-13_00009

commented

The dV problem and the bad node execution are related.
The error message is not from MJ. You should have a longer message in the KSP_Data/output_log.txt file. But I doubt we can do anything about it, looks like a KSP/unity problem.

commented

Thanks for taking a look at it-- once I found the error log in the alt-f12 menu, I wondered if it wasn't MechJeb after all.  I'll dig up the full log when I get home this evening, but I think the answer is probably "stop trying to put that many parts on your rockets."

On Monday, July 14, 2014 12:57 AM, sarbian [email protected] wrote:

The dV problem and the bad node execution are related.
The error message is not from MJ. You should have a longer message in the KSP_Data/output_log.txt file. But I doubt we can do anything about it, looks like a KSP/unity problem.

Reply to this email directly or view it on GitHub.

commented

Closing this as an old MechJeb issue. Many MechJeb issues have had little interest in years, have been fixed for years, do not include adequate replication steps, refer to old problems which are no longer applicable, or are difficult to determine what the problem is. This issue is being closed for one of those reasons. We apologize for any inconvenience, but keeping the TODO list tidy helps the developers.

If this bug/issue is still a problem, please open a new issue. For bugs please try to include a Minimal, Complete, Verifiable Example that explains all the steps required to replicate the issue. A link to the KSP.log file should be ideally included, but is often not sufficient information. Screenshots or short videos are often the best way to show a bug.