Discussion Space Shuttle Vessel - Payload Development Thread

Ok. I was hoping just to attach it to the pdp to rms to check camera alignment.

What does it mean "Attached vessel does not match vessel in scenario data"
 
Ok. I was hoping just to attach it to the pdp to rms to check camera alignment.
The grapple fixtures of the PFTA should be to spec, you can check your dimensions against them.

What does it mean "Attached vessel does not match vessel in scenario data"
I means that the scenario parameters don't all match.
 
Ok. this is what I was testing.
the rms is attached the the PDP for sts 3. It looks like the camera target needs to move.


PDP:STS_Payloads\PDPSSV
STATUS Orbiting Earth
RPOS -3600958.328 -2018525.324 -4985414.229
RVEL 4917.6683 3659.3723 -4929.7028
AROT -164.788 55.408 172.997
VROT 0.0077 -0.0267 -0.0150
ATTACHED 1:0,Columbia
NAVFREQ 0 0
END

scn:
@SUBSYSTEM PORT_RMS
ANGLES -13.477284 53.579636 -99.407302 -56.505406 12.722999 -54.576593
SHOULDER_BRACE 0.0
GRAPPLE 0 0.0000
RIGIDIZE 0 0.0000
EXTEND 0 0.0000
ELBOW_CAM -90.000000 105.000000 40.000000
WRIST_CAM 40.000000
MPM_ROLLOUT 1.0
MPM_LATCHES 1.000000 1.000000 1.000000
ATTACHED_PAYLOAD PDP 1
@ENDSUBSYSTEM


oh so in the scn the payload needs to be added. Now the camera aligns
 

Attachments

  • sts3pdprms1.jpg
    sts3pdprms1.jpg
    62.4 KB · Views: 7
  • PDPRMS1.jpg
    PDPRMS1.jpg
    39.4 KB · Views: 7
Last edited:
any idea why am I either getting CTD or mission starts but can't see Shuttle anymore at all ?
it's just a blank space. and I've never seen this before. everything loads fine but shuttle
:confused:
and I believe I have everything installed.

============================ ERROR: ===========================
Could not load vessel module: SSV_OV
[Vessel::LoadModule | .\Vessel.cpp | 5747]
===============================================================
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
D3D9: ERROR: Base Object 0x2683F5C8 = 'Clavius Base' not cataloged
D3D9: ERROR: Base Object 0x268403E8 = 'Preary Base' not cataloged
D3D9: ERROR: Base Object 0x2775F178 = 'UCGO Base Europa' not cataloged
000000.000: D3D9: [Scene Initialized]
000000.000: oapi::Module::clbkSimulationStart
000000.000: [CRT]:DIMENSIONS: 1039 1039

000000.000: Finished initialising panels
D3D9: NewShader [MeshIdx-0]=4
D3D9: NewShader [SSV\OV\OV]=FFFF
000028.092: [CRT]:DIMENSIONS: 1039 1039

000029.093: [CRT]:DIMENSIONS: 1039 1039

000036.944: [CRT]:DIMENSIONS: 1039 1039

000065.135: [CRT]:DIMENSIONS: 1039 1039

000085.176: D3D9: [Session Closed. Scene deleted.]
000085.176: D3D9: [Destroy Render Window Called]
D3D9: ERROR: UnDeleted Surface(s) Detected
D3D9: ERROR: [Failed to Reset DirectX Device] (Likely blocked by undeleted resources)


============================ ERROR: ===========================
Parse error from base definition file for Cape Canaveral: Block: TEXn: expected 3 values (*char, scalar, scalar)
[BaseObject::ParseError | .\Baseobj.cpp | 184]
===============================================================
============================ ERROR: ===========================
Parse error from base definition file for Cape Canaveral: Block: TEXn: expected 3 values (*char, scalar, scalar)
[BaseObject::ParseError | .\Baseobj.cpp | 184]
===============================================================
000000.000: BaseObject: Parse error 2
 
any idea why am I either getting CTD or mission starts but can't see Shuttle anymore at all ?
it's just a blank space. and I've never seen this before. everything loads fine but shuttle
:confused:
and I believe I have everything installed.
Which versions of Orbiter and SSV are you using?
Do all SSV scenarios have this issue?
 
latest SSV I believe
and O2016
* Changes from SSV v1.11 *
replaced dead Flight Data File page link with archived version
small code cleanup and corrections....
that's from read me, so I guess it's the latest

couple just CTD, the rest don't show SS

btw, I'm a pretty much noob about this, sorry, so SSV is not the same as SSU (ultimate) right ?
those (SSU) scenarios don't crash, it seems
 
Yes.
Initially I was thinking the alignment might not be good enough, but actually that might not work at all. The IECM vessel is already attached via a "parent" attachment (only one parent is allowed). When the vessel is attached directly to the PLB via the active latches, there is a "handover" between them and the RMS, thus working around this limitation.
I'll have to figure something out for this situation... thanks for catching it! Meanwhile you'll have to release the IECM from the pallet and then grapple it with the RMS. 🤷‍♂️
I've been thinking about this and I think the best way would be to externalize all systems stuff, VC elements included. Currently, everything is internal to the main SSV DLL module, which I think unnecessarily complicates things as things much exist both internally and externally at the same time. Once upon a time there was an add-on developer, Radu094, that came up with what I have always thought to have been a brilliant solution to this problem. It was called the "System&Panel SDK" which allowed for complex systems and at time, 2D panels, to be developed outside DLLs, in regular cfg files.

