OHM Jarvis 3.0 Dll Version - Final Beta

[boogabooga]

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

 

[fred18]

No, happens regardless of the launch site. Same result every time.

I would try o deactivate UMMUFA and Attachment manager and see if it happens anyway!

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?

Thank you VERY MUCH for your work and help! The adapter mass should be included in the payload file adding it to the payload mass.
example:
I have a payload of 1000 kg and an adapter of 200 kg, in the payload file I will put MASS=1200.

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.

I recently noticed it as well and found out that the command ShiftCG in c++ doesn't work well, will fix it for the final release. Thank you

3) Once in orbit, the upper stages are not controllable by attitude MFD or pursuit MFD.

That is for number 2), it will be fixed once the COG issue will be fixed

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:

that is another aspect of what asbjos pointed out a couple of posts up. This happens because of the ambiguity of the heading equation for azimuth close to 90°. You're right that it happens when crossing the ascending/descending node, you got exactly the point, congratulations :thumbup:
This is because for the time being the equations is forced to a solution only for azimuth=90° while it is left to ambiguity for the situation you pointed out. I will work on the complete solution of the equation for the final release, I wrongly thought it was not a big deal, but now i realize it needs a solution!

:tiphat::tiphat: THANK YOU VERY MUCH for your help, suggestions and collaboration, it's really precious!

 

[boogabooga]

Another small point:

The idea of launch delays is good, but perhaps the "launch window" needs to be configured in the .scn file. Three minutes is arbitrary. Launch windows to the ISS might be less than that, while launch windows to the moon might be three hours.


Also, perhaps there should be a flag in the .scn to disable failures?

 

[boogabooga]

Okay, I adapted (and slightly modified) the KH-11 mission for use with Jarvis dll.

I moved the pad (actually the launcher itself) at Vandenberg with 4th rock's stock bases upgrade ([ame="http://www.orbithangar.com/searchid.php?ID=6007"]Orbiter stock bases upgrade[/ame]) in mind.

You may need to move your pad if using one of the other Vandenberg add-ons.

 

[fred18]

Another small point:

The idea of launch delays is good, but perhaps the "launch window" needs to be configured in the .scn file. Three minutes is arbitrary. Launch windows to the ISS might be less than that, while launch windows to the moon might be three hours.


Also, perhaps there should be a flag in the .scn to disable failures?

I agree with you about the launch window. The point was that figure out how to make it work and implementing it took a while, and before going in too complicated issues I wanted to be sure that the system as I thought it was actually working.

Now that the feedbacks are good I will work for the final implementation of it, with a customizable launch window!

About disabling launch delays I will put an option in the scn, anyway for the time being you can set in failures.cfg the parameter COUNTDOWN_STOP=0

Thanks again for your help and suggestions!

 

[Cras]

I would try o deactivate UMMUFA and Attachment manager and see if it happens anyway!

As you saw in my log I have quite a bit of MFDs and plug ins running so it will take some time to disable and enable them to find out which one is not playing nice with your new Jarvis.

Ill let you know how it goes.

 

[K_Jameson]

Well, would be the case to take in account your results only when you'll try the Jarvis in a clean Orbiter installation. Otherwise, your bug segnalations could be false positive.

 

[Cras]

Well, would be the case to take in account your results only when you'll try the Jarvis in a clean Orbiter installation. Otherwise, your bug segnalations could be false positive.

Fair enough but if Jarvis .dll wont work with certain MFDs or what not, while other addons behave perfectly fine with them, then it becomes a compatibility issue and is not a by product of some mess of an orbiter install.

 

[K_Jameson]

Agreed, but, IMHO, the first goal for the team is to ensure compatibility with base Orbiter FIRST. And then to go forward and try with third-party MFD and other stuff commonly used. And for fullfill that goal, the first move is always the same: try the package with a fresh and clean copy of the simulator, only with the addons strictly required. Don't get me wrong: i won't make a flame for this. :tiphat:

 

[boogabooga]

If it hasn't been mentioned before, I believe the fourth stage of the Jarvis-C is overpowered by a factor of 10.

(~1.1MN vs. ~110kN for RL-10)

 

[fred18]

Thanks buddy, I'll give it a look this week!
:tiphat:

 

[romanasul]

Yeah boogabooga is right, that third stage has a load of power. The engines had to throttle back right after being started because they hit the payload limit of 5G's

 

[fred18]

"a 0 is only a 0, it has no value" "it depends on where you put it..."

looks like I added a zero at the end of the thrust of the third stage of JC, will correct in next release, thanks for noticing! :tiphat:

 

