Problems with Atlas V

Matte · Jun 4, 2008

Good afternoon.
i'm having troubles with Atlas V.
i tried both the Atlas V bersion 2 Beta 0.3 by Jim Clem and the re-edition Realistic Atlas V by Ryan Walean. using MRO i have no problem. as soon as i try to use the rocket from the scenarios included in the package of Atlas V it crashes telling me that it's a critical error, and to see the log:
so this is my log:

HTML:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 3 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module TrackIR.dll [API v.060425]
TrackIR module not found.
Module ScnEditor.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module OrbiterSound.dll [API v.060425]
Module Meshdebug.dll [API v.060425]
Module InterMFD51.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module FlightData.dll [API v.050206]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module GenesisMFD.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Render device: Fullscreen 1280 x 960
Device has hardware T&L capability
Joystick throttle: SLIDER 0
Joystick throttle control detected
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
>>> ERROR: No vessel class configuration file found for:
>>> ERROR: Multistage\Multistage
>>>        [C:\Source\Orbiter\Vessel.cpp / 248]
>>> TERMINATING <<<

can anyone help me please?
thanks
Matte

DaveS · Jun 4, 2008

You need to install the original Multistage.dll.

Matte · Jun 4, 2008

that, i suppose, can be found at the website of the developer!

DaveS · Jun 4, 2008

Matte said:
that, i suppose, can be found at the website of the developer!

Here: http://http://users.swing.be/vinka/base_package_040110.zip

Matte · Jun 4, 2008

Atlas now working perfectly! thanks a lot for your help.

Matte · Jun 7, 2008

ok, now that my problems with Multistage are solved and i can use the rockets, let me ask you another question.

how can i set a payload for the rocket? i don't know if i have to act on the CFG file or the scenery one...could you please give me some guidelines to set payloads for Atlas V, please?
Thanks a lot

DaveS · Jun 7, 2008

Matte said:
ok, now that my problems with Multistage are solved and i can use the rockets, let me ask you another question.

how can i set a payload for the rocket? i don't know if i have to act on the CFG file or the scenery one...could you please give me some guidelines to set payloads for Atlas V, please?
Thanks a lot

It's the INI file you have to edit. The section you want to edit is the [PAYLOAD_x] section.

MajorTom · Jun 7, 2008

DaveS said:
It's the INI file you have to edit. The section you want to edit is the [PAYLOAD_x] section.

And make sure you stay under the max. payload capacity in kg, else the payload will likely fail to reach orbit. (Probably obvious)

Matte · Jun 7, 2008

DaveS said:
It's the INI file you have to edit. The section you want to edit is the [PAYLOAD_x] section.

ok, perfect. i have identified the section we're talking about. i tried to put Carina's data, but nothing happens when i load the scenario. maybe something missing in the .SCN? or something wrong in .INI? could you please post just an example of how a INI should be compiled?
thanks a lot again

MajorTom · Jun 7, 2008

Matte said:
ok, perfect. i have identified the section we're talking about. i tried to put Carina's data, but nothing happens when i load the scenario. maybe something missing in the .SCN? or something wrong in .INI? could you please post just an example of how a INI should be compiled?
thanks a lot again

How about posting your full *.ini file here, so we can see if there is something wrong with it? Multistage and spacecraft modules are sensitive to errors.

MT

Matte · Jun 7, 2008

HTML:

[MISC]
cog=5

[STAGE_1]
Height=32
Diameter=4
EmptyMass=20743
FuelMass=284089
Thrust=4153416.7 
BurnTime=253
off=(0.,0.,0.)
MeshName="ATLASV/400CCB"
ENG_1=(.757,0,-20)
ENG_2=(-.757,0,-20)
ENG_DIAMETER=2
speed=(0.,0.,-5.)
PITCHTHRUST=361994.1
YAWTHRUST=361994.1
ROLLTHRUST=361994.1

[STAGE_2]
Height=13
Diameter=3
EmptyMass=1914
FuelMass=20830
Thrust=147000
BurnTime=842
off=(0.0,-.25,22.2)
MeshName="ATLASV/SEC"
ENG_1=(0,0,-5.5)
ENG_DIAMETER=1
IGNITE_DELAY=10
PITCHTHRUST=8645.9
YAWTHRUST=8645.9
ROLLTHRUST=160

[FAIRING]
N=2
MeshName="ATLASV/AV400FAIR"
EMPTYMASS=2255
Diameter=4
Height=12
angle=0.
off=(1.005,0.0,32.)

[PAYLOAD_1]
;off=(0,0,27.5)
;speed=(0,0,0)
;rot_speed=(0,0,0)
;MeshName=""
;Module=""
;name=""
;Diameter=
;Height=
;Mass=

her it is the "virgin" .INI file that comes with Atlas V package.
when i modified it i put:
[PAYLOAD_1]
;off=(0,0,27.5)
;speed=(0,0,0)
;rot_speed=(0,0,0)
;MeshName="carina"
;Module=""
;name="carina"
;Diameter=
;Height=
;Mass=5000
for sure it is wrong...but dunno where

DaveS · Jun 7, 2008

