Installed MechJeb but can't see MechJeb controls

[Orc]

Hi all

 

After more than a year of playing KSP I am ashamed to admit that I still haven't managed to successfully dock two spacecraft. I finally downloaded and installed MechJeb, in the hopes that learning from the best would help me. However this has not been the case.

 

I am running KSP version 1.0.5, downloaded from Steam some time (I think) in November 2015 to January 2016. I installed MechJeb from 'MechJeb2-2.6.1.0.zip' downloaded from the link provided by the KSP forums site.

 

I have tried adding the MechJeb modules to existing and new ships in a Sandbox game, and to ships in a new and an existing Career mode Game. From what I read about MechJeb I was expecting tabs that would contain detailed controls to pop up, allowing me to tell the MechJeb how I wanted the rocket flown (in my case I want it flown until the docking port on the target ship makes contact with the docking port on the MechJeb piloted ship). The modules are clearly doing something because when I select 'Control from here' and leave the controls alone the ship in question does deviate from the course I was flying BUT doesn't get piloted into fatal accidents. This 'robo-controller' does not change throttle settings or executing staging, which suggests to me that those functions haven't been activated yet.

 

If it makes any difference in the existing career game I was about halfway through buying all the 300 Science Points technologies, and had successfully landed a couple of missions on both the Mun and Minmus. Missions to Duna are on their way, and I have gotten the first Science Points from orbiting the Sun. 

 

What am I doing wrong? What have I (likely) screwed up?

 

Any help would be welcome.

 

Thanks.

 

Regards

Orc

[Cpt Kerbalkrunch]

You've been given a sign. Cleanse your system of this unclean entity.

To be a bit more serious, I'm sure there's a dedicated Mechjeb thread somewhere on the forum, if you don't get the answer here. I remember my first docking as one of those "jump out of your chair" moments. It's something where, if we were in the same room, I could show you in about 10 minutes. Sometimes videos just aren't able to explain things in the way you need them to. I had given up on the docking training mission, cuz I couldn't make it work. Finally did it in-game about 3 months later and it completely changed the game. Not to mention the change in my confidence level afterward. Out of curiosity, is it the rendezvous that you have trouble with, or the actual docking?

[Harry Rhodan]

1 hour ago, Orc said:

I am running KSP version 1.0.5, downloaded from Steam some time (I think) in November 2015 to January 2016. I installed MechJeb from 'MechJeb2-2.6.1.0.zip' downloaded from the link provided by the KSP forums site.What am I doing wrong? What have I (likely) screwed up?

Any help would be welcome.

You try running a mod made for version 1.3 with version 1.0.5.

[dangerhamster]

You could try this build, https://ksp.sarbian.com/jenkins/job/MechJeb2-Dev/578/ or a build around this version. Versions from #579 are for 1.1.

 

Edited June 19, 2017 by dangerhamster

[Orc]

4 hours ago, Cpt Kerbalkrunch said:

You've been given a sign. Cleanse your system of this unclean entity.

To be a bit more serious, I'm sure there's a dedicated Mechjeb thread somewhere on the forum, if you don't get the answer here. I remember my first docking as one of those "jump out of your chair" moments. It's something where, if we were in the same room, I could show you in about 10 minutes. Sometimes videos just aren't able to explain things in the way you need them to. I had given up on the docking training mission, cuz I couldn't make it work. Finally did it in-game about 3 months later and it completely changed the game. Not to mention the change in my confidence level afterward. Out of curiosity, is it the rendezvous that you have trouble with, or the actual docking?

Hi all

 

Installing a mod was not my first choice, especially seeing as my computer is a bit on the low-end in terms of specs. I don't think it has the horse power to accommodate too much extra. 

 

I don't have access to videos because I'm stuck on the ass-end of the Internet, and downloading them would be too prohibitive in (a) cost and (b) time. Yes there are still some places on the planet (Earth) that don't have access to affordable (or free) broadband-style Wi-Fi. 

 

But to answer Cpt Kerbalkrunch's question: I am capable of doing a pretty good rendezvous, enough to qualify to complete the 'Rendezvous two ships in orbit' contract. I can get a closest approach down to 200 meters and around a 15 m/s velocity difference and then I'm stuck. I accelerate (gently with a main engine using reduced thrust or with RCS) to kill off the remaining difference in velocity and suddenly the distance to target is growing or the velocity is growing. Do a quick flip around and reverse the changes and the same thing happens again. I can do this silly thruster dance until the ship runs out of fuel / mono-prop / electricity (or the crew mutinies) and not get any closer. If I look at how the other side of the ship's orbit is changing on the 'map' view I suspect the velocity changes are dragging the two ships' orbits out of alignment. 

 

What to do? Any advice will be appreciated.

 

Regards

Orc

 

[bewing]

The "retrograde" marker is your friend. In target mode, retrograde is the direction that will slow you down with respect to your target -- all the way to zero. Then you point your rocket at the target and do a very light burn. That will get you drifting slowly toward your target and when you get really close, you do the process again.

 

[Weywot8]

Try practicing docking at a much higher orbit, the higher the better - ++500km or so above Kerbin or better yet, Minimus. In low orbits, as you try to approach the target, you are also making changes to your orbit that will rapidly pull you away if you don't dock quickly. 

Keeping that in mind, if you have control of both ships, then try to orient and approach the docking port from either  or  direction. Movement in this direction just changes your inclination, orbital period stays relatively the same for a given dV. From the sounds of things, you are doing an approach with a large / component so paradoxically, as you try to slow down/speed up, your orbit changes alot, and it pulls you away relative to the target. At higher orbits, there is a much larger window for this sort of maneuver to work before your new orbit takes over.