[wingnut]

Thank you for this addon which is easy to use and has comprehensive documentation.

I noticed something in conjunction with TransX and I am not sure whether to post this in the TransX thread or here: Did anyone else experience TransX plans not getting restored correctly with this?

I can't pin-point what exactly causes my TransX plans not to get reloaded properly when it was saved on a Jarvis vessel and the scenario is loaded again. Sometimes the stages in the plan are restored but not their variables I've entered before. This mostly happens with plans stored while the Jarvis launcher is still on the launchpad before lift-off.

In the following on-orbit scenario for example, I noticed that the TransX MFD section contains two ship variables - likely caused by the separation of Jarvi's second stage:

(ChapmanModules and LaunchMFD elements are included in this scenario)

When the line Ship Js2 is removed from the scenario file, the TransX plan is restored correctly.

BEGIN_DESC
Earth departure burn complete
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 50551.7936997314
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Jarvis_E
END_FOCUS

BEGIN_CAMERA
  TARGET Jarvis_E
  MODE Cockpit
  FOV 60.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE User
  MODE TransX
[B][COLOR="Red"]  Ship  Js2
  Ship  Jarvis_E[/COLOR][/B]
  FNumber 6
  Int 1
  Orbit True
  Vector  4351977.74368 -4458494.03966 2090218.26816
  Vector  -2028.40053968 1485.8878949 7404.08689059
  Double  3.98600439969e+014
  Double  50551.5126325
  Handle Earth
  Handle NULL
  Handle NULL
Select Target
 0 Escape
Autoplan
0 0
Plan type
0 0
Plan
0 1
Plan
0 0
Plan
0 0
Select Minor
 0 None
Manoeuvre mode
0 1
Auto-Center™
0 0
Base Orbit
0 0
Prograde vel.
 5  6788.63896826
Man. date
 7  50551.791083
Outward vel.
 4  -251.63
Ch. plane vel.
 4  192.75
Intercept with
0 0
Orbits to Icept
0 0
Graph projection
0 3
Scale to view
0 0
Advanced
0 0
Pe Distance
 1  6572000
Ej Orientation
 1  0.69115038379
Equatorial view
0 0
Finvars
  Finish BaseFunction
  Int 2
  Orbit True
  Vector  -137149682870 7405902.16185 -60895539112
  Vector  15870.5174547 -3861.53482823 -34909.531615
  Double  1.32712838556e+020
  Double  50551.7912095
  Handle Sun
  Handle Earth
  Handle Jupiter
Select Target
 0 Jupiter
Autoplan
0 0
Plan type
0 2
Plan
0 0
Plan
0 0
Plan
0 1
Select Minor
 0 None
Manoeuvre mode
0 0
Auto-Center™
0 0
Base Orbit
0 0
Prograde vel.
 1  0
Man. date
 1  50551.7931241
Outward vel.
 1  0
Ch. plane vel.
 1  0
Intercept with
0 0
Orbits to Icept
0 0
Graph projection
0 0
Scale to view
0 0
Advanced
0 0
Prograde vel.
 1  0
Eject date
 1  50551.7672991
Outward vel.
 1  0
Ch. plane vel.
 1  0
Finvars
  Finish BaseFunction
  Int 4
  Orbit True
  Vector  -332076193028 -44401754366.6 333396188409
  Vector  4986.80545687 673.144431271 -5058.3418854
  Double  1.26686534397e+017
  Double  50502.785485
  Handle Jupiter
  Handle NULL
  Handle NULL
Select Target
 0 Escape
Autoplan
0 0
Plan type
0 1
Plan
0 0
Plan
0 1
Plan
0 0
Select Minor
 0 None
Manoeuvre mode
0 0
Auto-Center™
0 0
Base Orbit
0 0
Prograde vel.
 1  0
Man. date
 1  50551.7932009
Outward vel.
 1  0
Ch. plane vel.
 1  0
Intercept with
0 0
Orbits to Icept
0 0
Graph projection
0 0
Scale to view
0 0
Advanced
0 0
View Orbit
0 0
Finvars
  Finish BaseFunction
  Int 3
  Orbit True
  Vector  743641132637 -17057443224.1 128223100401
  Vector  2530.32788323 -577.457079373 18584.5950141
  Double  1.32839126489e+020
  Double  51254.6673357
  Handle Sun
  Handle Jupiter
  Handle Saturn
Select Target
 0 Saturn
Autoplan
0 0
Plan type
0 2
Plan
0 0
Plan
0 0
Plan
0 2
Select Minor
 0 None
