Search results

Starting to texture

(First stage without small details)

I like how terms that are used today like "forum" or "tablet" are based on ancient analogues.

I felt that it was a bit too short, and I wanted to make it a few meters taller. I decreased the thrust/weight ratio of the rocket from ~1.37 (the twr of Dmitry's F9M concept) to ~1.2 (twr of the real F9) and made some other minor changes (Dmitry told me via message on the NASASpaceflight forum...

Update: For some time I have had a problem in which the first stage return to launch site program would overshoot the target. Recently, and with BrianJ's help, I found that could be solved by modifying the "timetoimp" (not timetoimp2) and "k_factor" variables within the DoReentryCorrection()...

(note: by changing the "pitch_limit" variable within the F9R source code, the pitching profile of the first stage can be calibrated (BrianJ pointed out to me that it was very sensitive, i.e. changing it by 0.1 can be significant) up to a certain point (30 km) where the autopilot switches to a...

Based on several exchanges I've had between BrianJ and myself, I think I have figured out the reason for why it tends to overshoot. These are the issues: Again, this rocket is based on the ratios of this hypothetical methalox Falcon 9. I also looked at the Silverbird Launch Vehicle Performance...

That is incredibly disturbing.

This massive structure.

But here's the issue, it needs to be able to set the landing target before the spawning at separation.

But how can I implement peg.cpp in this custom dll? Is that possible? I could implement it in ms2015. But the point of this was to have the boost-back first stage. Another thing is that the F9R code tries to get the first stage to a certain apogee at the same time it reaches a certain reserved...

I still don't quite understand how the algorithms work, but from my understanding, the F9R guidance autopilot tries to pitch the rocket after reaching a certain altitude (30 km) so that the rocket reaches a certain specified apogee (default of 135 km) as soon as the first stage runs out of...

If it is possible, can you please tell me how you calibrated your ascent program?

What part of the code do you recognize? Never mind, perhaps it's mixed up. But I'm still wondering what exactly determines the trajectory of the rocket. edit: countdown

Except it resets to "PADBIAS 1.00" if you make a quicksave or save the current scenario.

Yes, during that launch, the first stage was pitching down more than it should. Here is a section of the F9R code, the relevant functions seem to be "CalcFlightVector" and "GoToFlightVector." (Even though the class says that it's the second stage, it actually controls the entire rocket before...

At launch, the rocket is at 3.91 deg. The targeted orbital inclination is 3.92. (Currently the HUD interface is ripped off from F9R but I might have to replace it with an MFD like Themis-A if I can figure out how to get an MFD to interface with a specific type of vessel.) At first stage...

I just realized... When the VESSEL2 class is being used, the custom HUD text (using the "TextOut" function as described here) doesn't work with other rendering clients (e.g. D3D9). No wonder Themis-A uses an MFD for launch control... I'm also having some difficulties with getting the F9R's...

Actually, I messaged woo482 about it, and he told me how it works. for(int i= 0; i< PayloadCount; i++){ pldofs = PM_GetDistantVectorToPayload(i) ofs = pldofs -_V(0,0,cgdif); PM_SetSlotAttachmentParams(i,ofs,_V(0,0,1),_V(0,1,0)); } "Where 'cgdif'...

Nothing is wrong with that picture, that is how it is supposed to work. But with my rocket based on the F9R code, Payload Manager does not compensate the payload placement after a change in the location of the center of gravity. When Universal Cargo Deck (based on Payload Manager) is added...