OHM TransX 2018.05.06 MMExt2 for Orbiter 2016

Now the "Scale to View" is somehow changed from previous default...Mars orbit is very little.

zB6BDwj.png
 
Last edited:
I don't have this problem here. How to recreate it?
 
Maybe it's not "Scale to View", but I was able to replicate it anyway:
at the start of scenario, select Venus as target in Launch MFD, then open TransX.

This is the scenario (with an XR-2 to Venus):
Code: 
BEGIN_DESC
Sono le 22:00 del 28 dicembre 2000 (MJD 51906.916667) e siamo a Cape Canaveral, sulla pista 15 del Kennedy Space Center.

Domani si apre la nostra finestra di lancio per Venere. Faremo questo volo con l'aiuto del TransX.

Manca ancora qualche ora al decollo e devi attivare il raffreddamento esterno (External Cooling) dal pannello inferiore altrimenti il liquido di raffreddamento si surriscalderà. Devi spegnere anche l'APU. Ricordati di riattivarlo poco prima del decollo, e di portare i controlli atmosferici di volo "AF CTRL" su "ON".

Appena giunto in orbita (o comunque sopra i 100km di quota) apri il radiatore.
Buona missione!
END_DESC
BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51906.916667
END_ENVIRONMENT
BEGIN_FOCUS
  Ship XR2-VENERE
END_FOCUS
BEGIN_CAMERA
  TARGET XR2-VENERE
  MODE Cockpit
  FOV 40.00
END_CAMERA
BEGIN_HUD
  TYPE Surface
END_HUD
BEGIN_MFD Left
  TYPE OAlign
  REF Earth
  TARGET Venus
END_MFD
BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  FRAME Equator
  ALT
  REF Earth
