Project Space Shuttle Vessel

Snax

Space Cowboy
Joined
Jun 20, 2018
Messages
214
Reaction score
151
Points
58
Location
Brussels
Looking at this, if I input "1,2" instead of "1.2" (like I usually do), I get 12 (which is wrong) and no exception. That exception only shows up if I type 2 decimal points, e.g., "1.2.3". :unsure:
Switched the Windows settings to have the decimal symbol ",", and it seems to work as is ("1,2" is parsed correctly, and "1.2" gives 12)... so again, the exception seems to be related to something else.



In that situation where the exception occurs: what is in the Other Vessels, Scenario Parameters text box?
Could you please load mission STS-101, and then without changes, try to create a scenario? Does it throw the exception? Do the numbers on the ISS scenario block match what is in the Other Vessels tab?



(this made my head hurt more than the ADI o_O)
I'll ask my friend to try your recommendation.
I know he started from the default STS-101 template and just edited the mission name with STS-900. He didn't change the OTHER VESSEL parameters for the ISS or anything else).
 

amalahama

Member
Joined
Feb 13, 2008
Messages
40
Reaction score
5
Points
8
Hi @GLS ! Will the IDP/GCS revamp allows finally to have different GCSs in different status, having the voting system modeled, and the possibility to link each IDP to different GCSs or to none as in FG Shuttle?
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,925
Reaction score
2,934
Points
188
Website
github.com
Hi @GLS ! Will the IDP/GCS revamp allows finally to have different GCSs in different status, having the voting system modeled, and the possibility to link each IDP to different GCSs or to none as in FG Shuttle?
Hmm, GCS = GPC?
Anyway, the current work is focused on the data flow from the GPCs to the IDPs. This will drive the GPC, IDP and MDU (and HUD) implementations forward. How much forward is still open... I obviously want things to improve, but I have to "contain" the work, otherwise it will just continue, and continue....
I'm currently working the software in the GPC, to generate the signals which then get sent to the displays, as well as being used by GNC. Lots of new modules and variables, which move the "cheating" further back: instead of having a display call the Orbiter API directly for, e.g., the current velocity, that is now done a couple of modules before, and from there to the display everything is as it should be. This will make it easier to eventually introduce the N of GNC, as the "clients" will already have the correct interface.
In parallel, I'm doing some limited work in the IDP and MEDS displays, but I'm kind of lost due to the unknowns in the IDP<-->MDU communication. I know the IDPs did the edge key and menu processing for the MDUs, but the format of the display data, and how much of it was in the MDU is unknown, so this part is currently in the back burner.
The current GPC layout will remain, as there are still many inputs and outputs to correct (this is part of that) before "detaching" the GPCs from Orbiter, and eventually having all 5. I moved away from them with the work in the dedicated displays, but the CRT displays will be a bit different-looking, as by using the buses to send the data to the IDP, a full refresh should no longer possible (only x amount of data can be sent on each cycle), so it will update "this" part, then "that" part, etc., but in the interest of time, might cheat this a bit.
For the IDP<-->MDU links, it will probably advance enough to have autonomous MDUs if the IDP is powered off. This is because what is displayed on each MDU depends on where it is located (e.g., if the CDR changes the ADI mode on the left, the right ADI should remain as the PLT left it), so a more advanced relationship is needed. But again, lots of unknowns in that part of the world, so let's see what happens.
 

amalahama

Member
Joined
Feb 13, 2008
Messages
40
Reaction score
5
Points
8
Thanks for the profuse response GLS. Yeah I meant GPC sorry for the confusion. I can't wait until the day we have Orbiter-independent GPCs running autonomously in parallel processes! That sounds very exciting! Even if it's still going to take a while
 

Geoair2

Well-known member
Joined
Dec 13, 2022
Messages
52
Reaction score
121
Points
48
Location
Ploemel
I have a little problem with a scenario with this error message

(SSV_OV) [FATAL ERROR] Exception in clbkPreStep: [Payload_Latch_1] Attached vessel attachment ID is not compatible
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
8,726
Reaction score
2,690
Points
203
Location
Dallas, TX
I have a little problem with a scenario with this error message

(SSV_OV) [FATAL ERROR] Exception in clbkPreStep: [Payload_Latch_1] Attached vessel attachment ID is not compatible
Did you change the attachment ID ?
 

GLS

Well-known member
Orbiter Contributor
Addon Developer
Joined
Mar 22, 2008
Messages
5,925
Reaction score
2,934
Points
188
Website
github.com
I have a little problem with a scenario with this error message

