I finally got the booster meshes right.
Question:
Is there a method to influence the autopilot in the guidance file, aside from the initial line
orbit(200,400,38) ?
Yes, I understand what you mean.
But this "change" is calculated automatically by multistage, we can not modify it, or we have to make a guidance file "by hand" without the parameter "time=Orbit()"
I use "Orbit(PeA,ApA,Inc)"
and as you may have seen, the values entered in the guidance file are not the final values reached by the rocket... I had to test several values
But you have this (in the multistage doc):
Orbit(PeA,ApA,Inc,Mode,GravTurnPitch,Abside)
with :
GravTurnPitch is the initial gravity turn pitch in case automatic value is not satisfactory
It then starts wild pitchdown-pitchup maneuvers.
This can be avoided by switching to manual control after the initial roll-to-heading.
But it would be convenient to have an automated flight into orbit.
In the Multistage doc, we can read :
Therefore the computational calculated value usually works, but it is more a "suggested"
value, that can be later optimized by the user. In the orbit call of the guidance program users can set this
at their pleasure, in order to find the optimal value. I've made hundreds of tests about this, but since all
the rockets are different and the firing sequences are different it cannot be made completely closed to the
user inputs, and by specifying which is the "suggested" value the user can have an idea of which
value shall be used for that particular orbit. If the user does not input anything the guidance computer will
use the suggested value.
Please, read the Fred18's multistage doc, may be you can improve this step ?
I haven't tested this feature yet.
The mass and thrust values I left unchanged for now.
Will look up thrust and weight values next year.
I have the actual characteristics of the rocket, I will put the values here... when I get home
Wish you a Happy New Year!

Thank you, same for you... and every body !!!