Project Space Shuttle Vessel

[Tiny_Bob]

coming soon (hopefully yall can tell what this will be)

 

[GLS]

View attachment 46194
coming soon (hopefully yall can tell what this will be)

Will you be able to launch, deploy the new one, grab the old one (you'll need the RMS for that), and land in one orbit? (probably not because ascent guidance isn't that great for rendezvous, and also the real one never got the upgrade to also target downrange position at MECO, to place the vehicle on an intercept trajectory with the target... but just making a deployment in one orbit should be fun enough).

BTW: a better thread for payloads: https://www.orbiter-forum.com/threads/space-shuttle-vessel-payload-development-thread.42248/

 

[Tiny_Bob]

Will you be able to launch, deploy the new one, grab the old one (you'll need the RMS for that), and land in one orbit? (probably not because ascent guidance isn't that great for rendezvous, and also the real one never got the upgrade to also target downrange position at MECO, to place the vehicle on an intercept trajectory with the target... but just making a deployment in one orbit should be fun enough).

BTW: a better thread for payloads: https://www.orbiter-forum.com/threads/space-shuttle-vessel-payload-development-thread.42248/

ive been doing some testing to try to somewhat pull off that mission. ive edited to ascent targets in the mission file but that causes a negative HP at MECO haha

 

[Channex]

Hello!

I'm unable to start the mission editor, do i need to set something up?
Not getting the promt to point it towards Orbiter.exe

Thanks

 

[GLS]

Hello!

I'm unable to start the mission editor, do i need to set something up?
Not getting the promt to point it towards Orbiter.exe

Thanks

Hi there!

Have you used Mission Editor in previous versions, and only the latest one doesn't work? Or is this the first time you use Mission Editor?
Anyway, the problem could be that you don't have the .NET Framework 4.8 installed: I think this is it: https://support.microsoft.com/en-us...-windows-9d23f658-3b97-68ab-d013-aa3c3e7495e0

 

[Channex]

No, just came back to SSV after a few years. Fresh install, mission editor wont launch. I do have the latest .Net

 

[GLS]

No, just came back to SSV after a few years. Fresh install, mission editor wont launch. I do have the latest .Net

Just to confirm, you are NOT using SSV v1.13, right?

 

[Channex]

Negative, latest version. 1.15

 

[GLS]

So it turns out this issue is related to the cultural settings in Windows, and how each culture looks at "." and "," in numbers, which caused a parse operation to fail. I think the latest changes in Mission Editor brought the issue forward to the start of the app, causing the window to not even show up. In previous versions the CTD would happen while using Mission Editor... I'm surprised this isn't an issue for more people (or maybe they just don't report it?).
Given that, I'm not sure if I should rush to release the fix, or wait a couple of weeks and maybe add some more things.

Anyway, thanks to @Channex for the help in debugging this issue.

 

[Tiny_Bob]

ive been doing some testing to try to somewhat pull off that mission. ive edited to ascent targets in the mission file but that causes a negative HP at MECO haha

yeah i dont think it likes this haha

 

[Yerson2008]

I would suggest the following idea: If an engine exceeds a critical limit (turbo pump temperature, combustion chamber pressure), simulate the automatic shutdown of that engine by the GPC. This would force it into an abort mode (RTLS, TAL, ATO, AOA). Ideally, try to simulate the abort modes; that would be my idea to make it a bit more realistic.

 

[GLS]

View attachment 46225View attachment 46226
yeah i dont think it likes this haha

I don't think a negative HP at MECO is a problem (it actually needs to be, so the ET doesn't land in Africa or Europe).... but going to a 90NM altitude MECO means that ASCENT TRAJ 2 display is useless (in v2.0 those trajectory lines will be I-Loaded so they can be changed for each mission).

 

[Tiny_Bob]

for the I-Loads, C1 and C2 and THETA-OMS, are those for a rendezvous intercept or something else? they are described as "target xxxx" in the I-Load list file

 

[GLS]

for the I-Loads, C1 and C2 and THETA-OMS, are those for a rendezvous intercept or something else? they are described as "target xxxx" in the I-Load list file

