Project CST-100

[N_Molson]

Atlas412 alpha v0.20

New features :

- Rocket is attached to a launchpad before liftoff.
- Guidance program (pitch) for the first stage.
- Some minor fixes.

Note :

The scenario now begins with the launchpad selected. Press "O" (the letter) to start a 10 seconds countdown. Right now mission time is not visible but this will be quickly fixed.

I sometimes have a display bug with the fuel gauges of the first stage. Can you confirm or not ?

 

[ky]

New features :

- Rocket is attached to a launchpad before liftoff.
- Guidance program (pitch) for the first stage.
- Some minor fixes.

Note :

The scenario now begins with the launchpad selected. Press "O" (the letter) to start a 10 seconds countdown. Right now mission time is not visible but this will be quickly fixed.

I sometimes have a display bug with the fuel gauges of the first stage. Can you confirm or not ?

No, I haven't noticed that.

 

[N_Molson]

Well, nevermind, it doesn't happen with D3D9 client.

The guidance program should send the second stage to an Apa of 195-200 km. Is it so ?

 

[ky]

Yep, it does. Right now Im getting the basic CST mesh without a VC ready, along with the SM. What was the diameter of the resized adapter?

 

[N_Molson]

The diameter is 4.56 meters, the number given by Boeing on the CST-100 factsheet as max diameter (should be the bottom of the capsule, without the thrusters housings).

 

[diogom]

Does the guidance extend to the 2nd stage too?
Also, at 2nd stage separation, all the values disappear from the MFD's, normal if I close one of them though.
Other than that, works ok

Edit: Nevermind the first part. Getting a good orbit with the pitch program here

 

[N_Molson]

Does the guidance extend to the 2nd stage too?

This is in progress. Going step by step to stay safe.

Also, the current first stage guidance is very basic. You will soon be able to modify the pitch program and set a launch heading. Did that for the Sigma rocket already, so that's "technology transfer".

Also, at 2nd stage separation, all the values disappear from the MFD's, normal if I close one of them though.

Hmm what do you mean precisely by "all the values disappear from the MFD's" ?

 

[diogom]

Hmm what do you mean precisely by "all the values disappear from the MFD's" ?

I'll get a screenshot

---------- Post added at 09:33 PM ---------- Previous post was at 09:22 PM ----------

Huh. Doesn't happen now for some reason, happened more than once at second stage separation before. I meant that, for example, on orbit MFD, the numbers disappeared and only the visual orbit display and the planet were visible.

 

[N_Molson]

Atlas-412 alpha v0.21

Huh. Doesn't happen now for some reason, happened more than once at second stage separation before. I meant that, for example, on orbit MFD, the numbers disappeared and only the visual orbit display and the planet were visible.

I had that one too. Disappeared after a while too. Well, let's remember it, but for now it seems it's not a big deal. :shrug:

Well, here is the v0.21 alpha release.

Features & fixes :

- Guidance for the second stage and automatic engines shutdown (should bring you on a 240x200 km orbit, if everything goes as planned).
- Implementation of a mission timer, and cockpit-view display.
- The DemoCap wasn't separating properly, fixed.
- Other hidden but time-consuming stuff !

Notes :

- The guidance system manages only the Pitch channel for the first stage, and the Pitch and Roll channels for the second stage. So the rocket can "slip", since there is no yaw control. If that happens, a shot of Killrot should help (don't let it fight the guidance program, though).

 

[diogom]

Apart from the "disappearing MFD" issues, (will have to test a few more times to be sure if they go away or not), got the democap on a 240x200 orbit, give or take a few meters :thumbup:
I noticed the countdown timer stays at ten for ten seconds, then starts normally at T-0, so no T-9,8,etc

 

[N_Molson]

I noticed the countdown timer stays at ten for ten seconds, then starts normally at T-0, so no T-9,8,etc

I can't reproduce that one. Looks like another display problem. :hmm: Does it happen with D3D7 and D3D9 clients ?

 

[diogom]

D3D7. It's also on the stage1's timer, stays at MET:-10, the launchpad's works fine

 

[ky]

I'm having some issues too, the launch autopilot does not initiate at all, and there is no countdown, then at 1st stage separation, the 1st stage rockets ahead of the second stage.

 

[N_Molson]

ky, did you try deactivating all but default modules (keep OrbiterSound) ?

 

[ky]

ky, did you try deactivating all but default modules (keep OrbiterSound) ?

I did, I'm running it in a clean install. I'll post screencaps in a minute.
EDIT: The second problem went away, the first is still there.

After pressing "O"

The gauges do seem a bit out of sync

 

[N_Molson]

The second problem went away

Weird. I'm going to search. Seems that there is a serious problem with the on-screen display. The "-1000000000" value is coherent, because it is the starting value I set for that variable. But it should not stay like that after you pressed O.

Are the screenshots from D3D7 ? Same problem with D3D9 ?

Edit : OK OK I think I got it. This happens when :

1) You press O and start the countdown in the launchpad.
2) You switch focus to the rocket while the countdown is running.

It's "normal" for now.

By "out of sync", what do you mean precisely ? I have my idea but need more details.

 

[ky]

Are the screenshots from D3D7 ? Same problem with D3D9 ?
By "out of sync", what do you mean precisely ? I have my idea but need more details.

The screenshots are from D3D7, and I cant test it with D3D9 since my graphics card doesn't meet the minimum requirements. By out of sync, I meant that your gauge display is running out slower than the HUD fuel gauge. For example, when the HUD display says that there is about half the amount of fuel left in the 1st stage, your fuel gauge says there is less than half.

 

[N_Molson]

Atlas-412 alpha v0.22

This release should fix the display problems mentionned earlier (custom gauges problems + "empty MFD's" bug).

Runs flawlessly on my setup with both D3D7 and D3D9.

Please tell me if you have an improvement with this new version. :tiphat:

 

[ky]

Runs flawlessly here also, both problems are fixed, and I got into a 241 x 203 km orbit.

 

[diogom]

Flawlessly here too. Also gave the LES a test at different times, works great.