END_MFD
BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
XR2-VENERE:XR2Ravenstar
  STATUS Landed Earth
  POS -80.705714 28.632274
  HEADING 150.00
  RCSMODE 0
  PRPLEVEL 0:1.000 1:1.000 2:1.000
  IDS 0:199 100
  NAVFREQ 588 466 84 114
  XPDR 193
  SECONDARY_HUD 3
  LAST_ACTIVE_SECONDARY_HUD 0
  ADCTRL_MODE 7
  TAKEOFF_LANDING_CALLOUTS 0.000000 0.000000 0.000000 0.000000 0.000000
  APU_FUEL_QTY 0.988
  LOX_QTY 0.999642
  CABIN_O2_LEVEL 0.209
  CREW_STATE 0
  INTERNAL_SYSTEMS_FAILURE 0
  COGSHIFT_MODES 0 0 0
  MWS_ACTIVE 0
  COOLANT_TEMP 32.435
  DMG_0 1.000000 Left Wing
  DMG_1 1.000000 Right Wing
  DMG_2 1.000000 Left Aileron
  DMG_3 1.000000 Right Aileron
  DMG_4 1.000000 Landing Gear
  DMG_5 1.000000 Nosecone
  DMG_6 1.000000 Retro Doors
  DMG_7 1.000000 Top Hatch
  DMG_8 1.000000 Radiator
  DMG_9 1.000000 Airbrake
  DMG_10 1.000000 Left Main Engine
  DMG_11 1.000000 Right Main Engine
  DMG_12 1.000000 Left SCRAM Engine
  DMG_13 1.000000 Right SCRAM Engine
  DMG_14 1.000000 Fore Hover Engine
  DMG_15 1.000000 Aft Hover Engine
  DMG_16 1.000000 Left Retro Engine
  DMG_17 1.000000 Right Retro Engine
  DMG_18 1.000000 Forward Lower RCS
  DMG_19 1.000000 Aft Upper RCS
  DMG_20 1.000000 Forward Upper RCS
  DMG_21 1.000000 Aft Lower RCS
  DMG_22 1.000000 Forward Star. RCS
  DMG_23 1.000000 Aft Port RCS
  DMG_24 1.000000 Forward Port RCS
  DMG_25 1.000000 Aft Star. RCS
  DMG_26 1.000000 Outboard Upper Port RCS
  DMG_27 1.000000 Outboard Lower Star. RCS
  DMG_28 1.000000 Outboard Upper Star. RCS
  DMG_29 1.000000 Outboard Lower Port RCS
  DMG_30 1.000000 Aft RCS
  DMG_31 1.000000 Forward RCS
  DMG_32 1.000000 Bay Doors
  IS_CRASHED 0
  MET_STARTING_MJD -1.000000
  INTERVAL1_ELAPSED_TIME -1.000000
  INTERVAL2_ELAPSED_TIME -1.000000
  MET_RUNNING 0
  INTERVAL1_RUNNING 0
  INTERVAL2_RUNNING 0
  ACTIVE_MDM 3
  TEMP_SCALE 2
  CUSTOM_AUTOPILOT_MODE 0
  AIRSPEED_HOLD_ENGAGED 0
  SCRAM0DIR 0.000000 0.000000 1.000000
  SCRAM1DIR 0.000000 0.000000 1.000000
  HOVER_BALANCE 0.000
  MAIN0DIR 0.000000 0.000000 1.000000
  MAIN1DIR 0.000000 0.000000 1.000000
  GIMBAL_BUTTON_STATES 0 0 0 0 0 0
  ATTITUDE_HOLD_DATA 0.000000 0.000000 0 0 0.000000
  DESCENT_HOLD_DATA 0.000000 -3.000000 0
  AIRSPEED_HOLD_DATA 0.000000
  OVERRIDE_INTERLOCKS 0 0
  TERTIARY_HUD_ON 1
  CREW_DISPLAY_INDEX 0
  GEAR 1 1.0000
  RCOVER 0 0.0000
  NOSECONE 0 0.0000
  AIRLOCK 0 0.0000
  IAIRLOCK 0 0.0000
  CHAMBER 0 0.0000
  AIRBRAKE 0 0.0000
  RADIATOR 0 0.0000
  HATCH 0 0.0000
  SCRAM_DOORS 0 0.0000
  HOVER_DOORS 0 0.0000
  BAY_DOORS 0 0.0000
  APU_STATUS 1
  EXTCOOLING_STATUS 0
  TRIM 0.000
  LIGHTS 0 0 0
  XRUMMU_CREW_DATA_VALID 1
  UMMUCREW XI0-Lee_Nash-39-65-78
  UMMUCREW XI1-Kara_Miller-32-65-58
  UMMUCREW XI2-Sharon_Valerii-26-67-54
  UMMUCREW XI3-Cameron_Mitchell-36-65-77
  UMMUCREW XI4-Samantha_Carter-33-66-53
  UMMUCREW XI5-Daniel_Jackson-35-68-75
  UMMUCREW XI6-Teal_c-31-64-104
  UMMUCREW XI7-Vala_Mal_Doran-30-67-53
  UMMUCREW XI8-Elizabeth_Weir-36-68-56
  UMMUCREW XI9-John_Sheppard-34-64-77
  UMMUCREW XI10-Rodney_McKay-35-72-90
  UMMUCREW XI11-Teyla_Emmagan-27-68-57
  UMMUCREW XI12-Ronon_Dex-32-63-97
  UMMUCREW XI13-Carson_Beckett-38-74-95
  PAYLOAD_SCREENS_DATA 0.2 0 1 1
END
XR2-VENERE_Bay:XRPayloadBay
  STATUS Landed Earth
  POS -80.7098293 28.6270272
  HEADING 149.98
  ATTACHED 0:3,XR2-VENERE
END
XR2PayloadCHM-01-1:XR2PayloadCHM
  STATUS Landed Earth
  POS -80.7098140 28.6270040
  HEADING 149.98
  ATTACHED 0:0,XR2-VENERE
  NAVFREQ 0 0
END
END_SHIPS


And this is the "XR2-VENERE.xrcfg" file

