boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 2,999
- Reaction score
- 1
- Points
- 0
I've had some time to test this and I have a few points:
1) I've always appreciated FOI's attention to detail so I've gone ahead and modified the default.ini files to include the payload adapter to those versions that lacked them. Also included is the spreadsheet that I used to calculate offsets. Payload masses have been adjusted accordingly. Does the dll take into account the adapter mass?
2) Now that this is a dll vessel free of multistage2 limitations, have you looked into the center of gravity? I believe that it is too far back on the upper stages. Moving it further forward might improve handling plus make the rotations look more realistic.
3) Once in orbit, the upper stages are not controllable by attitude MFD or pursuit MFD.
4) There is a situation that may arise regarding the autopilot and the orbital inclination. I will try to describe it the best that I can with an example:
Lets say you start at Cape Canaveral and launch toward a small inclination that is not quite due East, say +29 to +31 degrees, with a slightly northerly heading. You will launch a few degrees toward orbit normal from the prograde. Usually, this is fine. However, especially for heavily loaded 3+ stage Jarvis vehicles, it takes over ten minutes to get to to orbit. During that time you cross the point half-way between the ascending and descending node. When that happens, you need to change from slightly orbit normal to orbit ANTI-normal to continue increasing the inclination. Currently, the autopilot chases the inclination in the WRONG (orbit-normal) direction. This decreases the inclination instead of increasing it, which causes the autopilot to chase it more in the wrong direction which causes.....a feedback disaster.
Test: launch default Jarvis E from Cape Canaveral using the Default.ini that I have provided (payload > ~50 000 kg) with
Ap =250
Pe =250
INC = 29
1) I've always appreciated FOI's attention to detail so I've gone ahead and modified the default.ini files to include the payload adapter to those versions that lacked them. Also included is the spreadsheet that I used to calculate offsets. Payload masses have been adjusted accordingly. Does the dll take into account the adapter mass?
2) Now that this is a dll vessel free of multistage2 limitations, have you looked into the center of gravity? I believe that it is too far back on the upper stages. Moving it further forward might improve handling plus make the rotations look more realistic.
3) Once in orbit, the upper stages are not controllable by attitude MFD or pursuit MFD.
4) There is a situation that may arise regarding the autopilot and the orbital inclination. I will try to describe it the best that I can with an example:
Lets say you start at Cape Canaveral and launch toward a small inclination that is not quite due East, say +29 to +31 degrees, with a slightly northerly heading. You will launch a few degrees toward orbit normal from the prograde. Usually, this is fine. However, especially for heavily loaded 3+ stage Jarvis vehicles, it takes over ten minutes to get to to orbit. During that time you cross the point half-way between the ascending and descending node. When that happens, you need to change from slightly orbit normal to orbit ANTI-normal to continue increasing the inclination. Currently, the autopilot chases the inclination in the WRONG (orbit-normal) direction. This decreases the inclination instead of increasing it, which causes the autopilot to chase it more in the wrong direction which causes.....a feedback disaster.
Test: launch default Jarvis E from Cape Canaveral using the Default.ini that I have provided (payload > ~50 000 kg) with
Ap =250
Pe =250
INC = 29