Those are the PEG-4 targets for the OMS burns. PEG-7, using the dvX, dvY, dvZ items at the bottom of the display just "blindly" burn to get that dV, but PEG-4 is smarter, and more complex: it targets an altitude HT, at an angle THETA from the launch site (in OPS1), so that the vehicle gets to that target point with a velocity dictated by C1 and C2. I'm not remembering exactly which is which now, but they represent a relationship between vertical and horizontal velocity. These should be described much better in the SCOM and/or the DPS Dictionary (in the XXXXX MNVR YYYYY display section).
For this case, you need to know where the target is, HT and THETA, and then C1 and C2 need to be something such that the delta velocity on approach between the OV and the KH-9 can be nulled without using all of the RCS... not easy to calculate right now.
Another factor to consider is the plane matching, which seems like it would be done pretty much all during ascent, which is currently a weak point in SSV.
This deploy and retrieve mission is beginning to look like a bit too much to ask out of SSV at the moment... if I were you, I'd would focus more on a deploy mission alone, getting the KH-9 accurate, etc.

 

[Tiny_Bob]

Those are the PEG-4 targets for the OMS burns. PEG-7, using the dvX, dvY, dvZ items at the bottom of the display just "blindly" burn to get that dV, but PEG-4 is smarter, and more complex: it targets an altitude HT, at an angle THETA from the launch site (in OPS1), so that the vehicle gets to that target point with a velocity dictated by C1 and C2. I'm not remembering exactly which is which now, but they represent a relationship between vertical and horizontal velocity. These should be described much better in the SCOM and/or the DPS Dictionary (in the XXXXX MNVR YYYYY display section).
For this case, you need to know where the target is, HT and THETA, and then C1 and C2 need to be something such that the delta velocity on approach between the OV and the KH-9 can be nulled without using all of the RCS... not easy to calculate right now.
Another factor to consider is the plane matching, which seems like it would be done pretty much all during ascent, which is currently a weak point in SSV.
This deploy and retrieve mission is beginning to look like a bit too much to ask out of SSV at the moment... if I were you, I'd would focus more on a deploy mission alone, getting the KH-9 accurate, etc.

yeah i more so started it to see how much is possible, Indy also gave me the warning of "this probably wont work like you want it" haha

 

[Tiny_Bob]

how does the KU work for radar? does the target vessel need anything special on it?

 

[GLS]

how does the KU work for radar? does the target vessel need anything special on it?

That is the only thing it does...
As far as the target goes, nothing special is needed as the radar only works in passive mode, so it just needs to be close enough to be detected, I think the maximum range it's like 150kft at maximum power output.

 

[DaveS]

I think there's a bug either in the SSV Mission Editor or SSV itself as I can't get the payload retention latches to line up with the actual pins on the SpaceHAB SRM. Visually the module is in the correct location but not the latches themselves. PL IDs are 214 for the FWD trunnion pins and 238 for the aft trunnion pins along with the keel pin. I have doubled checked coordinates for the SpaceHAB itself and they're exactly right.

This is with SSV v1.15.

 

[GLS]

I think there's a bug either in the SSV Mission Editor or SSV itself as I can't get the payload retention latches to line up with the actual pins on the SpaceHAB SRM. Visually the module is in the correct location but not the latches themselves. PL IDs are 214 for the FWD trunnion pins and 238 for the aft trunnion pins along with the keel pin. I have doubled checked coordinates for the SpaceHAB itself and they're exactly right.

This is with SSV v1.15.

I've placed 2 DFI pallets at those locations and they show up there as expected, and counting the PLIDs, the latches seem to be in the correct place.
Where is the attachment for the SpaceHAB? Looking at a photo of STS-95, the PLIDs (and latches) are in the right place, so my guess is the SpaceHAB attachment isn't where it should be.

 

[DaveS]

I've placed 2 DFI pallets at those locations and they show up there as expected, and counting the PLIDs, the latches seem to be in the correct place.
Where is the attachment for the SpaceHAB? Looking at a photo of STS-95, the PLIDs (and latches) are in the right place, so my guess is the SpaceHAB attachment isn't where it should be.

The attachment is on the keel pin of the SpaceHAB and the coordinates are correct, no mixing up of positive or negative.