Unfortunately, it fell by the way side and was all but forgotten about. But the problems presented in this thread finally lead me to dig up Radu094's old site from 2005 (20 years ago) and thanks to the Wayback Machine, it can found archived here, with all the links working: https://web.archive.org/web/20060215040008/http://217.10.196.198/Orbiter/main.html

Would something like this work for SSV?
 
I've been thinking about this and I think the best way would be to externalize all systems stuff, VC elements included. Currently, everything is internal to the main SSV DLL module, which I think unnecessarily complicates things as things much exist both internally and externally at the same time. Once upon a time there was an add-on developer, Radu094, that came up with what I have always thought to have been a brilliant solution to this problem. It was called the "System&Panel SDK" which allowed for complex systems and at time, 2D panels, to be developed outside DLLs, in regular cfg files.

Unfortunately, it fell by the way side and was all but forgotten about. But the problems presented in this thread finally lead me to dig up Radu094's old site from 2005 (20 years ago) and thanks to the Wayback Machine, it can found archived here, with all the links working: https://web.archive.org/web/20060215040008/http://217.10.196.198/Orbiter/main.html

Would something like this work for SSV?
The SPSDK is very interesting, and it is a shame it wasn't continued... maybe it could be integrated into GenericVessel or VesselBuilder or some other similar framework, to expand their capabilities.
For SSV, it would require many more features, and very likely it would not work as well as code, and for sure it would be slower. Also, not sure how it would handle different system configurations, interface with the DPS, etc... and in the end, I don't know what problem it would solve.

Back to the RMS issue, this SDK would not solve this issue. The Orbiter attachment logic does not contemplate more than one attachment "holding" a vessel (more than one parent). There is a workaround in SSV for the PRLA - RMS duo (which probably would not be possible with the SPSDK), but it won't work with the RMS and payload attached to something else, and it also won't work with another RMS and a payload in the PRLAs. It requires "cooperation" between the 2 parents holding (actually, trying to hold) the payload, and while that is trivial when the 2 parents are the same vessel, it is no so easy when there are 2 different parents.
 
So I am hoping some one can see what is wrong?
Launching of the LESAT Sat. Basically how I did for STS2016. It just add rotation and detach.

Ejection of the spacecraft from the Shuttle is initiated when locking pins at the four contact points are retracted. An explosive device then releases a spring that ejects the spacecraft in a "Frisbee" motion. This gives the satellite its separation velocity and gyroscopic stability during the 45-minute coast period between deployment and ignition of the perigee kick motor. The satellite separates from the Shuttle at a velocity of 1.6 feet per second and a spin rate of about two rpm.

if (spintable == 1) {
OBJHANDLE hChild3 = GetAttachmentStatus(sat_attach);
DetachChild(sat_attach, .2);
if (oapiIsVessel(hChild3)) {
VESSEL* vChild3 = oapiGetVesselInterface(hChild3);
VECTOR3 avel;
avel.data[1] = 0;
avel.data[0] = 0;
avel.data[2] = 12 * RAD;
vChild3->SetAngularVel(avel);
}
}
}

what happens is the SAT is launched but it should slowly rotate away
 

Attachments

  • ssvsts51a1.jpg
    ssvsts51a1.jpg
    74.6 KB · Views: 8
Could it be a pre-step vs post-step issue? Try moving that code to the other function (I don't know in which one you have it).
 
Do we have specs for the Pallet? this is for STS51A
 

Attachments

  • ssvpallet.jpg
    ssvpallet.jpg
    51 KB · Views: 3
Do we have specs for the Pallet? this is for STS51A
Search "Spacelab Payload Accommodation Handbook", and you'll find specs for the pallet and other parts of the SpaceLab system. The pallets were used as bases for other payloads, so those handbooks will only give info on the "basic pallet" without the extras that were mounted in them.
 
Thanks. Now just to figure where the trunnions fit
 

Attachments

  • PALLET1.jpg
    PALLET1.jpg
    53.7 KB · Views: 7
Confused
I am trying to place a vessel in bay 10. I attach it in the scenario. but when I load it it is orbiting around the sun?
BASE_attach = CreateAttachment(true, _V(0, -.010, -0.02), _V(0, -1, 0), _V(0, 0, 1), "MMUFSS1", true);
IMAX:STS_Payloads\STS41CAMERA
STATUS Landed Earth
ATTACHED 0:17,Challenger
END

then
IMAX:STS_Payloads\STS41CAMERA
IMAX 0 0.0000
STATUS Orbiting Sun
RPOS 2.011 0.686 695998656.028
RVEL -0.0504 -0.0582 -64.3740
AROT -107.501 86.210 -18.799
VROT 753.3893 781.4090 -1723.6708
NAVFREQ 0 0
END

not sure if attachment numbers are good.
 

Attachments

  • STS41CPAYLOAD.jpg
    STS41CPAYLOAD.jpg
    33.7 KB · Views: 3
I use the scn the mission editor creates. But i dont see the vessel. Going to play with it.
 
Back
Top