Code: 
#--------------------------------------------------------------------------
# Sample XR2 Ravenstar Configuration Override File
#
# This is an example of how to override any or all default XR configuration
# values for a given XR vessel.  Each XR vessel in a scenario file checks for 
# a corresponding .xrcfg file with the same name as the vessel name.  For example:
#
# In the scenario file:
#   XR2-EXAMPLE:XR2Ravenstar
#     STATUS Landed Earth
#     POS -80.683114 28.597734
#     ...
#
# On load, the vessel named "XR2-EXAMPLE" above will look for an override file
# named "Config\XR2-EXAMPLE.xrcfg".  If found, any values specified in the xrcfg
# file will override (replace) the default configuration values.  For more information,
# refer to the section titled "Configuring Your XR Vessel" in the XR Flight Operations
# Manual.  
#
# Any values altered will take effect immediately the next time a scenario is loaded.
#
# NOTE: any or all configuration settings present in the default XR configuation file may 
# also be specified in an override (.xrcfg) file.  The ones show below are just a few
# for the purpose of an example.  Here we modify the configuration for an Earth-to-Mars 
# trip: ISP and LOX, plus APU fuel burn rate for good measure.
#--------------------------------------------------------------------------

[GENERAL]

#--------------------------------------------------------------------------
# Main Fuel ISP ("Specific Impulse") setting.  This determines how much 
# main/hover/rcs fuel is burned each second for a given thrust level.
# Higher settings allow longer flights without refueling.  Remember to 
# update the 'LOXLoadout' value later in this file as well so the crew will
# have enough oxygen for the mission!
#
# NOTE: The 'Expert' setting (0) is tuned so that you will need to use your SCRAM engines
# efficiently during ascent to LEO ("Low Earth Orbit").
# ISP values for each level are shown in [brackets].
#   0 = Expert    (ISS Only w/expert use of SCRAM engines and expert deorbit/landing)  [13943]
#   1 = Realistic (ISS Only)                [20914]
#   2 = Default   (ISS and Moon)            [25962]
#   3 = Medium    (ISS and Moon w/reserve)  [32981]
#   4 = Stock DG  (Moon w/large reserve; this is the original stock DG setting)  [40000]
#   5 = Big       (Mars)                    [52922]
#   6 = Huge      (Jupiter+)                [366251]
#   7 = Massive   (Jupiter+ w/full payload) [476127]
#
# The default value is 2 (ISS and Moon).
#
# NOTE: You can also override this global setting for a given scenario by setting a value for it in your scenario file; 
#       Refer to the scenario file named "Configuration File Override Example 2.scn" for an example.
#--------------------------------------------------------------------------
MainFuelISP=5

#--------------------------------------------------------------------------
# LOX (Liquid Oxygen) loadout setting.  This determines the maximum duration of a mission without 
# replenishing the LOX tanks.  Times listed assume a full crew (14 crew members); reducing the 
# number of crew members will increase the maximum mission duration accordingly.
#
# Increasing this value will increase the LOX loaded into the ship.  The mass value
# displayed for each setting assumes a LOXConsumptionRate (the parameter following this one)
# of 4 (realistic: 100% of normal).  To reduce the LOX mass required for a long mission,
# leave LOXConsumptionRate set to its default value of -1 (AUTO), or set it it 0 (OFF) or 1 (very low).
#
# Valid options (duration assumes full crew of 14):
#   0 = 7 days          (  182 kg)
#   1 = 14 days         (  364 kg)
#   2 = one month       (  792 kg)
#   3 = three months    ( 2374 kg)
#   4 = six months      ( 4746 kg)
#   5 = one year        ( 9489 kg)
#   6 = two years       (18975 kg)
#   7 = three years     (28462 kg)
#   8 = four years      (37948 kg)
#   9 = five years      (47438 kg)
#
# The default value is 1 (14 days).
#--------------------------------------------------------------------------
LOXLoadout=5

