Game Version
[e.g. 2026.1.123.4567]Operating System
Windows 11What Happened
The game crashes when setting orbit to eccentricity slightly above 1. Log file reports the following:03:49:16.566 ERROR Unhandled exception System.Exception: unclassifiable orbital energy: NaN
Parent: Sol Time: ∞secs.
PositionCci: <NaN, NaN, NaN>
VelocityCci: <NaN, NaN, NaN>
at KSA.Orbit.CreateFromStateCci(IParentBody parent, SimTime stateTime, double3 positionCci, double3 velocityCci, byte4 orbitLineColor)
at KSA.PatchedConic.CreateFromCalcData(PatchCalcData calcData)
at KSA.FlightPlan.CalculateEscapePatch(PatchedConic patch, SimTime startTime, PatchedConic& nextPatch)
at KSA.FlightPlan.CalculatePatch(List`1& patches, PatchedConic patch, SimTime startTime, KeyHash idHash, SimTime& expiryGameTime, Nullable`1 nextBurnTime, Boolean burnPatch, Int32 polynomialOrderN, IOrbiter encounterFilter)
at KSA.FlightPlan.ComputeCompleteTrajectory(Int32 patchLimit, Int32 polynomialOrderN, IOrbiter encounterFilter)
at KSA.Vehicle.Teleport(Orbit orbit, Nullable`1 body2Cce, Nullable`1 bodyRates)
at KSA.InputEvents.TeleportInputData.Apply()
at KSA.InputEvents.TypedBuffer`1.ApplyAll()
at KSA.InputEvents.ApplyInputEvents()
at KSA.Program.PrepareFrame(Double currentPlayerTime, Double dtPlayer)
at KSA.Program.OnFrame(Double currentPlayerTime, Double dtPlayer)
at KSA.App.Run()
at KSA.Program.Main(String[] inArgs).
What Was Expected
No crash or floating point error when setting eccentricity slightly above 1.Reproduction Steps
- Start game already in orbit.
- Set the orbit the default once above Earth with safety checks enabled
- Set orbit to eccentricity to 1.000001, and time since periapsis to 0. The game crashes here. I am only able to replicate this crash with time to periapsis set to 0. I am not able to replicate this crash for eccentricity less than 1, though.
- This error persists when time since periapsis is set near to 0.
Reproduction Rate
AlwaysAdditional Info
- Note I am running the "very low settings" community config, but I don't think that changes anything.
- I'm sure that the error is coming from specifically the process of setting the state vector from orbital elements. Maybe from a near-to 0/0 fp error that evades checks for a parabolic orbit.
Upvote
1