Manoeuvre mode
0 0
Auto-Center™
0 0
Base Orbit
0 0
Prograde vel.
 1  0
Man. date
 1  50551.7029336
Outward vel.
 1  0
Ch. plane vel.
 1  0
Intercept with
0 0
Orbits to Icept
0 0
Graph projection
0 0
Scale to view
0 0
Advanced
0 0
Velocity.
 1  0
Outward angle
 5  0.943746126845
Inc. angle
 5  0.0597320785071
Inherit Vel.
0 0
Eject date
 1  51254.6673357
Finvars
  Finish BaseFunction
  Int 0
  Orbit True
  Vector  -242608794246 30962810096 -481422961467
  Vector  4533.72689755 -570.689831523 8978.11328357
  Double  3.79311866084e+016
  Double  51433.9096304
  Handle Saturn
  Handle NULL
  Handle Titan
Select Target
 0 Titan
Autoplan
0 0
Plan type
0 1
Plan
0 0
Plan
0 0
Plan
0 0
Select Minor
 0 None
Manoeuvre mode
0 0
Auto-Center™
0 0
Base Orbit
0 0
Prograde vel.
 1  0
Man. date
 1  50551.5260292
Outward vel.
 1  0
Ch. plane vel.
 1  0
Intercept with
0 0
Orbits to Icept
0 0
Graph projection
0 0
Scale to view
0 0
Advanced
0 0
Finvars
  Finish BaseFunction
  Int 5
  Orbit True
  Vector  12818967.9217 269758959.79 -335059376.955
  Vector  86.4780500774 -8327.51118391 9041.45160736
  Double  9.0079965e+012
  Double  52052.6167079
  Handle Titan
  Handle NULL
  Handle NULL
Select Target
 0 None
Autoplan
0 0
Plan type
0 1
Plan
0 0
Plan
0 2
Plan
0 0
Select Minor
 0 None
Manoeuvre mode
0 0
Auto-Center™
0 0
Base Orbit
0 0
Prograde vel.
 1  0
Man. date
 1  50551.5260192
Outward vel.
 1  0
Ch. plane vel.
 1  0
Intercept with
0 0
Orbits to Icept
0 0
Graph projection
0 0
Scale to view
0 0
Advanced
0 0
Draw Base
0 0
Finvars
  Finish BaseFunction
END_MFD

BEGIN_MFD Right
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference jupiter
  Target none
  Center jupiter
  Data 0 1 2.094925687705891e-007 1 1 1 0 0 1 0 0 0
  MassLimit 1e+020
  CMode 0
  Config 1 1 1 1 0 0
  ExtMode 0
  Periapis Earth
  END 
  CorMFD V4
  Reference Earth
  Target Ecliptic
  Source Jarvis_E
  ActiveProg 5 5
  DataA 1 3 0 0 0 0
  DataB 1 1 50551.79058960998 0 0 0 0 0 0
  DVProg 6789 192.7 251.6 1
  AdvConf 0 0 0 0 0
  Guidance 0
  END 
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 1 50551.57180487293 10
  Guidance 0
  END 
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 50551.57180487293 50551.57180487293 0
  DataB 0 3 0 1 0 1
  END 
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 50551.57180487293 0
  END 
  LaunchMFD V4
  Target None
  Data 0 1 1 3 0 1 0
  END 
  CF1_DataA 0 0
  CF1_DataB 50548.3029768744 10 120000 2 20 150000
  CF1_SecTgt 
  mfdShare -1
  mfdProgram 4
END_MFD

BEGIN_SHIPS
Jarvis_E:JARVIS/Jarvis_E
  STATUS Orbiting Earth
  RPOS -3808246.99 4033604.48 -4581140.74
  RVEL 3940.698 -3230.516 -13239.767
  AROT -162.94 -27.25 -108.26
  RCSMODE 0
  AFCMODE 7
  PRPLEVEL 0:0.057719
  NAVFREQ 0 0 0 0
  XPDR 0
  FAIRINGON 0
  STAGE 2
  PRPLEVEL 2:0.057719
  PLNUM 0
  GLIMIT 5.000000
  GTVACC 6.000000
  TGT_APOGEE 200000.000000
  TGT_PERIGEE 200000.000000
  TGT_INC -44.840000
  AP 100
  MET 414.504258
  PAYLOAD_FILE Jarvis_E\Chapman.ini
END
PadJa:JARVIS\PadJa
  STATUS Landed Earth
  POS -80.6312150 28.5419000
  HEADING 90.00
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0 0 0
  XPDR 0
  ANIM_0 2 1.0000
  ANIM_1 2 1.0000
  ANIM_2 -2 0.0000
  ANIM_3 2 1.0000
