Jump to content

[1.12.x] Anatid Robotics / MuMech - MechJeb - Autopilot - [2.14.3] [4th March 2023]


sarbian

Recommended Posts

  • 2 weeks later...
  On 8/5/2023 at 1:07 AM, Phaeton99 said:

Is the Aircraft Approach and Autoland runway list limited to the stock six options?  I have attempted to add more to the LandingSite.cfg but these additions never appear in the list.

Expand  

It wasn't in earlier versions, so I wouldn't expect it to be now. You just need to look at the config file and add in entries based on the set out of runways already in there. You will need to get the co-ordinates at ground level at the begining and ends of the runways you want to add. I did this by building a little wheeled drone core with the mechjeb part added near the base. Then driving it to the ends and using the mechjeb menu to copy the co-ordinates to the clip board. Then pop out using the windows key and paste into a text file. If I remember correctly you need to adjust the set out of the numbers to match how it looks in the config file.

This is one I did years ago to add runways that were added by the Kerbinside mod.
 

  Reveal hidden contents

 

Link to comment
Share on other sites

  • 2 weeks later...

Using Mechjeb 2.14.3.0 (not dev), I've encountered a strange error.

Link to KSP.log https://web.tresorit.com/l/f4DOA#c4VJ_L1OXiP1WMFLgI4hNQ

Series of events:

1.  Tried to get a truss segment to dock with the truss on my ISS.

2.  Docking failed.

3.  See that even though the docking ports are right next to each other, the game says they are 10 meters apart

4.  Decide to take Bill out and detach docking port on station side and reattach

5.  Error spams the debug log:

vpT1JJ0.png

 

The docking ports in question are 2 Habtech2  T-400 Truss Connection Mechanism (integrated type A)  Keep in mind this docking port does dock with itself and already attached a truss segment on the other side.

The one I reattached is:

lLvgLo9.png

Edited by MashAndBangers
Link to comment
Share on other sites

  On 8/18/2023 at 10:20 PM, MashAndBangers said:

Using Mechjeb 2.14.3.0 (not dev), I've encountered a strange error

Expand  

10 meters apart makes it sound like MechJeb is measuring the Centre-of-Mass to Center-of-Mass separation. Without examining the log file (beyond me) I can only wonder if you forgot to use "control from here" with respect to the moving truss' TCM. Apologies if I am preaching to one wiser than I!

Link to comment
Share on other sites

  On 8/19/2023 at 1:05 AM, softweir said:

10 meters apart makes it sound like MechJeb is measuring the Centre-of-Mass to Center-of-Mass separation. Without examining the log file (beyond me) I can only wonder if you forgot to use "control from here" with respect to the moving truss' TCM. Apologies if I am preaching to one wiser than I!

Expand  

Yeah that threw me off.  I checked and I was controlling from the docking port and targeting the proper docking port. 

Link to comment
Share on other sites

  On 8/18/2023 at 10:20 PM, MashAndBangers said:

Using Mechjeb 2.14.3.0 (not dev), I've encountered a strange error.

Link to KSP.log https://web.tresorit.com/l/f4DOA#c4VJ_L1OXiP1WMFLgI4hNQ

Series of events:

1.  Tried to get a truss segment to dock with the truss on my ISS.

2.  Docking failed.

3.  See that even though the docking ports are right next to each other, the game says they are 10 meters apart

4.  Decide to take Bill out and detach docking port on station side and reattach

5.  Error spams the debug log:

vpT1JJ0.png

 

The docking ports in question are 2 Habtech2  T-400 Truss Connection Mechanism (integrated type A)  Keep in mind this docking port does dock with itself and already attached a truss segment on the other side.

The one I reattached is:

lLvgLo9.png

Expand  

Problem solved.  I had downloaded Habtech 2 from space dock when re-installing KSP and that's when the issues came up for this save.  I then replaced Habtech 2 with a download from the github repository and that fixed things. 

Link to comment
Share on other sites

  • 2 weeks later...
  On 8/29/2023 at 10:56 AM, Udav said:

I needed to study the air consumption of an airplane. I found the relevant fields in MechJeb, but they don't work. All parameters except one show "0", although the aircraft is flying safely. Fix please.

Expand  

If you’d kindly check the thread OP, there is a methodology for reporting bugs and getting support.   It goes a long way to getting your issue resolved if you help the devs out some, which includes giving specifics rather than vague “they don’t work”.   

Link to comment
Share on other sites

  • 2 weeks later...
  On 8/19/2023 at 10:25 AM, Kampfsanni said:

The Docking Autopilot has a glitch that let him lock up right before the final push from time to time. Switching it off and directly on again  normaly solves that and will dock immediately.

https://forum.kerbalspaceprogram.com/topic/154834-112x-anatid-robotics-mumech-mechjeb-autopilot-2143-4th-march-2023/page/168/#comment-4247646 

 

Expand  

I managed to reproduce this when I had speed limit at 0.1. Changing the limit to 1 immediately caused it to finish the docking.

