Spontaneous target orbit change

[varsass]

Hi, I got a quite problematic problem when I try some docking :

Step 1 set the target (properly orbiting at 150km) :

Step 2 lift off :

Step 3 climb little rocket climb ! :

Step 4 Final burn not so far from the target :

Step 5 target reach the 5km limit and becomes visible and BANG :

It seems the target speed automatically matches the rocket speed when coming closer that 5 Km

OK I can still dock my pod it's not a real docking problem, but after the docking everybody's going to die

outpout_log.txt : here (flight start a line 154 334, yes it's pretty big)

Mod list :

- Module Manager 2.5.1

- ActiveStruts 1.0.3

- ATM

- B9 R5.2.6

- Bahamuto Armory 0.6.1.2

- Cage system 1.1

- DeadlyReentry 6.2

- DistantObject 1.3.1

- EngineerRedux 0.6.2.11

- Visual Enhancement 7.4

- Eploration Pack 0.2.2

- FAR 0.14.3.2

- FTT 0.2.2

- Habitat Pack

- HoolignaLabs 3.0.0

- Karbonite 0.4.2

- Joint Reinforcement 2.4.4

- kOS 0.14.2

- K+ 0.2.2

- SelectRoot

- KW Rocketry 2.6

- Infernal Robotics 0.19.2

- MechJeb 2.4.0

- MechJebFARExt

- MKS 0.21.2

- Procedural Wings 0.9.1

- Procedural Fairing 3.10

- RasterPropMonitor 0.18.3

- RealChute 1.2.5.3

- Retro Future Plane 1.6.2

- SCANsat 8.0

- Station Parts Expansion 0.2.0

- Statio Science 1.3.1

- Toolbar 1.7.7

- TweakableEverything 1.4.1

- TweakScale 1.44

If someone aldready had that problem and found how to fix it, please share !

If I'm the first one, I'll just try to reinstall all those mods one by one, and see what happens.

I'm running KSP 32bits openGL

Edited November 8, 2014 by varsass
more info

[Padishar]

Can you explain what the actual problem is a bit better? Is it that your projected orbit suddenly changes or does something else happen? In the last picture you are only doing 106 m/s different speed to your target so you shouldn't have 440m/s+ left on the manoeuver node that is supposed to give you a similar orbit. I would suggest simply ignoring the manoeuver node (delete it) and burn target retrograde to slow down and rendezvous normally though you seem to be implying that you can still dock but after docking everybody will die. Why? What happens?

[Diazo]

As I understand the issue, the 440m/s on the maneuver node was correct when setup.

Then the target reached 5km away and all of a sudden 300m/s of delta v just vanishes as the target (which is non-focused with engines off) matches speed to the controlled vessel.

As the current vessel had not reached orbital speed yet, both craft are now on a reentry trajectory and their is not enough delta v left to get both craft back into orbit.

Having said that, I have no clue what could cause that. I don't recognize all the mods you have installed, but I don't see anything messing with the physics and/or timewarp that would be my first suspect.

D.

[Padishar]

Right, I see, the target started off with 145/155 orbit and suddenly changed to -313/147. That is very strange though I have seen similar things reported before. Did it correspond with when the navball changed from orbit to target mode or did you do that manually at some point?

Another slightly strange thing is that MJ is reporting two slightly different orbits for the current vessel. In the rendezvous window it says -251/150 and in the orbit info display it says -253.3/150.

Looking at the log, there are a number of issues...

PlanetShine is giving an exception during startup (line 1098)

There is a FAR related exception during loading (line 67946)

MechJeb's FAR extension is failing to access FAR because it is trying to use FAR 0.14.2 and you have a later version (line 150694)

Toolbar is doing something iffy with its GUI (line 150860)

DistantObjectEnhancement is doing something wrong when loading in the flight scene (line 151109)

MechJebFARExt gives the same problem twice more (lines 152442 and 156823)

There is a suspicious looking message "dT is NaN! tA: 0.817919731140137, E: 0, M: 0, T: NaN" indicating something is probably badly confused (line 156969)

I would suggest finding out what is wrong with FAR (if anything), updating MechJebFARExt to a version that works with the version of FAR you have and removing DistantObjectEnhancement.

[varsass]

MechJeb's FAR extension is failing to access FAR because it is trying to use FAR 0.14.2 and you have a later version (line 150694)

I've updated MechJebFARExt, removed/reinstall mechjeb and FAR, removed rasterprop, but the problem is still here.

Thanks for replying, I keep searching

Edited November 8, 2014 by varsass

[Padishar]

I've updated MechJebFARExt, removed/reinstall mechjeb and FAR, removed rasterprop, but the problem is still here.

Thanks for replying, I keep searching

Can you try removing DistantObjectEnhancement?

[varsass]

Just tried without Distant Object and Planet Shine, now RasterProp seems angry :

[LOG 22:15:33.112] getObtAtUT result is NaN! UT: Infinity
[LOG 22:15:33.112] getObtAtUT result is NaN! UT: Infinity
[EXC 22:15:33.113] ArithmeticException: NAN
	System.Math.Sign (Double value)
	Orbit.solveEccentricAnomalyExtremeEcc (Double M, Double ecc, Int32 iterations)
	Orbit.getRelativePositionAtT (Double T)
	Orbit.getPositionAtT (Double T)
	Orbit.getPositionAtUT (Double UT)
	JSI.JUtil.MinTargetDistance (.Orbit vesselOrbit, System.Func`2 targetOrbit, Double startTime, Double endTime, System.Double& timeAtClosestApproach)
	JSI.JUtil.MinTargetDistance (.Orbit vesselOrbit, .Orbit targetOrbit, Double startTime, Double endTime, System.Double& timeAtClosestApproach)
	JSI.JUtil.GetClosestApproach (.Orbit vesselOrbit, .Orbit targetOrbit, System.Double& timeAtClosestApproach)
	JSI.RasterPropMonitorComputer.UpdateTransferAngles ()
	JSI.RasterPropMonitorComputer.OnUpdate ()
	Part.ModulesOnUpdate ()
	Part.Update ()
[LOG 22:15:33.117] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - -Infinity
[LOG 22:15:33.118] dT is NaN! tA: NaN, E: 3.14159265358979, M: -8.40714670366795, T: -Infinity
[LOG 22:15:33.118] dT is NaN! tA: NaN, E: 3.14159265358979, M: -8.40714670366795, T: -Infinity
[LOG 22:15:33.119] getObtAtUT result is NaN! UT: NaN
[LOG 22:15:33.119] getObtAtUT result is NaN! UT: NaN
[LOG 22:15:33.120] getObtAtUT result is NaN! UT: NaN
[LOG 22:15:33.120] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - NaN
[LOG 22:15:33.121] getObtAtUT result is NaN! UT: NaN
[LOG 22:15:33.121] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - NaN
[LOG 22:15:33.155] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - NaN

I'll try again without Raster Prop, with full logs if nothing changes.

Edit :

Same problem without RasterProp :

[LOG 22:41:27.996] [Rendezvous]: Now tracking Docking-test vs. Docking-test 2
[LOG 22:41:27.996] [Rendezvous]: Tracking Docking-test vs. Docking-test 2 ended.
[LOG 22:41:28.055] Parsing vector2
[LOG 22:41:28.058] Parsing vector2
[LOG 22:41:28.060] Parsing vector2
[LOG 22:41:28.119] Parsing string
[LOG 22:41:28.119] Parsing vector2
[LOG 22:41:28.122] Parsing string
[LOG 22:41:28.122] Parsing vector2
[LOG 22:41:28.124] Parsing string
[LOG 22:41:28.125] Parsing vector2
[LOG 22:41:28.127] Parsing string
[LOG 22:41:28.127] Parsing vector2
[LOG 22:41:28.130] Parsing string
[LOG 22:41:28.130] Parsing vector2
[LOG 22:41:28.227] [MechJeb2] MechJebFARExt adding MJ2 callback
[LOG 22:41:28.261] Parsing vector2
[LOG 22:41:28.883] Parsing vector2
[LOG 22:41:28.894] Unpacking Docking-test
[LOG 22:41:29.043] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - -0.0056878911095079
[LOG 22:41:29.044] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - -0.0056878911095079
[LOG 22:41:29.139] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - -Infinity
[LOG 22:41:29.139] dT is NaN! tA: NaN, E: 3.14159265358979, M: -8.40714670366795, T: -Infinity
[LOG 22:41:29.140] dT is NaN! tA: NaN, E: 3.14159265358979, M: -8.40714670366795, T: -Infinity
[LOG 22:41:29.140] getObtAtUT result is NaN! UT: NaN
[LOG 22:41:29.141] getObtAtUT result is NaN! UT: NaN
[LOG 22:41:29.141] getObtAtUT result is NaN! UT: NaN
[LOG 22:41:29.142] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - NaN
[LOG 22:41:29.142] getObtAtUT result is NaN! UT: NaN
[LOG 22:41:29.143] problem! 
[NaN, NaN, NaN]  -  [NaN, NaN, NaN]  -  NaN  -  [NaN, NaN, NaN] - NaN
[LOG 22:41:29.178] problem! 

output_log.txt

Flight starts line 177404

Problem starts line 359100

KSP.log

Flight starts line 60031

Problem starts line 186939

And now it's worse, the target completely disappear

Edited November 8, 2014 by varsass

[Cynthum]

Im having the same problem aswell where my target changes orbit spontaneously during a rendezvous. I hope an answer can be found soon. I am running about the same mods but in 0.24.2.64bit

[Cynthum]

Well unless its been figured out. I found a work around it so far, just make velocity match burn above 2.5km and make the closing-in manually at a slow speed. It's worked for me so far.

[varsass]

Still haven't figured out what the problem is, I'm still trying

Can you post your mod list please, I need a list of suspect as short as possible

Edited November 16, 2014 by varsass

[worir4]

It is bahamutoD armory that causes this. If you extended the physics range this happens. I think if you update to the latest version it should be fixed or reduce the physics range to default.

[varsass]

It is bahamutoD armory that causes this. If you extended the physics range this happens. I think if you update to the latest version it should be fixed or reduce the physics range to default.

Thanks a lot, you saved my KSP