Software Missing Vessel.cpp

[Freedom 7]

When I was trying to start the Thor scenarios, it says I'm missing vessel.cpp. Here's what orbiter.log said...




**** Orbiter.log
Build Jun 6 2010 [v.100606]
Timer precision: 3.77525e-007 sec
Found 2 joystick(s)
Devices enumerated: 3
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
Module AtlantisConfig.dll .... [Build 100606, API 100606]
Module AtmConfig.dll ......... [Build 100606, API 100606]
Module DGConfigurator.dll .... [Build 100606, API 100606]
Module transx.dll ............ [Build 100528, API 100527]
Module TrackIR.dll ........... [Build 091120, API 091120]
TrackIR module not found.
Module ScriptMFD.dll ......... [Build 100606, API 100606]
Module ScnEditor.dll ......... [Build 100606, API 100606]
Module Rcontrol.dll .......... [Build 100606, API 100606]
Module Meshdebug.dll ......... [Build 100606, API 100606]
Module LuaMFD.dll ............ [Build 100606, API 100606]
Module LuaConsole.dll ........ [Build 100606, API 100606]
Module Framerate.dll ......... [Build 100606, API 100606]
Module FlightData.dll ........ [Build 100606, API 100606]
Module ExtMFD.dll ............ [Build 100606, API 100606]
Module CustomMFD.dll ......... [Build 100606, API 100606]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1594 x 1172 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Loading 8816 records from star database
Joystick throttle: SLIDER 0
Joystick throttle control detected
Module Sun.dll ............... [Build 100215, API 100212]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100215, API 100212]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100215, API 100212]
Module VenusAtm2006.dll ...... [Build 100606, API 100606]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100215, API 100212]
Module EarthAtmJ71G.dll ...... [Build 100606, API 100606]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100217, API 100215]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100215, API 100212]
Module MarsAtm2006.dll ....... [Build 100606, API 100606]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100215, API 100212]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100215, API 100212]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100215, API 100212]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100215, API 100212]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
>>> ERROR: No vessel class configuration file found for:
---------------------------------------------------------------
>>> ERROR: Multistage\Multistage
>>> [Vessel::OpenConfigFile | .\Vessel.cpp | 252]
---------------------------------------------------------------
>>> TERMINATING <<<

I do have multistage installed correctly.

 

[Lucy]

This doesn't mean you're missing vessel.cpp - rather the opposite, it's telling you that the error is in something vessel.cpp was asked to do by the scenario file, in this case initialise a multistage vessel.

Though I haven't used it, the replacement for the multistage.dll which wasn't quite compatible with Orbiter 2010 was here. Try this first.

 

[Freedom 7]

Still not working...

It is still not working.

 

[Lucy]

Okay. Can I see the contents of the scenario file causing this problem?

Preferably wrap it between

 tags to save space. My screen is old and tired.

 

[Freedom 7]

http://www.flickr.com/photos/beautyofaviation/5122472450/

That's the image of the contents of Scenarios.

 

[Lucy]

No, that wasn't what I asked for. I want the contents of the scenario file you're running which is giving you this problem.

 

[Freedom 7]

I don't know what you mean.

 

[orb]

I don't know what you mean.

In the Scenarios folder, which screenshot you have posted, find a scenario that is causing your problem. Then right click on it and choose "Open with...", and select Notepad and open that file with it. Next, you need to select all the contents of the file (CTRL+A for example), and copy them (for example CTRL+V, or CTRL+Insert, or with mouse). And then paste them between [code][/code] tags to a new post on this thread.

 

[Artlav]

The Thor scenario you're trying to run.
What is inside it? It's a text file.
The error seems to suggest that Multistage can't find the vessel ini file, but which file it is is said inside the scn file.

 

[Lucy]

Yes, what they said.

Let's go over the basics. Scenarios are not magical wonderful mysteries, they are all small text files which tell Orbiter what to do - what vessels to load, what solar system to use, what date to set, et cetera. They're all in folders within Scenarios as you've seen.

Those folders are also in your Launchpad's "Scenario" display - so, when you click to open the "Thor" folder or whatever it is, and select a scenario from that folder, you're telling Orbiter to load up that scenario - that file is a text file inside the Scenarios folder. See the screenshot (Click it to make it big enough to see).



To work out what your problem is, I was trying to find out what Artlav suggested, how is the scenario file telling Orbiter to define the vessel which is causing your crash? Obviously something is wrong there.

 

[n72.75]

Please post the scenario file.

and put it in "

" tags like this:


[CODE]Code
Code
Code
Code

 

[Freedom 7]

  [/code[COLOR="Red"]

[SIZE=1]---------- Post added at 01:05 AM ---------- Previous post was at 01:04 AM ----------[/SIZE]

[/COLOR][code BEGIN_DESC
Launch Echo1 from Kennedy Space Center.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 38602.6701443519
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Echo
END_FOCUS

BEGIN_CAMERA
  Target Echo
  MODE Extern
  POS 2.84 0.00 -99.07
  TRACKMODE TargetRelative
  FOV 60#
END_CAMERA

BEGIN_HUD
  Type Surface
END_HUD

BEGIN_MFD Left
  Type Surface
END_MFD

BEGIN_MFD Right
  Type Orbit
END_MFD
BEGIN_STATIONS
END_STATIONS

BEGIN_SHIPS
echo1:Multistage\Multistage
  STATUS Landed Earth
  BASE Cape Canaveral:14
  HEADING 135.00
  FUEL 1.000
  CONFIG_FILE Config\multistage\echo1.ini
;  GUIDANCE_FILE Config\thor\guidancetelstar.txt
  CONFIGURATION 0
  CURRENT_BOOSTER 1
  CURRENT_STAGE 1
  CURRENT_PAYLOAD 1
  FAIRING 1
END
END_SHIPS

---------- Post added at 01:06 AM ---------- Previous post was at 01:05 AM ----------

All other Thor scenarios are doing it too.

 

[BABYnecro]

CFG problems

I've found that in order to get a vessel to appear (such as the LAAT or Skyhopper from star wars that are posted on Orbithangar) I've had to move the .ini file from the Spacecraft folder of the Config Section to the Vessels folder. Then I had to change the name of the vessel call in the Scenario File to just the name of the file.

For example:

In Spacecraft folder:
laat.ini ---> LAAT.cfg (also moved to the Vessels folder)

In .scn:
ORIGINAL:
BEGIN_SHIPS
laat:Spacecraft\Spacecraft3
STATUS Landed Earth

NEW:
BEGIN_SHIPS
LAAT
STATUS Landed Earth





Unfortunately it seems that this removes some function from the vessels such as thrust and commands and such

 

[Izack]

That's because spacecraft3 INIs do not follow the same format as Orbiter CFGs. Frankly, I'm surprised that method works at all. :blink:

Usually, this error in Orbiter.log means that the INI file specified in the scenario does not exist in the directory it is supposed to be in (Config\Spacecraft.) Is the vessel the scenario needs installed? Did you alter the installation path at all? Check the zip file the addon came in. Is it unzipping in the right place? Which addon is it, anyway? I'd like to check myself.