You need to remove the semi-colons(

from each line. This tells Orbiter that it's a comment and should be ignored.

Matte · Jun 7, 2008

oh God...
i hadn't notice it...thanks again to everyone for support to an half-minded guy :lol: :lol: :lol:

Edit: but keeps up crashing :rofl:

HTML:

[MISC]
cog=5

[STAGE_1]
Height=32
Diameter=4
EmptyMass=20743
FuelMass=284089
Thrust=4153416.7 
BurnTime=253
off=(0.,0.,0.)
MeshName="ATLASV/400CCB"
ENG_1=(.757,0,-20)
ENG_2=(-.757,0,-20)
ENG_DIAMETER=2
speed=(0.,0.,-5.)
PITCHTHRUST=361994.1
YAWTHRUST=361994.1
ROLLTHRUST=361994.1

[STAGE_2]
Height=13
Diameter=3
EmptyMass=1914
FuelMass=20830
Thrust=147000
BurnTime=842
off=(0.0,-.25,22.2)
MeshName="ATLASV/SEC"
ENG_1=(0,0,-5.5)
ENG_DIAMETER=1
IGNITE_DELAY=10
PITCHTHRUST=8645.9
YAWTHRUST=8645.9
ROLLTHRUST=160

[FAIRING]
N=2
MeshName="ATLASV/AV400FAIR"
EMPTYMASS=2255
Diameter=4
Height=12
angle=0.
off=(1.005,0.0,32.)

[PAYLOAD_1]
off=(0,0,27.5)
speed=(0,0,0)
rot_speed=(0,0,0)
MeshName="carina"
Module="Multistage"
name="carina"
Diameter=
Height=
Mass=5000

clive bradbury · Jun 8, 2008

It's not just you - I have tried the Atlas time and time again without success - the 'empty' launcher is fine, but as soon as you add a payload it will crash more often than not. This is a shame, as it is a good looking add-on. Do like me and use the titan instead, which also has a launch AP.

Jrquinlisk · Jun 16, 2008

Hmm... I don't think you can stack Multistage vessels like that. Try changing the PAYLOAD_1 section from

Code:

Module="Multistage"

to

Code:

Module="Carina"

and see how that works.

to be · Jun 16, 2008

Perhaps an improvement to attaching, stacking, and docking should be considered for the next orbiter release. It is currently extremely cumbersome, and easy to make a mistake manually editing text based scenario and config files. This would be a major improvement to the scenario editor, and perhaps more important then minor physics tweaking, which is already extremely accurate.

Dr Pepper · Jun 16, 2008

Hi Matte. A very likely problem with your Carina payload is the fact that where you are telling Multistage/Orbiter to look for the Module. You are telling it to look under the base config directory, but the Carina module is under the Config/vessels directory. So, to fix it, add this:

Code:

Module="Vessels/Carina"

Remember, if a file you are trying to call is not in the base directory of that file type (Orbiter/config, Orbiter/Meshes, ect), you have to add the pathway to it from that base directory (Orbiter/config/vessels, Orbiter/Meshes/spacecraft, ect), which looks like this in the multistage .ini file:

Code:

Module="Vessels/Carina"
;or
Mesh="Spacecraft/doll1"

mbartley · Jun 24, 2008

I've flown the Atlas V a lot, though I haven't messed with it much lately, and I can find only a couple of the .ini files I've edited. Here's a simple one that I think is exactly what you're trying to do, and I know it works for me.

I'll only include the last PAYLOAD_1 section.

Code:

[PAYLOAD_1]
off=(0,0,28)
speed=(0,0,0.5)
rot_speed=(0,0,0)
MeshName="Carina"
Module="Carina"
name="Carina"
Diameter=5
Height=5
Mass=5000

The Module= line just says Carina rather than Multistage. You didn't have Diameter= and Height=. Maybe those have to be defined, though I don't know what effect they have anyway.

You don't need to say Module=Vessels\Carina, just Module=Carina. The Config\Vessels directory is one of the directories that is searched by default, and I believe it's been that way since Orbiter 2006.

One other off-topic thing. In your .ini file it looks like the 2nd stage has way too much power. It's Thrust value is 147000; mine is 99200. BurnTime, FuelMass, and EmptyMass are the same. Mine over-performs quite a bit as it is. The Atlas V 401 is supposed to be able to launch a 5000 kg payload (like our simple Carina) into a geostationary transfer orbit. My configuration can not only do that, it can almost take it all the way into geostationary orbit. Yours probably can send it to Jupiter.

I've tried tweaking performance numbers a bit (I changed the Thrust value to match what's shown on Astronautix), though I didn't do a thorough job and I definitely didn't work on all of the many Atlas V variations.

Jrquinlisk · Jun 24, 2008

Mine over-performs quite a bit as it is.

I think part of the problem is that Astronautix.com doesn't factor in the throttle-down towards the end of the first stage burn. I crunched some numbers, and I came up with an actual burn time for the first stage of 227 seconds. That might help you get more accurate results.

Dr Pepper · Jun 24, 2008

mbartley said:
You don't need to say Module=VesselsCarina, just Module=Carina. The ConfigVessels directory is one of the directories that is searched by default, and I believe it's been that way since Orbiter 2006.

Not on mine (and I didn't edit the Orbiter.cfg file, either, nor did any of the add-ons I downloaded). Odd.

Orbiter 2024 has been released!

Problems with Atlas V

Member

Addon Developer

Member

Addon Developer

Member

Member

Addon Developer

Ker-splash!

Member

Ker-splash!

Member

Addon Developer

Member

Tutorial Publisher

New member

Member

Soft Drink

Member

New member

Soft Drink

Similar threads