Problem Spacecraft 3 Jettison problem

[JackJL]

Hi there, I'm new to the forum, but I've just released two addons over at orbit hangar. What I'm trying to do now is make a spacecraft 3 carrier for these, so that several of them fit in an XR5 payload slot.

I've made the various files required and the ship works fine in orbiter. However when I attempt to jettison a payload, it CTD's. EXCEPT when the scenario is loaded with only 1 or 2 (of 4) payloads. It jettisons just fine then.

This has baffled me greatly and I can see no reason for it in the ini file, detailed below. Any comments you have on this would be greatly appreciated.

[CONFIG]
MESHNAME="STISConnectorBus"
VISIBLE=1
SIZE=6
EMPTY_MASS=1000


[PAYLOAD_0]
MESHNAME=..\config\dgivpayload\meshes\DGIVCargoSTISconnector
NAME=STIS Connector 1
OFF=(0,0.62,-1.46)
MASS=1550
MODULE=DGIVCargoSTISconnector
SPEED=(0,1,0)
ROT_SPEED=(0,0,0)

[PAYLOAD_1]
MESHNAME=..\config\dgivpayload\meshes\DGIVCargoSTISconnector
NAME=STIS Connector 2
OFF=(0,0.62,1.46)
MASS=1550
MODULE=DGIVCargoSTISconnector
SPEED=(0,1,0)
ROT_SPEED=(0,0,0)

[PAYLOAD_2]
MESHNAME=..\config\dgivpayload\meshes\DGIVCargoSTISconnector
NAME=STIS Connector 3
OFF=(0,-0.62,1.46)
MASS=1550
MODULE=DGIVCargoSTISconnector
SPEED=(0,1,0)
ROT_SPEED=(0,0,0)

[PAYLOAD_3]
MESHNAME=..\config\dgivpayload\meshes\DGIVCargoSTISconnector
NAME=STIS Connector 4
OFF=(0,-0.62,-1.46)
MASS=1550
MODULE=DGIVCargoSTISconnector
SPEED=(0,1,0)
ROT_SPEED=(0,0,0)

 

[MJR]

What is the Orbiter log saying? It could be a syntax error in your configuration file.

 

[JackJL]

The log shows the planets etc. loading and then

Finished initialising world
Module Spacecraft3.dll [API v.050206]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh

This doesn't say orbiter needs to close see orbiter.log etc. but just a windows this program needs to close send error report etc.

I've been playing around with the config file trying to get it into the XR5 bay so it's a bit messy:

; === Configuration file for STIS Connector Bus===


ClassName = STISconnectorbus
module = spacecraft3
;MeshName = STISconnectorbus
Size = 6.00
Mass = 1000; empty mass [kg]

