Problem Breaking TransX

[Nemoricus]

BEGIN_DESC
Orbiter saved state at T = 197
END_DESC

BEGIN_ENVIRONMENT
  System Deepstar/Sol
  Date MJD 77586.1033079642
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Deepstar
END_FOCUS

BEGIN_CAMERA
  TARGET Deepstar
  MODE Cockpit
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE User
  MODE TransX
  Ship  Deepstar
  FNumber 1
  Int 0
  Orbit True
  Vector  -25285700841.1 -1494616277.67 7658088351.73
  Vector  6801.77037311 393.261108792 -2261.73117454
  Double  1.26686534397e+017
  Double  77586.1033057
  Handle Jupiter
  Handle NULL
  Handle NULL
Select Target
 0 None
Autoplan
0 0
Plan type
0 0
Plan
0 0
Plan
0 0
Plan
0 0
Select Minor
 0 None
Manoeuvre mode
0 0
Base Orbit
0 0
Prograde vel.
 0  0
Man. date
 0  77586.1033055
Outward vel.
 0  0
Ch. plane vel.
 0  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
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Frame
  FRAME Ecliptic
  ALT
  REF Jupiter
END_MFD


BEGIN_SHIPS
Deepstar:Deepstar/Deepstar
  STATUS Orbiting Sun
  RPOS 540738686312.28 -16164280959.18 489851644749.82
  RVEL -1839.292 541.967 8315.675
  AROT 3.73 12.45 4.33
  RCSMODE 2
  PRPLEVEL 0:0.890
  THLEVEL 2:0.009
  DOCKINFO 1:0,Deepstar-Lander-1 2:0,Deepstar-Lander-2
  IDS 0:522 100 1:524 100 2:526 100 3:528 100 4:530 100
  NAVFREQ 0 0
  XPDR 520
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -1 0.622621
  SEQ 1 -2 0.000000
  SEQ 2 -2 0.000000
  SEQ 3 -2 0.000000
  SEQ 4 -2 0.000000
  SEQ 5 -2 0.000000
END
Deepstar-Lander-1:Deepstar/Deepstar-Lander-1
  STATUS Orbiting Sun
  RPOS 540738686312.79 -16164280952.29 489851644749.48
  RVEL -1839.292 541.967 8315.675
  AROT 3.73 12.45 -175.67
  RCSMODE 0
  PRPLEVEL 0:0.999
  DOCKINFO 0:1,Deepstar
  IDS 0:542 100
  NAVFREQ 0 0
  XPDR 550
  RCS 0
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
END
Deepstar-Lander-2:Deepstar/Deepstar-Lander-2
  STATUS Orbiting Sun
  RPOS 540738686311.77 -16164280966.08 489851644750.16
  RVEL -1839.292 541.967 8315.675
  AROT 3.73 12.45 4.33
  RCSMODE 0
  PRPLEVEL 0:0.999
  DOCKINFO 0:2,Deepstar
  IDS 0:562 100
  NAVFREQ 0 0
  XPDR 550
  RCS 0
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
END
END_SHIPS

BEGIN_ExtMFD
END

BEGIN_StateVectorMFD
END

In this scenario, if I pull up TransX, set the Target to either Io or Europa and then start playing the date value in maneuver mode, TransX becomes unresponsive if I exceed a certain time into the future. The numbers are all replaced with readouts along the lines of #1.QS or something like that.

Does anyone have any idea why this is ocurring?

For the people who may use this scenario, it requires Deep Star 2.0.

 

[tblaxland]

...TransX becomes unresponsive if I exceed a certain time into the future. The numbers are all replaced with readouts along the lines of #1.QS or something like that.

More likely "1.#QNAN", ie, a Quiet Not a Number. That would indicate that there is a maths problem of some sort that results in an undefined value.

How far into the future?

EDIT: Do you get the same problem if you substitute a default Delta-Glider into the scenario?

 

[Nemoricus]

I haven't tried that.

After further investigation, it seems that the problem is centered around MJD 77622. I'm not sure if there's a specific time during that day that the problem occurs, but I think it's likely to be around the time of periapsis.

I also tried going forward in time, further into Jupiter's sphere of influence, which seemed to improve the date range problem. However, it still seems to have trouble around MJD 7622.

I also change the value for prograde velocity in Maneuver mode. While this itself doesn't cause any problems, it may be related.

I'll go see what happens if a Delta Glider is substituted.

EDIT: There appears to be no difference with a Delta Glider substituted.

BEGIN_DESC
Orbiter saved state at T = 197
END_DESC

BEGIN_ENVIRONMENT
  System Deepstar/Sol
  Date MJD 77586.1033079642
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Deepstar
END_FOCUS

BEGIN_CAMERA
  TARGET Deepstar
  MODE Cockpit
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE User
  MODE TransX
  Ship  Deepstar
  FNumber 1
  Int 0
  Orbit True
  Vector  -25285700841.1 -1494616277.67 7658088351.73
  Vector  6801.77037311 393.261108792 -2261.73117454
  Double  1.26686534397e+017
  Double  77586.1033057
  Handle Jupiter
  Handle NULL
  Handle NULL
Select Target
 0 None
Autoplan
0 0
Plan type
0 0
Plan
0 0
Plan
0 0
Plan
0 0
Select Minor
 0 None
Manoeuvre mode
0 0
Base Orbit
0 0
Prograde vel.
 0  0
Man. date
 0  77586.1033055
Outward vel.
 0  0
Ch. plane vel.
 0  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
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Frame
  FRAME Ecliptic
  ALT
  REF Jupiter
END_MFD


BEGIN_SHIPS
GL-01:DeltaGlider
  STATUS Orbiting Sun
  RPOS 540738686312.28 -16164280959.18 489851644749.82
  RVEL -1839.292 541.967 8315.675
  AROT 3.73 12.45 4.33
  PRPLEVEL 0:0.553 1:0.9
  NOSECONE 0 0.0000
  GEAR 0 0.0000
  AIRLOCK 0 0.0000
END
END_SHIPS

BEGIN_ExtMFD
END

BEGIN_StateVectorMFD
END

 

[agentgonzo]

Are you using the [ame="http://www.orbithangar.com/searchid.php?ID=3039"]latest version[/ame] of TransX? There were QNAN bugs in previous versions (and some probably still occur).

I don't have any time to spend bug fixing in TransX anymore I'm afraid, but if you are a coder and fancy trying to fix it, TransX is open-source

 

[Nemoricus]

I'm using TransX 3.13, so I'm not sure why this came up.

I'll look into the source code later, but is it possible that TransX divides by the difference between the maneuver time and the periapsis time at some point?