Centaur G/G Prime High Energy Upper Stage

[Loru]

Ok - got some issues with specmap. Do you mind splitting mesh into 3 meshgroups so I can adjust specular levels in msh file?

That may help you tune specularrity to match Centaur mesh.

 

[DaveS]

Ok - got some issues with specmap. Do you mind splitting mesh into 3 meshgroups so I can adjust specular levels in msh file?

There's no problems with this.

 

[Loru]

 

[DaveS]

Very nice. Do you think you could increase the sides on the nozzle a bit so it has smoother shape? Right now the edges are very visible.

 

[Loru]

Nozzle is 24 sided lathed object. Increasing sides will increase polycount a lot and TBH remaking 80% of the mesh itself.

 

[DaveS]

Nozzle is 24 sided lathed object. Increasing sides will increase polycount a lot and TBH remaking 80% of the mesh itself.

OK. Was thinking that the nozzle was a freestanding object, separate from the rest of the engine hardware.

 

[Loru]

Engine package: http://alteaaerospace.com/loru/orbiter/rl10.zip

- 3dmodel folder contains max file, 3ds file, layered & grouped PSD with texture and normal map, UVW mapping pattern and normal map in bmp format.
- rest (Config, Textures, Meshes) is simple CFG vessel in proper orbiter folders as material reference (multiple conversions are causing material changes).

 

[DaveS]

Engine package: http://alteaaerospace.com/loru/orbiter/rl10.zip

- 3dmodel folder contains max file, 3ds file, layered & grouped PSD with texture and normal map, UVW mapping pattern and normal map in bmp format.
- rest (Config, Textures, Meshes) is simple CFG vessel in proper orbiter folders as material reference (multiple conversions are causing material changes).

Thanks. I'll integrate the engine once I'm done with the new REMs.

Edit:
Did you see my post about the Deployment Adapter here: http://www.orbiter-forum.com/showthread.php?p=497422&postcount=292?

 

[Loru]

Yep - not sure how much time I'll have on my hands though. I'm quite busy with my game project at the moment as I want usable alpha by the end May.

 

[DaveS]

Yep - not sure how much time I'll have on my hands though. I'm quite busy with my game project at the moment as I want usable alpha by the end May.

No problem. It will still look good. I thought I would ask as I'm nearly done with it. It's just lacking some of the avionics boxes (2xPICU, 1xPLIU, 2xCDU, 1xSignal Conditioner).

---------- Post added at 03:54 PM ---------- Previous post was at 02:40 PM ----------

Latest SC-1 on-orbit, now with engines thanks to Loru! This has now been checked in into the ShuttleCentaur branch.

---------- Post added at 04:42 PM ---------- Previous post was at 03:54 PM ----------

Here's the data for the REMs

//Attitude control thrusters
//Quad 1
P1: 0.9524, 1.1165, -4.1463
Y1: 1.0825, 0.9864, -4.1463
//Quad 2
P2: 0.9524, -1.1165, -4.1463
Y2: 1.0825, -0.9864, -4.1463
//Quad 3
P3: -0.9524, -1.1165, -4.1463
Y3: -1.0825,- 0.9864, -4.1463
//Quad 4
P4: 0.9524, 1.1165, -4.1463
Y4: 1.0825, 0.9864, -4.1463

//Settling thrusters, these are only used for propellant settling, not attitude control
//Quad 2 settling thrusters
S2A: 1.0038, -1.0122, -4.2222
S2B: 0.9732. -1.0422, -4.2222
//Quad 4 settling thrusters
S4A: -1.0038, 1.0122, -4.2222
S4B: -0.9732. 1.0422, -4.2222

They're now aligned with a single axis, so figuring out the directions should not be a problem. The settling thrusters can be used in either one of two modes, 2 thrusters (2S) or 4 thrusters (4S). The nominal sequence of events was first the 2S mode in an propellant collection maneuver some 5 minutes prior to MES. Then at MES-1 minute, it switched over to the 4S mode for propellant settling.