; === Docking ports ===
BEGIN_DOCKLIST
0.0 0.0 1.41 0 0 1 0 1 0
0.0 0.0 -1.4 0 0 -1 1 0 0
1.51 -.04 0 1 0 0 0 1 0
-1.51 -.04 0 -1 0 0 0 1 0
END_DOCKLIST
;----------------------------------------------------
; XR Payload custom parameters
;----------------------------------------------------
; REQUIRED: must be set to 'true' for this vessel to be dockable in an XR-class payload bay.
;XRPayloadEnabled = true
; cosmetic description; 127 chars MAX., but 40 chars or less recommended
;Description = Bus for STIS connectors
; Dimensions in meters: X (width) Y (height) Z(length). This also determines how many standard payload slots are occupied.
;Dimensions = 2.22 2.52 6.00
; attachment point index (0-n) that should be used for grappling in the bay; default=0
;AttachmentPointIndex = 0
; (OPTIONAL) maximum quantity of MAIN FUEL this payload can hold
;PropellantResource1 = 0
; (OPTIONAL) maximum quantity of SCRAM FUEL this payload can hold
;PropellantResource2 = 0
; (OPTIONAL) maximum quantity of LOX this payload can hold
;PropellantResource3 = 0
; (OPTIONAL) Offset in meters from the center of the primary payload slot to the center of this payload's mass (X,Y,Z).
; If this is not set, the default is [0 0 0]. These coordinates are necessary so that the collision detection code can know the
; origin point (the "centerpoint") of the payload mass in order to determine how many slots this payload module will occupy.
; If you adjust your attachment point coordinates to center this module in its primary payload slot, these coordinates
; should be [0 0 0] (the default). If your payload is attached off-center in the slot along any axis, as will be the case
; if your payload occupies more than one slot, you will need to adjust these coordinates accordingly.
; For example, if your payload's center-of-mass is 0.3 meter below the centerpoint of its primary slot, this
; value should be 0 -0.3 0. As another example, if your payload is two slots long, one slot wide, and one slot high,
; this value should be set to 0 0 -3.048: the reason is that the center-of-mass of a 40-foot-long container is 3.048 meters
; (1/2 slot) AFT of the ceterpoint of the primary slot (the forward of the two slots it occupies).
;PrimarySlotCenterOfMassOffset = 0 0 0
; (OPTIONAL) If this is not specified, a default thumbnail is used.
; Path relative to Orbiter config directory (e.g., "C:\Orbiter\Config") to the bitmap thumbnail image for this payload.
; This is displayed on the payload panel when this cargo is selected.
; This should point to a 24-bit-color bitmap that is 154x77 pixels in size.
; NOTE: do not use pure white (255,255,255) in your custom thumbnail bitmaps because that color is rendered
; as transparent when a bitmap is rendered on the panel.
;ThumbnailPath = /dgIVpayload/images/DGIVCargospaceloo.bmp
; (OPTIONAL): List of Orbiter vessel classnames for which an 'ExplicitAttachmentSlots' property is defined.
;VesselsWithExplicitAttachmentSlotsDefined = XR2Ravenstar
; (OPTIONAL): These are optional parameters that only need to be defined for a given ship class if you have a
; large or specially-shaped payload. If no explicit attachment slots are defined, the ship will compute
; which slots are valid for this payload based on its dimensions and the location of its attachment point.
; If explicit attachment points *are* defined here they will override any calculations made by
; the ship as to whether this object will fit in the bay when attached to a given slot. However,
; they do *not* override checks as to whether this object will fit alongside *other payload* in the
; cargo bay. Most payload objects will not need to define this value.
;
; Format is: <parent vessel classname>_ExplicitAttachmentSlots = # # # ...
;XR2Ravenstar_ExplicitAttachmentSlots = 3
; (OPTIONAL) Defines a delta to be applied to this vessel when it is deployed on the ground. This is useful
; when the payload vessel defines touchdown points that are belxow the ground when the vessel is deployed.
; For example, '0.0 2.0 0.0' would deploy the vessel to 2.0 meters *higher* than normal when this payload
; is deployed while landed.
;GroundDeploymentAdjustment = 0 0 0
;----------------------------------------------------
; === Attachment specs ===
; NOTE: a payload object's attachment point should be set for the CENTER of the bay slot into which it is
; attached. Each standard slot is exactly 2.4384 wide (X), 2.5908 high (Y), 6.096 long (Z). Some XR-class
; ships, such as the XR5 Vanguard, have some slots that are wider as well.
; WARNING: attachment *direction* must be (0 1 0) and attachment *rotation* must be (0 0 1)! The bay
; collision detection code expects this.
; Note: only *one* BEGIN_ATTACHMENT/END_ATTACHMENT block may be present in any vessel's .cfg file.
; If you have multiple attachment points, you must declare them all in a single block.
; === Attachment specs ===
;BEGIN_ATTACHMENT
;P 0.0 0.38 -0.72 0 1 0 0 0 1 XRCARGO
;END_ATTACHMENT


XRPayloadEnabled = true

Description = Dragonfly
 
Dimensions = 7.2 5.6 14.8

AttachmentPointIndex = 2

PrimarySlotCenterOfMassOffset = 0 2.8 -2.4

ThumbnailPath = Vessels\Dragonfly_XR5_Thumbnail.bmp

;VesselsWithExplicitAttachmentSlotsDefined = XR5Vanguard

;XR5Vanguard_ExplicitAttachmentSlots = 3
;----------------------------------------------------

BEGIN_ATTACHMENT
P 0 -2.8 2.4  0 1 0  0 0 1  XRCARGO
END_ATTACHMENT

 

[liber]

Mesh is missing,check in configuration file mesh path...put mesh in mesh folder.

 

[JackJL]

Thanks for the advice, but

The mesh of the bus is correctly named as STISConnectorBus.msh in the meshes folder. I do not believe this is the problem as with only 1 or 2 payloads (of 4) the crash does not occur and the deployed vessels are the correct module, mesh etc. The payload definitions are identical (except the offset and name).

 

