Search results

You are very welcome, my friend :) I am very happy you have succeeded! (y) P.S. I will need your Kourou CSG + Ariane5 soon. Merci!

Strange. Some things you could try: 1. Move all the "rocket release" code into the clbkPreStep(....) section. 2. Check your attachment point parameters for typos, make sure vectors are normalised and orthogonal, etc. That's about all I can think of 🤷‍♂️

So when your rocket is released, this line GetAttachmentStatus(PAD1); is going to return NULL, isn't it? So anything downstream that needs a valid hVessel is going to fail. So you need to put in a conditional, you could do this: void BOLAUNCHTABLE::clbkPostStep (double simt, double simdt...

Good launch today, in spite of the weather (y) Sadly I missed it (watching replays now), but here's a launch scenario for today anyway. Falcon9 autopilot set for 51deg.equ., 200km x 400km orbit. Scenario starts T-3mins.

Re: Launch pad release of rocket.... try the following maybe? OBJHANDLE hvessel = GetAttachmentStatus(PAD1); VESSEL2* v = (VESSEL2*)oapiGetVesselInterface(hvessel); thrust = v->GetThrusterGroupLevel(THGROUP_MAIN);

Gaah! Scrubbed by weather. Try again tomorrow (weather permitting).

Crew-11 Launch Hi, attached below are a scenario for Crew-11 launch on the Falcon9 and the relevant falcon9 .cfg file. Scenario in the Crew Dragon 2022 folder. Falcon9 for Orbiter2016 add-on is required. ISS state vectors from Horizons (see above post by @francisdrake if using Orbiter2024)...

Just out of curiosity, here's a 3-view comparison of the 300-day trajectory prediction by LagrangeMFD (rotating frame, Earth-Sun fixed) from Gargantua2024's scenario (Horizons data) vs. the halo orbit that LagrangeLaunchMFD will put you in: Gargantua2024 scenario: LagrangeLaunchMFD launch...

Oh, also, if you use static const double step = RAD * 60; then you should change this line as follows: int idx = max (0, min (5, (int)(aoa*istep))); (The number where the "5" is should = nabsc - 2)

Hi, well it could be that you haven't defined the function for all possible AoA, -180 to +180 deg. You have 6 "steps" (nabsc - 1) and static const double step = RAD * 22.5; 6 x 22.5 = 135 So you only defined CL and CM over 135deg range. Either set static const double step = RAD * 60; or static...

Yes, by all means. ....and thanks to everyone for your work to make MS2015 compatible with O2024 (y) Cheers, Brian

Great! No problem at all - I haven't had time to do anything much. Take as much time as you like, no worries. Looking forward to seeing the updated models :-) Cheers, Brian

What I got from the pdf's is the attitude is managed by RCS until 91km alt. when its just left to find its equilibrium attitude of AoA -11.1. Specificaly, it sets the AoA -20 at 9 mins before entry and keeps it there until entry alt. At that point I think it just nulls out any rotation - if you...

My pleasure and privilege, mate (y) My understanding from the AAIA paper is that AoA -20° is set 9mins before entry, then set to -11.1° at 243km alt....... Yes, I had to read that section a few times! I think you can vary the entry angle by changing the time and velocity vector of the burn...

Thanks. I need to re-read and understand the entry targeting parts. Two things I got already: 1) Nominal entry angle is 16.8 (not 15, don't know where I got that, I blame poor eyesight and creeping senility ;) ) 2) Aeroshell hits 13.6g (ouch) during entry. So I'm guessing it goes deeper in the...

Well, thanks! Nice to know I at least look like I know what I'm doing....;) Do you mean the Aeroshell during reentry? Steering will get difficult as dynamic pressure increases. Tweak away by all means but I think moving the airfoil ref point will destabilize things. Try decreasing the RotDrag...

Thanks! I'll give it a read. The smallest deorbit dV I found was 148m/s - making the burn at the nominal point of True Anomaly 217deg, just getting the PeA down to -27km, not targeting anything in particular. But maybe I'm wrong about the reentry parameters I got from the AAIA paper? In which...

Hi, Interstage sep works fine. Stage 2 ignition fails every time for me unless IGNITE_DELAY > 0 (or engine command in the guidance file). OK, I'm getting the hang of how it all works, I think. I've just been concentrating on the Aeroshell aerodynamics for now. This AIAA paper has some useful...

Yes, your MS2015 .dll etc. For some reason I had a hunch it might be something to do with IGNITE_DELAY parameter. I changed the Titan .ini 2nd stage IGNITE_DELAY to 3.00 and now it all works fine (with your original guidance file). Go figure. Its probably just me. Its a drawback if you're...

Hi, thanks very much for this, looks great (y) Viking is one of my favourite missions. I tried the launch scenario (using Orbiter2016), I like the trees, Titan looks awesome. Autopilot launch works fine (maybe a bit steep in the gravity turn?) ...except the second stage fails to ignite. You can...