OHM GEP - Mariner 10

[OrbitHangar]

Author: missleman01

MARINER 10- By the early seventies NASA had launched many many probes to the planets, but no one had yet visited tiny Mercury. NASA wished to do so but could not afford a Titan rocket needed for a direct approach. Instead, NASA took its highly successful Mariner Spacecraft Bus, added a sunshield and new cameras, and launched it on a stock Atlas-Centaur. Utilizing a "reverse" gravity assist, Mariner 10 flew by Venus, using its influence to slow the spacecraft and deflect it deeper into the Solar System for a Mercury flyby.*

DOWNLOAD

 

[ncc1701d]

Not working

I did clean install of Orbiter 031217 on my vista machine.
Then unzipped this addon. Everything seems normal but Orbiter crashes when trying to run the scenario. Dont know what to do or if it requires support files.

 

[garyw]

First thing I'd do is get the latest version of Orbiter, it's easier for people to assist if you use that one in place of an older version especially as it's a spacecraft/multistage vessel.

 

[ncc1701d]

I unzip the file in Orbiter 10 as well.
It crashed and here is my orbiterlog info
where i would find Sol_1975.cfg I dont know.
the mentioning of obsolete api function led me to belive I had to use older version of orbiter but I am new at all this.
----------------------------------------
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 6.98413e-008 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Mobile Intel(R) 4 Series Express Chipset Family)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1600 x 900 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1
Loading 15382 records from star database
---------------------------------------------------------------
>>> ERROR: While initialising solar system Sol_1975:
>>> File not found: .\Config\Sol_1975.cfg
>>> [Orbiter::CreateRenderWindow | .\Orbiter.cpp | 726]
---------------------------------------------------------------
>>> TERMINATING <<<

 

[orb]

where i would find Sol_1975.cfg I dont know.

Did you try to find it there: [ame="http://orbithangar.com/searchid.php?ID=501"]GEP - Earth 1975 - DSN[/ame]?

 

[Columbia42]

And if you don't feel like downloading that you can just switch the system to Sol in the scenario file instead of Sol_1975

 

[garyw]

>>> ERROR: While initialising solar system Sol_1975:
>>> File not found: .\Config\Sol_1975.cfg
>>> [Orbiter::CreateRenderWindow | .\Orbiter.cpp | 726]
---------------------------------------------------------------
>>> TERMINATING <<<

That's the problem.

Edit the scenario file and change SYSTEM sol_1975

to

SYSTEM sol

then try again.

 

[ncc1701d]

ok I did download that "GEP - Earth 1975 - DSN "and it fixed that problem.
I did not try yet the second suggestion of

"Edit the scenario file and change SYSTEM sol_1975

to

SYSTEM sol"

Just wondering though if I change it to SYSTEM sol will my simulation still be accurate for a launch that took place in 1975?

 

[tblaxland]

Edit the scenario file and change SYSTEM sol_1975

to

SYSTEM sol

then try again.

IIRC the GEP scenarios require sol_1975 for the launch pads.

 

[Starshipexplorer]

Hi ncc1701d. Even though you changed Sol_1975 to Sol, if you haven't changed the MJD reference in the scenario, the date in the upper right screen should reference 1973.

 

[rseferino]

One question. I'm running this add-on in Orbiter 2010-p1, but the Atlas-Centaur does not appear on the launch pad. I install a clean version but still does not appear.

 

[IronRain]

Do you have the new [ame="http://www.orbithangar.com/searchid.php?ID=4661"]stage.dll[/ame]? Sometimes, there is a stage.dll included in an add-on. You have to copy the new stage.dll again if that happens..

 

[rseferino]

Thanks IronRain. I try that ... tonight.

 

[ncc1701d]

making it work

hey rseferino
I am new to the add ons thing. I noticed some addons I used so far you could press the p key and see a predone scenario run.
I dont think this mariner 10 addon has this. You said you have it on your orbiter 2010?
Do you know how to launch this rocket etc?
I dont know if its an elaborate thing I need to study or if I can watch a predone scenario.
Anything you could share with me thats easy to get this puppy up? or to see mariner orbiting? I am new to to orbiter. Somethings are easier than I thought and somethings are alot harder.
Maybe their a tutorial covering rocket launches as oppossed to the gliders.
thanks

 

[rseferino]

I do testing, but ... perfect run in 2006 even perform the flyby to Mercury. In 2010 (and 2010P1) the problem it poses is this:

The new stage.dll solves the problem of a rocket stage "disappeared" after being separated.

 

[Starshipexplorer]

Hi ncc1701d. In reference to the P key, one has to have a guidance file (it's a text file) and the guidance_file command in the scenario for the P "auto launch". The guidance file is easy to make, and you have to edit the scenario adding the command line. The Mariner10 does not have one, but you can customize one for it. Hope this helps.