[liber]

Don't know,pass here a scenario files...

 

[JackJL]

I've taken this straight from vinka's examples, and i've been tweeking it since i've changed it - hence the CURRENT_PAYLOAD 1 (it works for 2 and 3, not 0)

BEGIN_DESC
The Russian Dolls in orbit
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51982.9587552315
END_ENVIRONMENT

BEGIN_FOCUS
  Ship STISConnectorBus
END_FOCUS

BEGIN_CAMERA
  TARGET STISConnectorBus
  MODE Extern
  POS 2.89 -48.26 -36.70
  TRACKMODE TargetRelative
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
END_HUD

BEGIN_MFD Left
  TYPE Orbit
  PROJ Ship
  REF Earth
END_MFD

BEGIN_MFD Right
  TYPE Surface
END_MFD

BEGIN_SHIPS
STISConnectorBus:Spacecraft\Spacecraft3
  STATUS Orbiting Earth
  RPOS 6059127.95 1536951.30 -2166151.23
  RVEL 2426.320 772.252 7311.284
  AROT 5.79 -19.17 74.65
  CONFIGURATION 1
  CURRENT_PAYLOAD 1
END
END_SHIPS

 

[garyw]

What is the name of the CFG file you are using and where is it located?

 

[JackJL]

The config of the bus is in the config/vessels folder named STISconnectorbus.cfg

the config of the payload is in config/vessles folder called DGIVCargoSTISconnector.cfg

 

[liber]

Spacecraft use diferent configuration...
Here is your scenario and how should be configure to work:

 

[JackJL]

Thanks for the all the bits liber!

I've got the connector on it's own working as just a cfg type vessel, what I was trying to do was use the bus to jettison these. In your ini file no payloads are defined. Could you explain what changes you meant to show please, I'm at a bit of a loss

 

[liber]

In STISConnectorBus.ini file locate in Config\spacecraft you need there to add docking point.
Check spacecraft pdf how to add docking paramater...or examin spacecraft based add.on with docking capeable ships.

 

[JackJL]

I hadn't thought of that. I was trying to do this using the spacecraft payload system, so that the payloads wouldn't exist as ships when the bus was in the payload bay of an XR5. I'm not sure if the XR5 allows this, but I'll try it, it seems a bit simpler!

---------- Post added at 23:45 ---------- Previous post was at 23:32 ----------

It doesn't look like this will work as the attachment caused by payload system in the XR5 overrides the docking of a vessel. This affects it if the payload is docked before or after it is loaded in the XR5.

 

[liber]

STISConnectorBus.ini

[CONFIG]
MESHNAME="DGIVCargoSTISconnector\DGIVCargoSTISconnector"
SIZE=3
EMPTY_MASS=1000
FUEL_MASS=0

[DOCK_0]
POS=(0,0,1.3953)
DIR=(0,0,1)
ROT=(0,1,0)

[DOCK_1]
POS=(0,0,-1.3953)
DIR=(0,0,-1)
ROT=(0,1,0)

[DOCK_2]
POS=(1.4845,0,0)
DIR=(1,0,0)
ROT=(0,1,0)

[DOCK_3]
POS=(-1.4845,0,0)
DIR=(-1,0,0)
ROT=(0,1,0)

4 DG docked.scn

BEGIN_DESC
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 51982.9614706945
END_ENVIRONMENT

BEGIN_FOCUS
Ship STISConnectorBus
END_FOCUS

BEGIN_CAMERA
TARGET STISConnectorBus
MODE Extern
POS 17.50 -133.95 -37.71
TRACKMODE TargetRelative
FOV 50.00
END_CAMERA

BEGIN_HUD
TYPE Orbit
REF AUTO
END_HUD

BEGIN_MFD Left
TYPE Orbit
PROJ Ship
FRAME Ecliptic
REF Earth
END_MFD

BEGIN_MFD Right
TYPE Surface
SPDMODE 1
END_MFD

