Skip to content

Latest commit

 

History

History
169 lines (115 loc) · 5.58 KB

README.md

File metadata and controls

169 lines (115 loc) · 5.58 KB
Raw

MechJeb2

Anatid Robotics and Multiversal Mechatronics proudly presents the first flight assistant autopilot: MechJeb

MechJeb2 is a mod for the game Kerbal Space Program. To learn how to use it, visit the wiki. For more info, visit this KSP forum post.

Table of Contents

Install

Manual install

Download

Download from Jenkins: https://ksp.sarbian.com/jenkins/job/MechJeb2-Release/

Unpack

Unzip the zip in KSP GameData directory. You should have something that looks like that :

Kerbal Space Program
-- GameData
   -- MechJeb2
      -- Bundles
      -- Icons
      -- Localization
      -- Parts
      -- Plugins

Via CKAN

CKAN has all the release of MechJeb, just install it as usual.

Development version of Mechjeb

If you want the unstable dev version of MechJeb then :

  1. Open CKAN settings (Settings => CKAN Settings)
  2. Press the New button
  3. Select the MechJeb-dev line, click OK and exit the options.
  4. Refresh
  5. Select "Mechjeb2 - DEV RELEASE" in the list
  6. Then "Go to Change" to install

Common Issues

  1. Why is the Mechjeb menu not showing?

    Make sure you have the part on your ship (AR202 case in the Control section).

  2. (Windows) I cannot find Mechjeb anywhere, there aren't even parts in the R&D facility!

    Some Windows protection and anti-virus software can sometimes block KSP from loading MechJeb. You should install KSP outside the C:\Program Files (x86)\ directory. Steam has an option to change the install directory of a game or you can just copy the directory somewhere else.

  3. Why is some Mechjeb function not available?

    Science and career mode requires you to unlock some specific node in the Research and Development tree. You also may need to upgrade the tracking station to level 2 (game code restriction we can't do much about).

  4. How do I report a bug?

    Check if your problem has already been reported: https://github.com/MuMech/MechJeb2/issues
    If you found a problem which is similar to yours, feel free to add more information to the existing issue.

    If you cannot find the problem, get a log and create a new issue with a descriptive title of the problem.

Development

Maintainers

Code Standards

  1. No var: use explicit types.
  2. Prefer single lines, when possible: especially if-else blocks!
  3. No null-conditional operators: Unity 4.x has a custom == for checking object nulls.
  4. Assembly version needs to remain at 2.5.1.0; file version can be incremented.

Third-party libraries

Build

Linux

The project uses Mono and Make to build the addon, make sure you have both installed.

  1. (optional) Set your KSP directory
export KSPDIR="${XDG_DATA_HOME}/Steam/SteamApps/common/Kerbal Space Program"
  1. Build the mod
make build
  1. (optional) Install the mod into your KSP directory
make install

Windows

  1. Install the version of Unity that KSP uses ( Currently 2019.2.2f1 )

  2. Configure your system environment variables and add:

  • KSPDIR set to where your KSP install is ( usually **C:\Program Files (x86)\Steam\SteamApps\Common\Kerbal Space Program ** )
  • MONO set to the path of Unity current mono.exe ( usually C:\Program Files\Unity\Hub\Editor\2019.2.2f1\Editor\Data\MonoBleedingEdge\bin\mono.exe )
  • PDB2MDB set to the path of pdb2mdb.exe ( usually C:\Program Files\Unity\Hub\Editor\2019.2.2f1\Editor\Data\MonoBleedingEdge\lib\mono\4.5\pdb2mdb.exe )

  1. Load MechJeb2.sln and open the properties of the MechJeb2 project (Right-Click=>properties). In the "Reference Path" section add the KSP libs folder to the list ( usually C:\Program Files (x86)\Steam\SteamApps\Common\Kerbal Space Program\KSP_x64_Data\Managed )

  2. Repeat step 3 for the MechJebLib, MechJebLibBindings, and MechJebLibTest projects.

  3. Perform nuget restore to get external dependencies such as JetBrains.Annotations.

License

Licensed under the GNU General Public License, Version 3.

Portions (in the "MechJebLib" directory) are placed in the public domain and are documented in the affected source code headers.