Advanced Question how to add spacecraft3-vessels to scenario?

[HAL9001]

How can I add spacecraft-3-vessels to the scenario?
I can't add them with the scenario-editor.

greets, hal9001

 

[Izack]

You need to add a cfg file to the Vessels folder.

You would create a file called <your vessel name without spaces>.cfg, which would look like this:

ClassName = <same as filename>
Module = Spacecraft3

When you spawn it with the scenario editor, the vessel name you enter MUST be the same as the file/class name (what you see in the vessel list.)

So for the James Cook, it would be JamesCook.cfg, reading:

ClassName = JamesCook
Module = Spacecraft3

and you would name the vessel JamesCook.

You can choose other names/add more of the same vessel to a scenario by creating other CFG files and INI files in the Config\Spacecraft folder with the same contents, only with different file and class names.

So you could copy JamesCook.ini, paste it in the same directory, rename it BotanyBay.ini, then create a new config file under Config\Vessels called BotanyBay.cfg, with ClassName = BotanyBay, add both with the scenario editor and voila! you have two of the same ship. :thumbup:

 

[gattispilot]

So I am trying to get this to work. So in the config/vessel folder I have a cfg named:
BARM1.cfg

and in it is:

; === Configuration file for spacecraft3 ===
ClassName = BArm1
Module = Spacecraft3

BArm1 is the name of .ini in the spacecraft folder.

When I load it in SCN editor no mesh shows up?

 

[Trekkie]

So I am trying to get this to work. So in the config/vessel folder I have a cfg named:
BARM1.cfg

and in it is:

; === Configuration file for spacecraft3 ===
ClassName = BArm1
Module = Spacecraft3

BArm1 is the name of .ini in the spacecraft folder.

When I load it in SCN editor no mesh shows up?

Check if the mesh file is the Same as in the ini file and try to keep the ini and the vessel named the same

 

[gattispilot]

Thanks. So when you add the vessel the name must be the same as the cfg.

BArm1:BArm1
  STATUS Orbiting Earth
  RPOS 6995440.87 0.00 421220.53
  RVEL -453.291 -0.000 7528.050
  AROT 0.00 0.00 0.00
  AFCMODE 7
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.500000
  SEQ 2 -2 0.500000
  SEQ 3 -2 0.500000
  SEQ 4 -2 0.500000
  SEQ 5 -2 0.500000
  SEQ 6 -2 0.500000
  SEQ 7 -2 0.500000
  SEQ 8 -2 0.125000
END

 

[DaveS]

Thanks. So when you add the vessel the name must be the same as the cfg.

BArm1:BArm1
  STATUS Orbiting Earth
  RPOS 6995440.87 0.00 421220.53
  RVEL -453.291 -0.000 7528.050
  AROT 0.00 0.00 0.00
  AFCMODE 7
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.500000
  SEQ 2 -2 0.500000
  SEQ 3 -2 0.500000
  SEQ 4 -2 0.500000
  SEQ 5 -2 0.500000
  SEQ 6 -2 0.500000
  SEQ 7 -2 0.500000
  SEQ 8 -2 0.125000
END

Not the cfg file but the INI file. The vessel name tells SC3 which INI file to load. So a vessel with the name of "801bc" tells SC3 to load the INI file named "801bc.INI" in the Config\Spacecraft folder.

 

[gattispilot]

Ok So make sure .ini and .cfg are the same names. It looks like the Vessel names needs to be the same also.

 

[Trekkie]

Ok So make sure .ini and .cfg are the same names. It looks like the Vessel names needs to be the same also.

Correct, so if you would have for instance an ini file named Enterprise then the vessel in game has to have the Same name in order for it to load( i also always have the ini and .cfg the Same names just to be sure)