BEGIN_SHIPS
STISConnectorBus:Spacecraft\Spacecraft3
STATUS Orbiting Earth
RPOS 6393141.07 1658000.58 -390848.50
RVEL 403.248 253.181 7726.636
AROT 6.31 -20.93 74.47
VROT 0.34 0.00 0.00
DOCKINFO 0:0,01 1:0,02 2:0,03 3:0,04
NAVFREQ 0 0
RCS 1
CTRL_SURFACE 1
CONFIGURATION 1
CURRENT_PAYLOAD 1
END
01eltaglider
STATUS Orbiting Earth
RPOS 6393145.61 1658001.86 -390838.03
RVEL 403.248 253.181 7726.636
AROT -173.69 20.93 105.53
VROT -0.34 0.00 0.00
PRPLEVEL 0:1.000 1:1.000
THLEVEL 4:0.009 5:0.009
DOCKINFO 0:0,STISConnectorBus
NAVFREQ 0 0 0 0
XPDR 0
NOSECONE 1 1.0000
END
02eltaglider
STATUS Orbiting Earth
RPOS 6393137.41 1657999.51 -390859.33
RVEL 403.248 253.181 7726.636
AROT 6.31 -20.93 74.47
VROT 0.34 0.00 0.00
PRPLEVEL 0:1.000 1:1.000
DOCKINFO 0:1,STISConnectorBus
NAVFREQ 0 0 0 0
XPDR 0
NOSECONE 1 1.0000
END
03eltaglider
STATUS Orbiting Earth
RPOS 6393144.40 1657989.50 -390848.56
RVEL 403.248 253.181 7726.636
AROT 90.64 14.48 68.35
VROT 0.00 0.00 -0.34
PRPLEVEL 0:1.000 1:1.000
DOCKINFO 0:2,STISConnectorBus
NAVFREQ 0 0 0 0
XPDR 0
NOSECONE 1 1.0000
END
04eltaglider
STATUS Orbiting Earth
RPOS 6393138.62 1658011.88 -390848.81
RVEL 403.248 253.181 7726.636
AROT -89.36 -14.48 111.65
VROT 0.00 0.00 0.34
PRPLEVEL 0:1.000 1:1.000
DOCKINFO 0:3,STISConnectorBus
NAVFREQ 0 0 0 0
XPDR 0
NOSECONE 1 1.0000
END
END_SHIPS

BEGIN_ExtMFD
END

---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------

It doesn't look like this will work as the attachment caused by payload system in the XR5 overrides the docking of a vessel. This affects it if the payload is docked before or after it is loaded in the XR5.

Don't know...

 

[JackJL]

I think we are trying to do 2 different things, I have already made the [ame="http://www.orbithangar.com/searchid.php?ID=3984"]connector [/ame]which has the docking ports . The thing I'm trying to make now is a carrier vessel to hold 4 of these connectors in 1 payload slot of an XR5. I was trying to make this carrier from spacecraft3, with the connectors as simple .cfg vessels.

Sorry for the confusion, I hope this clears up what I'm trying to do
[ame="http://www.orbithangar.com/searchid.php?ID=3984"] [/ame]

 

[liber]

I think we are trying to do 2 different things, I have already made the connector which has the docking ports . The thing I'm trying to make now is a carrier vessel to hold 4 of these connectors in 1 payload slot of an XR5. I was trying to make this carrier from spacecraft3, with the connectors as simple .cfg vessels.

Sorry for the confusion, I hope this clears up what I'm trying to do

I think that is impossible to do...paylod carring a payload in XR5 payload bay...

 

[JackJL]

The XR payload system simply attaches a vessel to the XR5. The spacecraft 3 payload system only creates the vessel when it it jettisoned. So either before or after jettisoning only the spacecraft3 carrier is attached to the XR5 and is not attached to anything else.

That's how I see how it works anyway, I can't see where any conflict would come from with this

 

[liber]

Maybe you looking for this...
STISConnectorBus is attached to XR-5 and DeltaGlider is dock to STISConnectorBus...

 

[n122vu]

I think what you are trying to accomplish has already been done, using the following addons in tandem.

Universal Cargo Deck
[ame="http://www.orbithangar.com/searchid.php?ID=3262"]Universal Cargo Deck, release 4[/ame]

Universal Cargo Deck Carrier for the XR-5
[ame="http://www.orbithangar.com/searchid.php?ID=3312"]Universal Cargo Deck carrier for the XR5[/ame]

I think you could use the UCDC to position your 4 vessels (or anything else for that matter) any way you wanted in the payload bay, and set the jettison speed, etc. Also, the UCDC allows the mass of the ships/payload to be added to the vessel.

Just a thought.

 

[Donamy]

This may help

[ame="http://www.orbithangar.com/searchid.php?ID=2890"]Resolve[/ame]