Fixing NaN errors

[John FX]

Hello,

I`ve been getting fairly regular NaN errors since installing RO possibly due to SOI changes. Black screen, NaN everywhere, game freezes.

Does anyone know of a way to fix these, possibly by editing the persistence file?

Thank you in anticipation.

[Padishar]

Without seeing the persistence file and a log file (output_log.txt or player.log) it's impossible to tell...

[John FX]

1 hour ago, Padishar said:

Without seeing the persistence file and a log file (output_log.txt or player.log) it's impossible to tell...

Here you go, Should have posted them in the OP...

Output.log

Persistent

Just had a look in my output log and there were so many errors I can`t tell what the problem is.

The NaN`s start about when Mars 1 (Mars 1 and Mars 2 both have the Nan issue) is unpacking,

Spoiler

Unpacking Mars 1
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

TestFlightInterface: Could not find TestFlightInterop module
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

TestFlightInterface: Could not find TestFlightInterop module
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

TestFlightInterface: Could not find TestFlightInterop module
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

RemoteTech: Loading Flightcomputer from persistent!
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

RemoteTech: Loading queued commands from persistent ...
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

RemoteTech: Loading Flightcomputer from persistent!
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

RemoteTech: Loading queued commands from persistent ...
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Look rotation viewing vector is zero
 
(Filename:  Line: 70)

Invalid parameter because it was infinity or nan.
 
(Filename:  Line: 155)

Invalid parameter because it was infinity or nan.
 
(Filename:  Line: 155)

Invalid parameter because it was infinity or nan.

 

Edited March 20, 2016 by John FX
more info

[Padishar]

You've messed up the second link a bit but I managed to find it.

There are so many exceptions in your log that I'm not surprised you're getting nasty crashes.  They start during part loading when Procedural Parts gives an exception for several of its parts.  Then there's an exception from Scatterer while trying to destroy something though it looks like most other plugins are just being initialised about then.  Then there are a couple of null reference exceptions from KAC when going from the tracking station to the space center.  Then the same Scatterer exception happens again when switching from space center to flight followed by an argument exception from DeadlyReentry (calling a GUI function from OnStart).

There are a number of exceptions from MJFARExt because it can't load the FAR dll.  I assume this would be normal if you don't have FAR installed but you do appear to as FAR also gives an index out of range exception when trying to build its voxel stuff.  There are then ~28000 lines of "Transform error" followed by, what appears to be FAR, getting upset about stuff being NaN.  Then there are also lots of other exceptions from other mods and bits of stock code presumably because the earlier exceptions have prevented some stuff from being initialised correctly.

I can't see anything obviously wrong in the .sfs but, if I had to guess at the underlying cause, I would say that the installations of either or both of Procedural Parts and FAR are broken and this is causing exceptions during the initialisation of the flight scene that causes everything to break...

Edit: Also, the exception from Deadly Reentry could be causing something nasty so that should be reported to the author as it should be fairly simple to fix.

Edited March 20, 2016 by Padishar

[NathanKell]

Sadly those OnStart ProcParts exceptions are a known issue with the current release. They only occur during the loading screen and things otherwise work. I've pushed a fix to git but there's been no release.

[John FX]

I remember that FAR had issues with being installed with CKAN so I`ll reinstall that manually, I did notice also that it seemed to happen more often if I used KAC`s `jump to ship`

I`ll also report the error to the DRE thread. I may remove scatterer too until after 1.1 and RVE are playing well with RO.

Thank you so much for looking at it, there was just so much going on I wasn`t sure where to start.

[Jansn67]

Sporadic i have NaN-Errors with Weight and Electricity ONLY (at switching) to some (not all, but they all are the same Vessel) of my RemoteTech- and ScanSAT-Probes. But in general, they work all fine.

First solution: dont switch there if its not really neccessary.

Second solution: if its neccessary and if i see NaN in Trackig Center (Mod = Ressource Window in TS) -> quicksave -> edit quicksafe.sfs -> quickload.

 

Edited March 21, 2016 by Jansn67

[Padishar]

The only thing I know of that causes electric charge NaNs is using an engine that has a max EC capacity of 0 but allows it to be tweakable in the VAB.  Opening the part menu of the engine will cause it to read NaN/0.0 and this will cause most things that try to get the mass of the part (or the whole vessel) to get a NaN result (including the CoM indicator in the VAB).  Fundamentally, this is a stock bug with the resource tweakable sliders but making something tweakable when it can only range from 0 to 0 is not sensible so the engine really should be fixed.  It can be temporarily fixed by just dragging the tweakable slider a little which will reset it to 0.0/0.0 and the mass calculations will start working again.

Given you are switching between vessels in flight it is unlikely to be related to this.  It is more likely that some mod that tries to adjust the EC to simulate on-rails consumption is making a mess of things and setting it to NaN.  There isn't much you can do about this other than finding a reliable sequence of actions that can reproduce it with as few mods installed as possible and then reporting it to the authors of those mods that look likely.

[John FX]

Just to update, I reinstalled FAR manually and I avoid switching to craft with KAC and have not had a NaN error since.