Scav
Mostly Harmless
- Joined
- May 8, 2010
- Messages
- 1,002
- Reaction score
- 38
- Points
- 48
Absolutely! Matter of fact, I can post the code right here when I'm done. :thumbup:
---------------------------------------------------------------------
Here it is! Quick and dirty, but it spawns the mesh in a workable place in the cargo bay. Only, I'm working on debugging some more; it gives a mesh without the functionality I'm looking for. Amongst the complaints at the moment, are that the vessel has no propulsion or animation once released from the bay. My uneducated thought is, this might have to be DLL'ed for it to work splendidly.
Oh well. At least this gives you a placement for the sat, right? :tiphat:
---------------------------------------------------------------------
Here it is! Quick and dirty, but it spawns the mesh in a workable place in the cargo bay. Only, I'm working on debugging some more; it gives a mesh without the functionality I'm looking for. Amongst the complaints at the moment, are that the vessel has no propulsion or animation once released from the bay. My uneducated thought is, this might have to be DLL'ed for it to work splendidly.
Oh well. At least this gives you a placement for the sat, right? :tiphat:
Code:
; DSCS vessel class, configuration file for implementing in XR5's cargo bay.
Meshname = dscs
Mass = 2277
Size = 1.0
;----------------------------------------------------
; XR Payload custom parameters
;----------------------------------------------------
; 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 = Deep Space Comms Satellite (2,277kg)
; Dimensions in meters: X (width) Y (height) Z(length). This also determines how many standard payload slots are occupied.
Dimensions = 1.02 1.02 2.11
; (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): List of Orbiter vessel classnames for which an 'ExplicitAttachmentSlots' property is defined.
VesselsWithExplicitAttachmentSlotsDefined = XR5Vanguard
; (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 = # # # ...
XR5Vanguard_ExplicitAttachmentSlots = 1 3 5; Floor level only. This module takes up two slots.
;----------------------------------------------------
; === 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.
; Also note that the XR attachment point *must* be labeled XRCARGO.
BEGIN_ATTACHMENT
P 0 0 .5 0 1 0 0 0 1 XRCARGO
P 0 -0.725 -3.0 0 -1 0 0 0 1 XS
P 0 -0.725 -6.0 0 -1 0 0 0 1 XS
END_ATTACHMENT
Last edited:
That scenario works great, I'll include it in the next update if you don't mind. 