#--------------------------------------------------------------------------
# APU Fuel Burn Rate : this is the rate at which APU fuel is burned in kg/sec.
# The Auxiliary Power Unit (APU) provides hydraulic power to the ship.
#   0 = unlimited : (runs indefinitely)
#   1 = very low  : 0.90718474 kg/minute (2 lb/minute)    (3.7 hours runtime)
#   2 = low       : 1.81436948 kg/minute (4 lb/minute)    (110 minutes runtime)
#   3 = moderate  : 2.72155422 kg/minute (6 lb/minute)    (74 minutes runtime)
#   4 = realistic : 4.08233134 kg/minute (9 lb/minute)    (49 minutes runtime)
#   5 = expert    : 6.12349701 kg/minute (13.5 lb/minute) (33 minutes runtime)
#
# The default value is 2 (low: 110 minutes runtime).
#
# NOTE: You can also override this global setting for a given scenario by setting a value for it in your scenario file; 
#       Refer to the scenario file named "Configuration File Override Example 2.scn" for an example.
#--------------------------------------------------------------------------
APUFuelBurnRate=1


###########################################################################
# END OF FILE
###########################################################################
 
Last edited:
OK, I have it. I don't know who broke it, but the DLL shipped with Orbiter doesn't have the problem. I'll investigate it on the next weekend.
BTW, you do know that how you want to launch isn't the best technique around? You should rather pass the incl and LAN to Launch MFD from the Escape Plan.

For the record, here's a minimized scenario:
Code: 
BEGIN_DESC
Select Venus in Launch MFD, then open TransX and choose Escape
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51906.9167783448
END_ENVIRONMENT

BEGIN_FOCUS
  Ship GL-01
END_FOCUS

BEGIN_CAMERA
  TARGET GL-01
  MODE Cockpit
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE OAlign
  REF Earth
  TARGET Venus
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  FRAME Equator
  ALT
  REF Earth
END_MFD

BEGIN_SHIPS
GL-01:DeltaGlider
  STATUS Landed Earth
  POS -80.7057140 28.6322740
  HEADING 150.00
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 402 94 0 0
  XPDR 0
  GEAR 1 1.0000
  AAP 0:0 0:0 0:0
END
END_SHIPS
 
Enjo said:
OK, I have it. I don't know who broke it, but the DLL shipped with Orbiter doesn't have the problem. I'll investigate it on the next weekend.
Click to expand...
Cool thanks!

Enjo said:
BTW, you do know that how you want to launch isn't the best technique around? You should rather pass the incl and LAN to Launch MFD from the Escape Plan.
Click to expand...
Yes I know, I'm still learning...errr...bug-hunting!
In fact I don't know why I opened LaunchMFD first. It was maybe the Probe who guided my bug-hunting finger.
:tiphat:
 
orb said:
Don't put them there. That's the reason for the error. Delete them and install vcredist_x86.EXE from this page instead.
Click to expand...

I tried in a clean Orbiter and it doesn't work, but I'll try this, anyway.

---------- Post added at 01:00 AM ---------- Previous post was at 12:40 AM ----------

EDIT: ok, it's working after vcredist_x86 installation. Thanks orb and Enjo!
 
hello,
Thanks for all improvements on TransferX known as TransX.
I use TransX with two vessels : Arrow Freighter and Delta Glider IV (last upgrades).

I have noticed a problem on my vessels after the use of the Auto-Center™ function (a perfect tool), when making the mid-course orbital correction from Earth to Mars :

- autopilots programs (Prograde, Retrograde etc) did not work on both vessels.
Before the mid-course correction : all was ok and after : autopilots did not responde.

I have saved the scenario, going out Orbiter, open again the scenario and then autopilots work !
I do not know why because it is not a CTD, only the autopilots of vessels are out of order after mid-course correction with Auto-Center™.
 
Last edited:
Thanks for the feedback and report.
Before I have a chance to test it during the weekend, maybe it's a silly question, but did you actually disable the Auto-Center function before enabling other APs? If you did, then I believe that we can say that these addons are incompatible for now, and I will have to resolve the issue with Dan.
 
hello,
I have tested again Auto-Center™ function with vessel DGIV for a mid-course correction :
using Auto-center function perfectly (with View button), I pushed again the View button to go back to Stage 1.

Then :
Auto-center : OFF
Manoeuvre Mode : OFF.

