Launch MFD releases

Looks fine, but please give me links to the vessels so I can do something about it.
 
Neptune [ame="http://orbithangar.com/searchid.php?ID=4693"]Neptune-1 Medium Launch Vehicle 2.0[/ame]
Falcon9 [ame="http://orbithangar.com/searchid.php?ID=5442"]SpaceX launch vehicles and Dragon[/ame]
Thanks.
 
Neptune - I can't run it in a sim, because it crashes despite I've installed the dependencies
Falcon9 - I can't launch it, because it doesn't react on the engne controls ...
 
That's weird , both are running fine here and the falcon9 reacts with the PID autopilot.

---------- Post added at 06:06 PM ---------- Previous post was at 05:55 PM ----------

although with disastrous results and weird behavior, it says ideal pitch 75 degrees for a lot of time.

---------- Post added at 09:09 PM ---------- Previous post was at 06:06 PM ----------

Can anyone confirm if the launch compass has problems: Target (asc) or (desc) are 0° every time whatever the target is.
I tried with orbiter 2010 p1 since I use the beta and the problem is still there. It works with LaunchMFD 1.4.6 but not with 1.5.0.
 
Is there a space in the PITCH_PROGRAM_TIME line in your .cfg?

I ran across this myself. It is now fixed in the current version, but the one you are using may still have that. Make sure there is no spaces. When there is no valid pitch program, it goes to hold a 75 degree pitch to ensure the space craft does not crash into the earth.
 
I have I think the current version (1.5.0) and no, no space in the indicated line.
Do you have the same problem with the launch compass in the last version ?
The 1.4.6 I mention is only a test I did to check for the launch compass behavior.
 
I'll get back to you later on this issue. Right now I'm under some time pressure.
 
Does the roll program have to be done manually? I can't get the shuttle to roll using this and setting target to ISS
SPACE_BANK = 100 50 0
ATMO_XY = 4 12 0
ATMO_BANK = 1 2 0
ATMO_CONTINUOUS_CONTROL_SWITCH_ANGLE = 45.0
ATMO_BANK_TARGET_WINGS_LEVEL_SWITCH_ANGLE = 20.0

UPSIDE_DOWN = TRUE
ROLL_ALT = 0.5e3

PITCH_PROGRAM_ALTITUDE
0 90
2.5 70
7 60
10 50
15 40
20 30
48 20
95 10
150 0
END_PITCH_PROGRAM_ALTITUDE
 
if things are working correctly, the roll program is done automatically. No manual input required. All you need to do is enter the target, activate the autopilot, and throttle up.
 
Ahhh Haaa!!! Now I know why It wasn't working. In OMP's earth.cfg the earth don't rotate. Humm so now what? Anybody have any ideas?
 
Non rotating Earth? what is the point of that?

Using a non-rotating earth is safe to call working by a new set of rules, that is for sure. I have no idea if that condition is out of bounds for LaunchMFD, I will have to let Enjo answer that one.
 
The non-rotating earth in OMP is due to clients that view other vessels they have a jerkiness effect unless the earth isnt rotaing. It interferes with viewing and docking for sure as the vessels postion is constantly changing. Bouncing back and forth and the like. And without the luxury of time acceleration the assent has to be spot on
 
Last edited:
Hi Enjo,I am kind of confused about using direct acsent,in the playback folder you have three scenarios 1. direct acsent phase 1. 2.direct acsent 2nd phase,and 3. direct acsent 2nd phase syncro,Ok here is where I get confused. when I use the 1st scenario direct acsent it gets my DG-S up to the ISS,but there is no 2nd phase,and I can get to about 300km from the ISS. Now the phase 2 scenario has the DG-S cruisng along waiting for the ISS to catch up with it,and the text says turn AP on and wait for Delta T to go to 0.So the question is are there 2 phases when using the direct acsent AP?and if there is how do I know when to start the 2nd phase up? like the scenario you included called direct acsent phase2?Thanks
 
the playbacks do not have the whole thing.

If you want to fly direct ascent, this is what you do.

Take off when you see your target is going to pass over your departure point, but when it is significantly behind you (Delta T is still positive). Take off, get to a good cruise. Then use LaunchMFDs heading guidance and follow it, either using autopilot, or if you are using somethine like DGIV, you can use its own atmo ap.

Follow the heading guidance which will get you on the right plane as your target.
Then get into a nice cruise. For the DGIV, I recommend something like 15 km in altitude. And the slower the better. That means the less time you have to wait, since you are waiting for the target to catch up to you. As you see Delta-T get lower, kill any ship autopiots, acivate LaunchMFDs DA Autopilot, then wait. It will eventually kick on, (a blue line of text will appear which is confirmation that it is on its way). Then sit back and watch as it brings up right up to your target. It is a beautiful thing to watch.
 