Stick with MechJeb and make a note on how they time their rendezvous burns and pick up some tricks there. Also, to practice the docking part of docking, use MJ's maneuver planner to auto-execute the following.

• set up Hohmann transfer to target
• fine tune closest approach to target (50m)
• match velocities to target at closest approach. 

This gets you 50-65m within you target with almost zero relative velocity. Perfect setup for manual docking practice and figuring out what works and what doesn't. 

Once you figure it out and get the hang of it, docking in lower orbits is more manageable.

[Harry Rhodan]

1 hour ago, Orc said:

I don't have access to videos 

Well, I think the pictures in this old thread are still worthwhile and much simpler to download and keep:

 

[Cpt Kerbalkrunch]

@Orc I always aim for a rendezvous of 100 meters whenever possible, but 200 is definitely good. At this point, relative velocity is all-important. A 15m/s rendezvous is more of a high-speed flyby. All you can do with that is hope you don't hit each other. You're right there, though. With your navball set to "Target", hit Retrograde hold on your SAS. You're basically pointing away from your target. Now accelerate (nice and easy) until the relative speed drops to zero. You are now "stopped" (for lack of a better word) relative to one another. Now set your SAS to "Target hold". You should now be pointing directly at the other ship, which is just sitting there. You should also right-click your docking port and select "control from here".

Now switch to the other ship. Target your original ship and set Navball to "Target", right-click your docking port and select "control from here", and set SAS to "Target hold". Both ships are now lined up, docking ports pointed at one another, and (relatively) not moving. Now take control of whichever ship is going to do the docking and engage RCS. Leave SAS just on "Hold" at this point so you can adjust course if necessary. Press H to move forward, adjusting course with W,A,S,D as necessary to keep your prograde marker centered on the Target marker. Stop accelerating at about .2m/s. That seems ridiculously slow, and it is, but that's what timewarp is for. If you're new at docking, better to speed up time than speed up your ship. As you're moving together, if your prograde marker starts drifting one way or another, stop timewarp and adjust course. If you ever feel like it's getting away from you, just hit N to slow down until your relative velocity is back to zero, then aim the ships toward each other and start moving forward again.

Eventually you'll get there. I swear to you that if you keep trying, you'll get it. Docking is one of those things where, after you do it a couple of times, you'll wonder why you had such a hard time in the first place. Good luck to ya. Just stay with it and don't give up.

 

Crap. Was typing this out over a couple hours (stuck at work, as usual) and didn't notice the other replies. Didn't mean to imply that they weren't correct.

Edited June 19, 2017 by Cpt Kerbalkrunch

[Ty Tan Tu]

We'll go over the absolute basics first. If you have the Steam version, it has probably auto updated to 1.3. It is shown in the bottom right corner of the screen.

You GameData folder should look something like this. You might not have the top three folders (that is a different mod) but make sure your MechJeb2 folder is there. Also notice that I am using ModuleManager.2.8.0.dll which you will need if indeed you are on version 1.3.

 

Now you should be able to place the MechJeb2 part. Notice the MechJeb2 at the upper right on your screen after the part is placed.

 

When out of the hanger the 'MJ' icon will be on the right. That is where you get the MechJeb2 menu.

 

I am sorry if this is too basic, but on the off chance it helps someone else I thought I would post it.

Edited June 20, 2017 by Ty Tan Tu
Oops I hit Submit post rather than Insert Other Media

[Ty Tan Tu]

If you are indeed on version 1.0.5, go here https://ksp.sarbian.com/jenkins/job/MechJeb2-Dev/ and download Build 698. I think the current ModuleManager.2.8.0.dll should still work (don't quote me on that), but let us know if you are still having problems. 

[Orc]

Hi all

 

Thanks for all the advice and help. 

 

I am in fact stuck running 1.0.5. I had to use a laptop (notebook) computer in a unlimited public Wi-Fi space to do the original Steam and KSP download, and my home internet connection is simply too slow and too expensive to use for updates. And the laptop's networking has stopped working. 

 

The docking advice makes it clear to me that there are one or two more things I need to learn about Rendezvous before I can realistically expect to dock.

 

To  Ty Tan Tu: Thank you for your detailed explanations. I will be putting your words into action at the next available launch window.

 

Kind regards to all,

Orc

[Orc]

Hi all

 

I examined the KSP.log file and found the following:

 

[ERR 07:54:55.236] AssemblyLoader: Exception loading 'MechJeb2': System.Reflection.ReflectionTypeLoadException: The classes in the module cannot be loaded.
  at (wrapper managed-to-native) System.Reflection.Assembly:GetTypes (bool)
  at System.Reflection.Assembly.GetTypes () [0x00000] in <filename unknown>:0 
  at AssemblyLoader.LoadAssemblies () [0x00000] in <filename unknown>:0 

Additional information about this exception:

 System.TypeLoadException: Could not load type 'MuMech.FuelNode' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.MechJebModuleMenu' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.ReentrySimulation' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.SimulatedParachute' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.SimulatedVessel' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.FuelFlowSimulation+<>c' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.ReentrySimulation+SimCurves' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.ReentrySimulation+Result' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.VesselExtensions+<>c' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.VesselState+ResourceInfo' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'MuMech.SimulatedPart' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type '<>c' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type '<>c__DisplayClass40_0' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'DisplayOrder' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type '<>c' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type '<>c__DisplayClass29_0' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'Outcome' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'prediction' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type 'DragCubePool' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 System.TypeLoadException: Could not load type '<>c' from assembly 'MechJeb2, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null'.

 

 

I can only assume that this is something bad that I've done wrong. Where do I go from here? Is there a specialist forum for this sort of thing?

 

Thanks and regards to all,

Orc