Space Shuttle Ultra 1.25 Revision B development

Got it. The hydraulic cylinder shown there, is there another one on the inboard side as well?

No, one should be enough and having it inboard would make maintenance complicated.
 
Is this now more accurate:
 

Attachments

  • SRM_transporter_wheelset_revised.jpg
    SRM_transporter_wheelset_revised.jpg
    29.6 KB · Views: 473
No, actually the actuator should attach to a small arm, there is not much travel range.
 
No, actually the actuator should attach to a small arm, there is not much travel range.
Do you a photo of this arm? I just made it like your modification to the screenshot. I have very little reference images of the wheelsets. They were based off some photos from the Ares 1X stacking last year when the segments were transported from the Surges to the VAB.
 
Do you a photo of this arm? I just made it like your modification to the screenshot. I have very little reference images of the wheelsets. They were based off some photos from the Ares 1X stacking last year when the segments were transported from the Surges to the VAB.

here is a better view of a similar vehicle:

http://www.kamag.com/index.php?eID=...> | </a>&md5=a2d76ca00401856902007f0e99f00385

http://www.kamag.com/index.php?eID=...> | </a>&md5=228f84eb25b0b1778b3fe29c78fcdea6

The tilting actuator seems to be inside the vehicle or a worm drive.
 
here is a better view of a similar vehicle:

The tilting actuator seems to be inside the vehicle or a worm drive.
Can't make out any details in those photos. Are they really that important considering you can't actually see them unless you move the camera underground? Remember, KSC is very very flat and even. The hydraulic systems is just used to raise/lower the platform for pallet pick up/drop off. Other than that, it pretty much remains even.
 
Last edited:
Can't make out any details in those photos. Are they really that important considering you can't actually see them unless you move the camera underground? Remember, KSC is very very flat and even. The hydraulic systems is just used to raise/lower the platform for pallet pick up/drop off. Other than that, it pretty much remains even.

The actuator does not need to be visible, but I need something to animate properly. Looks like the top part of the bogey is directly attached to the Y-rotation axis, so no additional part is needed, but the bogey needs to be split into an upper and an lower part.
 
The actuator does not need to be visible, but I need something to animate properly. Looks like the top part of the bogey is directly attached to the Y-rotation axis, so no additional part is needed, but the bogey needs to be split into an upper and an lower part.
Like this:
 

Attachments

  • SRM_transporter_bogeys_separated.jpg
    SRM_transporter_bogeys_separated.jpg
    17.1 KB · Views: 450
Like this:

Yes, and the top part is installed fixed on the axis that permits rotation around the Y-Axis - it looks in the photos like it is connected to a disk shaped top part, together with the attachment of the hydraulic actuator.
 
New transporter mesh have been checked in. Hopefully this will work.
 
New transporter mesh have been checked in. Hopefully this will work.

Yes, that is useful, but you could have left the hydraulic actuator for rotating the wheel set away, it is not visible in any picture I can find and likely not existing, but instead they used a worm gear. Also the disk above the bogey is pretty flat as far as I can tell.
 
Yes, that is useful, but you could have left the hydraulic actuator for rotating the wheel set away, it is not visible in any picture I can find and likely not existing, but instead they used a worm gear. Also the disk above the bogey is pretty flat as far as I can tell.
Checked in a version with the hydraulic actuator removed.

---------- Post added at 11:47 PM ---------- Previous post was at 07:09 PM ----------

Currently we have a problem with camera direction when switching cab views. Seems like we have to add some additional code per Martin here: http://orbiter-forum.com/project.php?issueid=544#note3477
 
Does anyone think we could have a release, for Orbiter 2010 in time for STS-133 ? I'd like to get the payload working for that mission.
 
Does anyone think we could have a release, for Orbiter 2010 in time for STS-133 ? I'd like to get the payload working for that mission.
Could get "sporty" for that. Any special features needed? For this release we're aiming for mission completion, IE that you can fly a mission from pre-launch to wheelstop on the runway.

So for that we need at least a working GLS and a working comm system. I believe we were thinking about prototyping the comm system in the C/T before putting in the shuttle.
 
So for that we need at least a working GLS and a working comm system. I believe we were thinking about prototyping the comm system in the C/T before putting in the shuttle.

I still have issues in getting a useful voice comm system working in a smaller manageable context. The more different messages we need to send, the tougher things get, SSU is no combat flight simulator in which you can happily get through with a dozen phrases.

In Mercury, I work by using the "new" open Orbiter MFD Menu system, for the Black Dart, I currently experiment how to show a small temporary dialog window while you type.

I think the MFD Menu version is too limited for SSU (If you remember the "Married with children" episode with the Dodge telephone hot line, you should know the problem) the dialog window approach of the Black dart still suffering from design issues.

I think, for keeping things simple for the user, there should be just one voice communication system user-interface for all vehicles and buildings in SSU, a common back-end for it is mandatory.
 
Just checked in a fix (for the shuttle and Crawler).
Works perfectly now, thanks! BTW, could you add a function that logs G's over time during launch? I have found a generic SSME throttle curve diagram that could help us nail down why we are MECO'ing some 45 seconds early compared to the real shuttle.

I think we're running too hot somewhere and this diagram could help us nail down if we're hitting milestones too early during ascent. If it helps, the sample time is every 5 second starting at T0 with G's being every 0.25 G.
 
Works perfectly now, thanks! BTW, could you add a function that logs G's over time during launch? I have found a generic SSME throttle curve diagram that could help us nail down why we are MECO'ing some 45 seconds early compared to the real shuttle.

I think we're running too hot somewhere and this diagram could help us nail down if we're hitting milestones too early during ascent. If it helps, the sample time is every 5 second starting at T0 with G's being every 0.25 G.

Really G's or better vacuum and effective thrust, with throttle level in %RPL?
 
Back
Top