OK Cras, I sort of get it,but can I use the launch mfd autopilot to get me to the required heading,and the desired cruise speed before I use the direct acsent autopilot?,also I am using the DG-S which has scram engines.

---------- Post added at 02:46 PM ---------- Previous post was at 12:41 PM ----------

OK,when I see the Delta T start lowering, I turn off the launch MFDs default autopilot,and press mod button twice to turn on direct acsent AP,and I also turn on the COR button,and finally the AP button again,and the ship goes crazy heads for the ground,and crashes.What am I doing wrong?Thanks:shrug:
 
Last edited:
There is something called the "DEF" button. I think it is DEF. It is on the right hand side of the MFD. That button will turn off the pitch channel, and only provide guidance for the heading. You can use that with the autopilot to let it fly to the heading. You then need to keep the ship under control pitch wise with throttle and/or trim.

As for the thing going nuts in DA mode and pitching down is something I have never seen, so I am not sure what is going on. I have activated it at the wrong time before and I see it just pitch straight up in the air and do nothing useful aside from that.

Make sure your RINC is zero. When that is zero, and your Delta T is getting close to zero, pressing the autopilot button should then cause it to pitch up. It also controls the engines.
 
Thanks Cras for all the help ,I finally pulled it off,I came up to the ISS,about 10km from it, sure was a magnificent sight,and awesome job with this AP Enjo.:cheers:
 
Hi Enjo,I am kind of confused about using direct acsent,in the playback folder you have three scenarios 1. direct acsent phase 1. 2.direct acsent 2nd phase,and 3. direct acsent 2nd phase syncro,Ok here is where I get confused. when I use the 1st scenario direct acsent it gets my DG-S up to the ISS,but there is no 2nd phase,and I can get to about 300km from the ISS.

Phase 2 is an extension of phase 1. If you grabbed steers right after the phase 1 playback ends, you'd be in phase 2 or phase 2 synchro, whatever DA mode you choose. They are alternative ways to perform the manouevre. The synchro mode is needed, because the first mode is impossible to perform when you cruise with like > 4 km/s.

The two modes can be switched with the DEF button on Direct ascent page.

Now the phase 2 scenario has the DG-S cruisng along waiting for the ISS to catch up with it,and the text says turn AP on and wait for Delta T to go to 0.

Interceptor said:
OK,when I see the Delta T start lowering, I turn off the launch MFDs default autopilot,and press mod button twice to turn on direct acsent AP,and I also turn on the COR button,and finally the AP button again,and the ship goes crazy heads for the ground,and crashes.What am I doing wrong?Thanks:shrug:

This is another source of confusion. Currently the MFD doesn't store AP using/not_using flag in scenario (playback) file, so after the playback starts, you have to click on the AP button to get the correct readouts.

To make things clear, immediately after you launch and get into more or less correct direction, you should enable the DA AP and the COR and keep them, because they are specifically programmed so that they will always try to keep you "under" the target's plane, even if you go beyond it. You may notice sometimes that the DA AP suddenly turns you 90* right, then after some time 90* left. This meant that you got over the plane (from south to north), then, after some time of turning 90* right crossed it (from north to south), and finally, you have to reallign by turning 90* left, and slowly to the right (you can see it on the Map MFD). It's all done automatically only in the DA autopilot (not in the standard one), so be sure to enable it as soon as you can.

The cruise speed is intentionally not controlled by the AP, because you might be using DG, DG-S, XR, or DGIV that all have their own specifics. Besides, as Cras noted, at least initially, you want to lower the cruise speed to make the intercept happen sooner. In short - cruise speed and trim control is always left to the user.

Make sure your RINC is zero. When that is zero, and your Delta T is getting close to zero, pressing the autopilot button should then cause it to pitch up. It also controls the engines.

Zero RINC increases precision, but it's the DA AP that helps you keep it that way. You could try to do it yourself by following the flight director of course, that would have exactly the same effect as using the AP, plus human error, but I didn't predict the manual use case and the RINC correction works only when the AP is on. I'll try to provide a fix for that.

And an another tip-o-the-hat from my own experience:
When you use the regular DA mode, once the orbital insertion starts, you will notice that the ship has a hard time pitching up to the target pitch, because it's neither in thick atmosphere, nor in the space. You can help it by using the numpad to reach the target pitch, until in space. This greatly increases precision, and leaves more space for the main engines to correct the interception time.


If anything is still unclear, I'm happy to answer, and thanks for the thumbs up :)

As far as previous bug reports are concerned - I didn't forget about them and I will look into them when I have some free time.
 
Last edited:
OK,Enjo I might have found a bug,or maybe not?anyways when I use the target box,and choose any target besides the ISS, like the Arrow it says manual target,and,the correction option does not work.Thanks
 
Last edited:
Back
Top