After :
I tryed to enable autopilots (Prograde, Retrograde, etc) and I saw all are out of order for this vessel. It is not possible to activate autopilots, even with the keyboard.

A previous version of Transx (TransX-2013.12.13-auto-min) seems to avoid my issue with autopilots. Anyone can confirm or it's only me ?
 
Last edited:
Leospace said:
using Auto-center function perfectly (with View button), I pushed again the View button to go back to Stage 1.
Then :
Auto-center : OFF
Click to expand...
I see now.
You need to disable the Auto-Center while still being IN the Target View. TransX' limitation. Sorry.
 
Thanks a lot Enjo !
All is ok now when I disable the Auto-center function inside the Target View. :thumbup:
 
EDIT: Nevermind. I'm just stupid :D
EDIT #2: Works perfectly! The Autocenter function is REALLY helpful. I always struggled with the alignment of the crosshair. Awesome work! THANKS!
 
Last edited:
Can someone explain how to properly use the Auto-Min function? I tried using it but it doesn't seem to minimize the closest approach, it actually makes it larger.
 
First set all the variables, except the ejection MJD, to AutoMin.
Set the Ejection MJD to fine and slowly move forward. You should see the closest approach coming down.

Once you get a reasonably good launch window, set Ejection MJD to AutoMin
and tweak it further.
 
Castor said:
First set all the variables, except the ejection MJD, to AutoMin.
Click to expand...
It turns out that in practice it make sense only to set Prograde and ChangePlane velocities to AutoMin, and leave the Outward vel as 0. Then proceed as Castor described.
 
Thank you for both of your replies, I read the documentation on the Auto-Min function, but did not quite understand. I am currently flying the messenger mission and it is very complex (many gravity assists), so the Auto-Min function does help tremendously. Thank you guys for your help.
 
That's nice to hear, because I was afraid that the Auto-Min feature was just a toy, or poor man's way to reach a planet fast.
 
Enjo said:
That's nice to hear, because I was afraid that the Auto-Min feature was just a toy, or poor man's way to reach a planet fast.
Click to expand...

No, it is far from that. The Auto-Min feature lets you try 1,000's of variations per minute by only changing the MJD. Without the Auto-Min feature, you have to change all 3 velocities + the date variable, write down your results, then change all 3 variables again + the date, and write that result down, and repeat the process until you're happy. It is ridiculously time consuming.

Auto-Min is a Godsend!
 
Auto-Centre Bug

Firstly I'd like to thank you for releasing a much improved TransX, but I've noticed a bug when using the auto-center feature.
If you were to eject from any planetary orbit for a heading to another planet and you're half way you need to do a course correction. For this I used the auto-center feature by turning it on before the burn and then off after the burn followed by turning maneuver mode off as well.
This looks good but when you go into time acceleration, the craft wobbles ridiculously and the RCS engines kick in automatically (in Arrow-Freighter and DGIV-3 at least) to correct wobble which uses up all my fuel. The only way of getting to my other planet after using this would be to wait in real time (not going to happen) or use the scenario editor to keep refilling my tanks before every maneuver (not fun).
What makes this worse is that it affects all other vessels as well causing them to want to face the direction of my last maneuver, which stops my pro-retro-+norm--norm etc... autopilots from working.
 
You must log in or register to reply here.

Similar threads

OrbitHangar
OHM TransX 2018.04.05 MMExt2 for Orbiter 2010
Replies
1
Views
3K
jgrillo2002
jgrillo2002
OrbitHangar
OHM Launch MFD - v. 1.6.5 for Orbiter 2010
Replies
0
Views
2K
OrbitHangar
OrbitHangar
K
Optimal Earth-Venus-Mercury transfer - PyKEP / PyGMO
Replies
6
Views
7K
Keithth G
K
OrbitHangar
OHM Launch MFD - v. 1.6.6 for Orbiter 2016
11 12 13
Replies
243
Views
133K
CafuneAndChill
C
OrbitHangar
OHM Launch MFD - v. 1.6.2 for Orbiter 2006
Replies
3
Views
5K
Enjo
Enjo
Back
Top