I'm not sure to what extent speed limit was a factor or not as in your previous screenshots, you always had your limit set at 1m.

I'll take a look at the code since I was the last one to make major changes to the docking code. (some minor change by someone else but I don't think that's a factor, I managed to repro with an older branch predating that change)

One thing that might be a factor is the undocking and redocking to a different port. If you're initiating docking to another  port from within the bounding box then the docking AP could get confused somewhere along the way because it has to first back out of the box in a safe manner, move around the station and then re-enter the box from a new angle. That's alone involves some complex maneuvering by the AP to get out, go around and then back in. Before I did some revamping of the docking code, it had a nasty tendency to try to fly through the station to get to the new docking port.

I think it might be getting hung up on the corner of the bounding box. It would be trying to maintain the safe distance while simultaneously moving laterally to the docking axis and that could produce contradictory velocity changes.

Link to comment
Share on other sites

  • 2 weeks later...

Why ascent guidance is so excrements? I'm flying this rocket

8F3XQNG.png

I can get it manually to orbit without issue, but MechJeb can't even find a way to get out of orbit. All settings a refactory default. This is the result:

lEbm03g.pngHl64Y4h.png

Like I said, I can fly this rocket to orbit just fine, but no matter what changes I make to the options, MechJeb can't, so I must ask again. Why is ascent guidance so excrements?

Edited by AnFa
Link to comment
Share on other sites

@AnFa Your rocket may not have the control authority to fly the path that MJ is trying to fly. In fact, the Classic Ascent is basically defining a static flight path based on the settings in the Ascent Path Editor.  A rocket with sufficient thrust AND  control authority will get to orbit over Kerbin with the default settings. You say you can get it there manually.  If that's so then adjust the shape of the curve in the editor to match your manually flown path. But understand that the classic ascent guidance doesn't do anything more than follow a statically defined curve. It's on you to either build a rocket that can fly within those parameters or to change the parameters to something your rocket can fly.

Link to comment
Share on other sites

  On 9/26/2023 at 2:03 AM, AnFa said:

Why is ascent guidance so excrements?

Expand  

I can give you one person's perspective. 

Ascent guidance on stock is next to worthless to me. I don't mess around in stock very often, but when I do I don't use ascent guidance at all.

Most of the time I'm in either KSRSS or JNSQ. This is where I use ascent guidance 100% of the time, both PVG and Classic, depending on the vehicle. A full Saturn V stack from BDB will get to 130km x 130km on KSRSS (from KSC) with PVG ascent perfectly on my system. I also use PVG for Titans, and anything that has a single upper stage ignition. For most everything else, I use Classic and do a teeny bit of futzing with the ascent curve shape. The ascent parameters and the TWR of the upper stage are the two things that affect my success more than anything else.

So my thought is that on stock, it's not good. On 2.x, it's very good. And I'm guessing on RSS ... PVG is probably excellent.

Link to comment
Share on other sites

  • 1 month later...

Help. Im not sure what's happened here but my mechjeb tab is on the far top left corner. I don't know why its moved there. I also cannot see any of the controls when I click to activate one, as in I click the auto docker, but the gui doesn't show on screen despite it existing. 

I did have an error loading the game saying I have an outdated firespitter incase that's a cause?

Link to comment
Share on other sites

  On 11/2/2023 at 6:07 PM, MattST said:

Help. Im not sure what's happened here but my mechjeb tab is on the far top left corner. I don't know why its moved there. I also cannot see any of the controls when I click to activate one, as in I click the auto docker, but the gui doesn't show on screen despite it existing. 

I did have an error loading the game saying I have an outdated firespitter incase that's a cause?

Expand  

You can move the MechJeb lid by right click pressing on it and dragging it left and right. As for the your other error, Firespitter shouldn't have anything to do with this

Link to comment
Share on other sites

  On 11/2/2023 at 6:27 PM, AnFa said:

You can move the MechJeb lid by right click pressing on it and dragging it left and right. As for the your other error, Firespitter shouldn't have anything to do with this

Expand  

Right clicking doesn't do anything. Also now the whole GUI just won't show up, not sure what's going on.

Link to comment
Share on other sites

  • 2 weeks later...

I'm having this problem with Landing Info. The Suicide Burn Countdown is being incredibly optimistic. I'm descending to the Mun and if I start the burn at 0, the countdown keeps going into the negatives and I crash. If I start the burn 10s before 0, I still crash. What's going on?

Link to comment
Share on other sites

  On 11/10/2023 at 10:27 PM, AnFa said:

I'm having this problem with Landing Info. The Suicide Burn Countdown is being incredibly optimistic. I'm descending to the Mun and if I start the burn at 0, the countdown keeps going into the negatives and I crash. If I start the burn 10s before 0, I still crash. What's going on?

Expand  

How shallow/steep is your descent? At the point you start your burn, are you doing a straight vertical descent or do you still have a lot of horizontal velocity to kill?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...