(SSV_OV) [FATAL ERROR] Exception in clbkPreStep: [Payload_Latch_1] Attached vessel attachment ID is not compatible

Space Shuttle Vessel Manual said:
For compatibility, the attachment must have the id "XS".
.
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
8,726
Reaction score
2,690
Points
203
Location
Dallas, TX
; === Configuration file for vessel class Shuttle ===
ClassName = EURECA
Module = EURECA

RenderCockpit = TRUE

; === Attachment specs ===
BEGIN_ATTACHMENT
P 0 1 0.0 0 -1 0 0 0 -1 XS
P -1.561 1.67 0.465 -0.714216 0.692871 -0.0991215 0.43054, 0.546559, 0.718268 GF
END_ATTACHMENT


"5.2 RMS For the RMS to grapple a payload, it much have an attachment with the ID "GF". The attachment must be placed at the surface of the Grapple Fixture plate, centered in the cam/arm assembly. The attachment direction and rotation vectors for the RMS End Effector are shown in figure 31. "

GF for RMS Grapple
XS for payloads:
For compatibility, the attachment must have the id "XS". The attachment direction and rotation vectors for a keel-attached payload are shown in figure 25, and for longeron-attached payloads in figure 26.
 

Geoair2

Well-known member
Joined
Dec 13, 2022
Messages
52
Reaction score
121
Points
48
Location
Ploemel
It doesn't work as if something in the module was causing a problem 😢
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
8,726
Reaction score
2,690
Points
203
Location
Dallas, TX
I detached the Eureca. But I need this file:(SSV_ET) [ERROR] Can't open mission file STS-46
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
8,726
Reaction score
2,690
Points
203
Location
Dallas, TX
Change the scn to this:
EURECA:EURECA
ANT 0 0.0000
SPANEL 0 0.0000
HATCH 0 0.0000
STATUS Landed Earth
POS -80.6208722 28.6271110
HEADING 0.00
ALT 47.489
AROT 87.306 -52.872 6.926
ATTACHED 1:10,Atlantis
AFCMODE 7
PRPLEVEL 0:1.000000
NAVFREQ 0 0
XPDR 0
END
STS46CB:STS46CB
BOOM 0 0.0000
GAS 1 0.0000
CONCAP2 0 0.0000
GAS1 0 0.0000
GAS1 -1083982474 0.1496
TETHER 0.000000
PLB_CAM 0.0000 0.0000 0.0000 0.0000
STATUS Landed Earth
POS -80.6040953 28.6082743
HEADING 148.64
ALT 39.152
AROT 90.000 0.160 90.000
AFCMODE 7
NAVFREQ 0 0
XPDR 0
END
TSS:TSS1
ANT 0 0.0000
STATUS Landed Earth
POS 0.0000000 0.0000000
HEADING 0.00
ALT 1.985
AROT 90.000 0.000 90.000
ATTACHED 0:0,STS46CB
AFCMODE 7
NAVFREQ 0 0
XPDR 0
END

You will need to adjust the XS attachment though
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
8,726
Reaction score
2,690
Points
203
Location
Dallas, TX
Not sure.
Looks like missing a texture?
D3D9: WARNING: Texture STS_PAYLOADSNEW/SST46IMAGE1.dds not found.


(SSV_OV) [INFO] Can't find payload for latch Payload_Latch_1
000000.000: (SSV_OV) [INFO] In clbkPreStep
(SSV_OV) [FATAL ERROR] Exception in clbkPreStep: [Payload_Latch_1] Attached vessel attachment ID is not compatible

No ideas
 

Geoair2

Well-known member
Joined
Dec 13, 2022
Messages
52
Reaction score
121
Points
48
Location
Ploemel
Using Eureca in passive charging everything works but I cannot deploy it while in active charging it no longer works although this is the only way to deploy it.
Yet it works with Hubble. o_O
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
8,726
Reaction score
2,690
Points
203
Location
Dallas, TX
Using Eureca in passive charging everything works but I cannot deploy it while in active charging it no longer works although this is the only way to deploy it.
Yet it works with Hubble. o_O
No idea. For my STS2016. The Eureca is attached using k/j focused on the base.
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
8,726
Reaction score
2,690
Points
203
Location
Dallas, TX
Not sure. The CB is coded to attached to the structure? if close. K/J attach/detach. When does the Ctd occur. So technically the Eureca should be attached the cb not the SSV.
 
Top