END
LaunchMFD-Probe-Jarvis_E:LaunchMFD-Probe
  STATUS Orbiting Earth
  RPOS 3967082.82 -3007705.56 -4932504.71
  RVEL 3559.012 -4007.206 5305.914
  AROT 39.19 32.36 12.86
  AFCMODE 7
  NAVFREQ 0 0
END
Js2:JARVIS\Jarvis_s2
  STATUS Orbiting Earth
  RPOS -4096156.32 4275379.48 -3082929.48
  RVEL 2777.695 -2270.095 -6810.340
  AROT -76.17 53.25 32.47
  VROT 0.19 0.14 0.02
  AFCMODE 7
  NAVFREQ 0 0 0 0
  XPDR 0
END
END_SHIPS

BEGIN_ExtMFD
END

 

[fred18]

Thanks for pointing this out. I never had this issue. It seems exactly related to the jarvis staging. Anyway the staging is executed as per oapi standards: delete the mesh and spawn the depleted stage module.

I don't know if other multistage vehicles experience the same issue? maybe the transx guys can help us a bit on this!

 

[wingnut]

I don't know if other multistage vehicles experience the same issue? maybe the transx guys can help us a bit on this!

I tried with the Ariane 5 but it did not happen there even after manually staging which seemed to be trigger for the problem with Jarvis.

I could try to do some more tests as I am not sure how exactly to reproduce which case and eventually ask in the TransX development thread, too.

 

[Interceptor]

Hi Fred18,is there anyway to change the headings on the launch pads?the reason I am asking is I still use the pad lights that came with the ASVI pads,and some of them don't line up properly,unless you turn the pad launch tower 180 degrees,could maybe a future version have a feature to be able to change the heading for the pads in the scenario file,or just a fix to put the lights in the right position.Thanks

 

[Napalm42]

I don't think I've seen someone post the issue, but I've been encountering some odd behavior from the autopilot the past few launches.

Normally the scenario starts with the AP running and executes no problem, the issue I'm having is that about 50% of the time, the autopilot simply fails to run without any sort of crash or error (Enter scenario, countdown frozen, nothing happens). I know for a fact that the Jarvis can make it to my desired orbit, because I tested it manually to see if that would be a cause, but it had more than enough fuel.

I'm wondering if this is that failure config? If so, then it should probably print an error to the HUD saying "launch scrubbed" or something.

 

[fred18]

Hi Fred18,is there anyway to change the headings on the launch pads?the reason I am asking is I still use the pad lights that came with the ASVI pads,and some of them don't line up properly,unless you turn the pad launch tower 180 degrees,could maybe a future version have a feature to be able to change the heading for the pads in the scenario file,or just a fix to put the lights in the right position.Thanks

Will check!!! Thank you!

In the meantime, you can do two things: open the scenario you want, save it and then manually edit the lpad heading or (easier) open the scenario editor and edit the launchpad heading. The jarvis is attached to the launchpad so everything will move accordingly!

I don't think I've seen someone post the issue, but I've been encountering some odd behavior from the autopilot the past few launches.

Normally the scenario starts with the AP running and executes no problem, the issue I'm having is that about 50% of the time, the autopilot simply fails to run without any sort of crash or error (Enter scenario, countdown frozen, nothing happens). I know for a fact that the Jarvis can make it to my desired orbit, because I tested it manually to see if that would be a cause, but it had more than enough fuel.

I'm wondering if this is that failure config? If so, then it should probably print an error to the HUD saying "launch scrubbed" or something.

I'm not sure i well understood what the issue is, the countdown is stopped and the launch does not happen? What does the launch window says? Could you post the scenario file that you are running please?

 

[Interceptor]

Hi fred18,yeah I chose option 3 in the scenario to move the jarvis to the new pad position,and everything is moved correctly,but now I am not getting the pad effects at take off,I only get the effects on the Jarvis rocket.Thanks

---------- Post added at 09:54 AM ---------- Previous post was at 09:18 AM ----------

Hi fred18,yeah I chose option 3 in the scenario to move the jarvis to the new pad position,and everything is moved correctly,but now I am not getting the pad effects at take off,I only get the effects on the Jarvis rocket.Thanks

OK fred18,your suggestions seem to work,all is well.Thanks again.:lol:

---------- Post added at 10:50 AM ---------- Previous post was at 09:54 AM ----------

Nope,sorry I am still not getting the pad smoke effects.