Project

General

Profile

Bug #28460

Targeting Jool moon causes crash to desktop! "CheckEncounter: failed to find any intercepts at all"

Added by Krazy1 over 2 years ago. Updated almost 2 years ago.

Status:
New
Severity:
Low
Assignee:
-
Category:
QA
Target version:
-
Start date:
08/26/2021
% Done:

0%

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

Description

Steps to reproduce in stock KSP 1.12.2 on Win10:

Start new sandbox game.
Time warp to year 1, day 199, 1 hour (approx.)
Launch a Mk1 command pod
Use alt-F12 cheat to set orbit. Copy/ paste these (from my career save where I found this):

SMA = 81052129392.125916
ECC = 0.83260632468582185
INC = 0.038412899555496038
LPE = 353.52092985938856
LAN = 345.21017397841274
MNA = 0.0083908025450638787

Go to map view.
Set view to Jool.
Set target to any Jool moon.
Crash to desktop

Player log spams "CheckEncounter: failed to find any intercepts at all"

Game breaking - must fix.

Player (2).log (829 KB) Player (2).log Krazy1, 08/26/2021 05:17 AM
KSP (2).log (449 KB) KSP (2).log Krazy1, 08/26/2021 05:18 AM
persistent.sfs (62 KB) persistent.sfs time and orbit set, ready to CTDT Krazy1, 08/26/2021 05:18 AM
YaRroRB.png (1.68 MB) YaRroRB.png Krazy1, 08/26/2021 05:26 AM
iWruMWE.png (1.19 MB) iWruMWE.png Krazy1, 08/26/2021 05:27 AM
58615
58616

History

#1 Updated by Krazy1 over 2 years ago

Also happens in KSP 1.11.2 with sometimes not immediate crash and more verbose log:

[LOG 17:33:25.756] CheckEncounter: failed to find any intercepts at all
[LOG 17:33:25.873] CheckEncounter: failed to find any intercepts at all
[LOG 17:33:25.916] CheckEncounter: failed to find any intercepts at all
[LOG 17:33:25.962] CheckEncounter: failed to find any intercepts at all
[LOG 17:33:26.037] CheckEncounter: failed to find any intercepts at all
[LOG 17:33:26.520] CheckEncounter: failed to find any intercepts at all
[LOG 17:33:26.601] CheckEncounter: failed to find any intercepts at all
[EXC 17:33:26.984] StackOverflowException: The requested operation caused a stack overflow.
    Targeting+Interval.Create () (at <06f13185617646e5bc801baeab53ab75>:0)
    Smooth.Pools.Pool`1[T].Borrow () (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting+Interval.Borrow (Targeting+Sample s1, Targeting+Sample s2, System.Int32 tgt_index) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting+Interval.Subdivide () (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)
    Targeting.add_crossing_subdivisions (System.Collections.Generic.List`1[T] intervals, Targeting+Interval ival, System.Boolean reversed) (at <06f13185617646e5bc801baeab53ab75>:0)

#2 Updated by Jonassoe over 2 years ago

You can get around this by disabling "always show closest approach" in settings.
However, this is a very serious bug and I don't know why they're not working on it. It's a bug that reliably crashes the application to desktop - why is that not #1 priority?

#3 Updated by Zeggpold2 almost 2 years ago

I just ran into this in 1.12.3.3137 (LinuxPlayer). The option "Always Show Closest Approach for Target" in Main Menu > Settings > Graphics was already off, so that workaround didn't work for me. I seem to have gotten past it by unsetting the target, but I'm not sure that was what actually helped.
In my case, it's worse than just crashing KSP; KSP uses up all the memory on the system, which locks up the GUI. I have to login remotely and kill the KSP process to get back control.

Also available in: Atom PDF