CVS-less install: Difference between revisions
Jump to navigation
Jump to search
imported>Tschachim (→How do I update?: no meshland anymore) |
imported>Tschachim (Orbiter 2010) |
||
| Line 6: | Line 6: | ||
== How do I start? == | == How do I start? == | ||
First, it is recommended that you create a new folder for project Apollo (separate from your main orbiter installation). | First, it is recommended that you create a new folder for project Apollo (separate from your main orbiter installation). This allows a clean install of Orbiter with just Project Apollo, allowing for clean testing. You can choose the location and the name of the new folder as you like, in the following it is assumed that the folder is "C:\ProjectApollo". | ||
Then: | Then: | ||
* Download and unzip the '''CVS snapshot''' using the link at the top of this page. Copy it into the destination directory with all folders intact. | * Download and unzip the '''CVS snapshot''' using the link at the top of this page. Copy it into the destination directory with all folders intact. | ||
* Install Orbiter in your folder, that means in the example above the path of Orbiter is "C:\ProjectApollo\orbiter.exe". This includes the following files at the moment:<BR><BR>'''Orbiter | * Install Orbiter in your folder, that means in the example above the path of Orbiter is "C:\ProjectApollo\orbiter.exe". This includes the following files at the moment:<BR><BR>'''Orbiter 2010-P1 Edition''' (http://orbit.medphys.ucl.ac.uk) | ||
** | ** orbiter100830.zip<BR><BR>Optional:<BR> | ||
**Earth091124_11_14.zip | |||
** | **Moon090730_L11.zip<BR>You can install every other Planetary extension package, too.<BR><BR><div style="margin-left: -1.5em;">'''OrbiterSound 3.5''' (http://orbiter.dansteph.com)</div> | ||
** | |||
** OrbiterSound35.exe<BR><BR><div style="margin-left: -1.5em;">Orbiter and OrbiterSound should not overwrite any of the CVS files.</div><BR> | ** OrbiterSound35.exe<BR><BR><div style="margin-left: -1.5em;">Orbiter and OrbiterSound should not overwrite any of the CVS files.</div><BR> | ||
* Now you have everything you need except probably the most important files, the modules. Please download and unzip the '''Modules Pack''' using the link at the top of this page. Make sure that the directory structure of the archive is retained, usually there's a "Use Folders" option box or similar, which should be ticked/checked.<BR><BR>If you have a compiler/IDE you can build them for yourself, of course: | * Now you have everything you need except probably the most important files, the modules. Please download and unzip the '''Modules Pack''' using the link at the top of this page. Make sure that the directory structure of the archive is retained, usually there's a "Use Folders" option box or similar, which should be ticked/checked.<BR><BR>If you have a compiler/IDE you can build them for yourself, of course: You will find the Project Apollo solution file for Microsoft Visual Studio 2005/2008/2010 in the "ProjectApollo" source folder ("C:\ProjectApollo\Orbitersdk\samples\ProjectApollo\ProjectApollo2005/2008/2010.sln"). All available projects are included in this solution.<BR><BR> | ||
* Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''' | * Start Orbiter, go to the "Parameters" tab and make sure that at least '''Complex flight model''', '''Limited fuel''', '''Radiation pressure''' and '''Gravity-gradient torque''' are enabled. If you're using a Virtual AGC scenario, also enable '''Nonspherical gravity sources'''.<BR> | ||
* Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' module.<BR> | * Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' module.<BR> | ||
* Optionally you can change some options with the '''[[ | * Optionally you can change some options with the '''[[Launchpad Configuration Options]]''' on the "Extra" tab.<BR> | ||
* That's all, now you can try if Orbiter and Project Apollo is working. You'll find the proper scenarios in the '''"Project Apollo - NASSP" scenario folder''' and subfolders. | * That's all, now you can try if Orbiter and Project Apollo is working. You'll find the proper scenarios in the '''"Project Apollo - NASSP" scenario folder''' and subfolders. | ||
Revision as of 14:57, 7 September 2010
|
If you are here, it is because for some reason you wish to install using a CVS snapshot instead of a full download. While this still allows you to update through CVS this method is not recommended as it will not always give you the most up to date files from which to debug. Also, it minimizes your access to some bug fixes that require only a proper CVS update.
If you for some reason cannot use CVS, or have CVS installed but would rather download the snapshot at once, this is the page for you.
How do I start?
First, it is recommended that you create a new folder for project Apollo (separate from your main orbiter installation). This allows a clean install of Orbiter with just Project Apollo, allowing for clean testing. You can choose the location and the name of the new folder as you like, in the following it is assumed that the folder is "C:\ProjectApollo".
Then:
- Download and unzip the CVS snapshot using the link at the top of this page. Copy it into the destination directory with all folders intact.
- Install Orbiter in your folder, that means in the example above the path of Orbiter is "C:\ProjectApollo\orbiter.exe". This includes the following files at the moment:
Orbiter 2010-P1 Edition (http://orbit.medphys.ucl.ac.uk)- orbiter100830.zip
Optional: - Earth091124_11_14.zip
- Moon090730_L11.zip
You can install every other Planetary extension package, too.OrbiterSound 3.5 (http://orbiter.dansteph.com) - OrbiterSound35.exeOrbiter and OrbiterSound should not overwrite any of the CVS files.
- orbiter100830.zip
- Now you have everything you need except probably the most important files, the modules. Please download and unzip the Modules Pack using the link at the top of this page. Make sure that the directory structure of the archive is retained, usually there's a "Use Folders" option box or similar, which should be ticked/checked.
If you have a compiler/IDE you can build them for yourself, of course: You will find the Project Apollo solution file for Microsoft Visual Studio 2005/2008/2010 in the "ProjectApollo" source folder ("C:\ProjectApollo\Orbitersdk\samples\ProjectApollo\ProjectApollo2005/2008/2010.sln"). All available projects are included in this solution.
- Start Orbiter, go to the "Parameters" tab and make sure that at least Complex flight model, Limited fuel, Radiation pressure and Gravity-gradient torque are enabled. If you're using a Virtual AGC scenario, also enable Nonspherical gravity sources.
- Go to the "Modules" tab and activate the ProjectApolloMFD module.
- Optionally you can change some options with the Launchpad Configuration Options on the "Extra" tab.
- That's all, now you can try if Orbiter and Project Apollo is working. You'll find the proper scenarios in the "Project Apollo - NASSP" scenario folder and subfolders.
How do I update?
NOTE: If you decided to do the CVS-less install, you will still have access to CVS updates if you decide later to install a CVS client. For that reason, the instructions are shown here for your convenience.
To get the latest version of Project Apollo you don't have to do the initial checkout again but you have to a CVS update.
- Choose the CVS Update menu item from the Tortoise context menu for each folder below "C:\ProjectApollo", i.e. "Config", "Doc", "Html" etc. CVS will download the changed files and merge the changes into your local copies.
- Download and unzip the latest Modules Pack (using the link at the top of this page).