Project

General

Profile

Bug #26971

Decoupling an EVA constructed vehicle renders controls dead and causes StackTrace

Added by ShadowZone over 3 years ago. Updated over 2 years ago.

Status:
Resolved
Severity:
Low
Assignee:
Category:
Regression
Target version:
Start date:
01/05/2021
% Done:

100%

Version:
Platform:
Windows
Expansion:
Core Game
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

I built a vehicle in orbit to go to the Mun and back. That worked without a flow. The problem started when trying to decouple the final stage. After decoupling, the vehicle became completely unresponsive to control inputs even though there was enough power.
Also, the orbit was messed up (see video below) and the log showed about a million StackTrace entries:

[LOG 12:13:52.374] dT is NaN! tA: 6.27323280732056, E: 0, M: 0, T: NaN
at System.Environment.get_StackTrace () [0x00000] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0
at Orbit.GetDTforTrueAnomaly (System.Double tA, System.Double wrapAfterSeconds) [0x00000] in <f8bc9e2b903e48a5b248ab0083c07c62>:0
at OrbitTargeter.UpdateNodesAndVectors () [0x00000] in <f8bc9e2b903e48a5b248ab0083c07c62>:0
at OrbitTargeter.LateUpdate () [0x00000] in <f8bc9e2b903e48a5b248ab0083c07c62>:0

I made a short clip highlighting the issue:
https://www.youtube.com/watch?v=0qUyGQ_oId4

Links to the log file and quicksave file, since I cannot produce a .craft file - it was built in orbit with EVA construction.

It might be related to this issue:
https://bugs.kerbalspaceprogram.com/issues/26926
But in my case when I rebuild the vehicle in the VAB, it works without a problem.

History

#1 Updated by victorr over 3 years ago

  • Status changed from New to Confirmed
  • Assignee set to victorr
  • % Done changed from 0 to 10

#3 Updated by Anth12 over 3 years ago

#27045 is this related? it is in the Editor however

I dont think this is related at all

#5 Updated by Anth12 about 3 years ago

Further testing shows that this is related to physicless parts being decoupled

#6 Updated by victorr almost 3 years ago

  • Status changed from Confirmed to Ready to Test
  • Target version set to 1.12.0
  • % Done changed from 10 to 80

We have made some changes in this last 1.12.0 release and would like some feedback on this issue. Thanks.

#7 Updated by Technicalfool over 2 years ago

  • Status changed from Ready to Test to Resolved
  • % Done changed from 80 to 100

This should be fixed. Please continue to report if it breaks again.

Also available in: Atom PDF