Edit: Forgot to mention that the Centaur is now rotated to match the schematics in the TC-1 Postflight Report.

 

[GLS]

Holy cow, that looks awesome! I'll get to work then.

---------- Post added at 08:22 PM ---------- Previous post was at 08:10 PM ----------

Edit: Forgot to mention that the Centaur is now rotated to match the schematics in the TC-1 Postflight Report.

Hmmm, are you sure you rotated in the correct direction? Looks like it's 180º from where it should be... I think the feedlines should be on the left side, and the pair of tanks on the right, and starting at the top moving clockwise the thrusters should be 1-2-3-4.

 

[DaveS]

Hmmm, are you sure you rotated in the correct direction? Looks like it's 180º from where it should be... I think the feedlines should be on the left side, and the pair of tanks on the right, and starting at the top moving clockwise the thrusters should be 1-2-3-4.

I see what you mean. Yes, it is incorrect now. I'll check in the corrected mesh in a few minutes. Fixing the REMs shouldn't be issue though, as all you need to do is switch around the current ones.

Quad 1 Now = Quad 3 Fixed
Quad 2 Now = Quad 4 Fixed
Quad 3 Now = Quad 1 Fixed
Quad 4 Now = Quad 2 Fixed

 

[GLS]

I see what you mean. Yes, it is incorrect now. I'll check in the corrected mesh in a few minutes. Fixing the REMs shouldn't be issue though, as all you need to do is switch around the current ones.

Quad 1 Now = Quad 3 Fixed
Quad 2 Now = Quad 4 Fixed
Quad 3 Now = Quad 1 Fixed
Quad 4 Now = Quad 2 Fixed

Yes, I've done that already.
I also need the current offset of the attachment plane between the Centaur and the CISS, as looks like it changed (and probably the top plane where the adapter would meet the Centaur).

 

[DaveS]

The fixed mesh has now been checked in.

---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------

Yes, I've done that already.
I also need the current offset of the attachment plane between the Centaur and the CISS, as looks like it changed (and probably the top plane where the adapter would meet the Centaur).

Yes. The current CISS Deployment Adapter doesn't include the 2.25" (0.06985 m) SuperZip* section. There's an identical section on the Centaur aft adapter to mates to section on the CISS DA. So the mating plane would be at the ends of these sections.

 

[GLS]

It took 6 or 7 attempts, but finally manage to overcome the tree branch conflict that was preventing me from committing stuff to the ShuttleCentaur branch. Anyway, the new code is up. Still needs some tweaking on the Centaur/CISS attachment coordinates, but other than that it's good to go! We should buy some ad space here in the forum to get customers for the Centaur. :lol:

A small side note: there's a bug in the CRTMFD (the one in the trunk not the branch) that CTDs the whole works when it is opened in another vessel, so if it CTDs when changing vessels it's CRTMFDs fault (and mine, as I'm to blame here). I'll work on a fix now, but in the meantime here's the heads up.

 

[DaveS]

The G is here! Now available in the ShuttleCentaur branch!

 

[GLS]

DoD, get your payloads ready! :thumbup:
I'll get to work on that one as soon as I fix a long existing bug I just discovered in CRTMFD: it saw the default Atlantis as the SSU. Result: CTD.

 

[DaveS]

DoD, get your payloads ready! :thumbup:

Don't forget NASA as they ordered one as well for the Venus Radar Mapping Mission (VRMM, subsequently renamed "Magellan"). As far as I have been able to determine, launch was scheduled for April 6 1988 as mission STS-81I.

 

[GLS]

Shouldn't the cg of the Centaur G be somewhere in the middle of it? If you could move it aft into the LOX tank it would be nice, and please say by how much it moved so I can correct the thruster positions.

 

[DaveS]

Shouldn't the cg of the Centaur G be somewhere in the middle of it? If you could move it aft into the LOX tank it would be nice, and please say by how much it moved so I can correct the thruster positions.

Checked in a moved version. Amount is 3.5844 m.