Jump to content

Getting NullReferenceException at CometVFXController.LateUpdate


Recommended Posts

Having a problem with my career game.  For some reason, apparently when a comet spawns, something is wrong because I get the following errors repeated endlessly:


NullReferenceException: Object reference not set to an instance of an object
  at CometVFXController.LateUpdate () [0x00156] in <c1858a3f77504bd1aaa946fdccf84670>:0 
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

I can fix it temporarily by going into the save file and deleting the comet:

		VESSEL
		{
			pid = 54f8d0d629f941c88626240aa5329f4d
			persistentId = 3893921262
			name = UnknownComet
			type = SpaceObject
			sit = ORBITING
			landed = False
			skipGroundPositioning = False
			vesselSpawning = True
			launchedFrom = 
			landedAt = 
			displaylandedAt = 
			splashed = False
			met = 6225711.4006192945
			lct = 6225711.4006192945
			lastUT = -1
			distanceTraveled = 0
			root = 0
			lat = 9.6270188652078712
			lon = -86.927851974552311
			alt = 28145353356.800259
			hgt = -1
			nrm = 0,1,0
			rot = 0.0685398951,-0.800244808,-0.243902251,0.543527603
			CoM = 0,0,0
			stg = 0
			prst = False
			ref = 0
			ctrl = False
			PQSMin = 0
			PQSMax = 0
			GroupOverride = 0
			OverrideDefault = False,False,False,False
			OverrideActionControl = 0,0,0,0
			OverrideAxisControl = 0,0,0,0
			OverrideGroupNames = ,,,
			altDispState = DEFAULT
			ORBIT
			{
				SMA = 630842177619.66125
				ECC = 0.97469954410955661
				INC = -9.688934326171875
				LPE = 0
				LAN = 144.62237548828125
				MNA = -0.0064265099161463779
				EPH = 6225711.4006192945
				REF = 0
			}
			PART
			{
				name = PotatoComet
				cid = 0
				uid = 1738383386
				mid = 1738383386
				persistentId = 2014826312
				launchID = 0
				parent = 0
				position = 0,0,0
				rotation = 0,0,0,1
				mirror = 1,1,1
				symMethod = Radial
				istg = 0
				resPri = 0
				dstg = 0
				sqor = 0
				sepI = 0
				sidx = 0
				attm = 0
				sameVesselCollision = False
				srfN = None, -1
				mass = 150
				shielded = False
				temp = -1
				tempExt = 0
				tempExtUnexp = 0
				staticPressureAtm = 0
				expt = 1
				state = 0
				attached = True
				autostrutMode = Off
				rigidAttachment = False
				flag = 
				rTrf = 
				modCost = 0
			}
			ACTIONGROUPS
			{
			}
			DISCOVERY
			{
				state = 1
				lastObservedTime = 6225711.4006192945
				lifetime = 1147356.4636230469
				refTime = 1728000
				size = 6
			}
			FLIGHTPLAN
			{
			}
			CTRLSTATE
			{
			}
			VESSELMODULES
			{
				ModularFlightIntegrator
				{
				}
				AxisGroupsModule
				{
				}
				PWBVesselModule
				{
					resource1 = 
					resource2 = 
					resource3 = 
				}
				SnackConsumption
				{
					LastUpdateTime = 0
					supplierMinerCraftId = 
					lastMinerToDepositCraftId = 
				}
				CrewRequirementVesselModule
				{
				}
				PksUpgradeVesselModule
				{
					lastTimeCheck = 0
				}
				ParkingBrake
				{
					lat = 0
					lon = 0
					alt = 0
					positionSet = False
				}
				VesselModuleSave
				{
				}
				KSPWheelVesselDebug
				{
				}
				KSPWheelDustCamera
				{
				}
				WorkshopManager
				{
					Workshops
					{
					}
				}
				BetterBurnTimeData
				{
				}
				ModuleStabilization
				{
				}
				CometVessel
				{
					typeName = long
					cometPartId = 2014826312
					vfxStartDistance = 2.2105851501226423
					comaWidthRatio = 1145895.1771259308
					tailMaxWidthRatio = 1
					tailMaxLengthRatio = 104.03748750686646
					ionTailMaxWidthRatio = 0.29999999999999999
					comaWidth = 2229044.1421592887
					tailWidth = 2229044.1421592887
					tailLength = 231904152.09215087
					ionTailWidth = 668713.24264778662
					hasName = False
					radius = 74.5837173
					seed = 1738383386
					numGeysers = 50
					numNearDustEmitters = 125
					optimizedCollider = False
					fragmentDynamicPressureModifier = 0
				}
				KSPWheelVesselControl
				{
				}
				AlertMonitors_Module
				{
					initted = True
				}
			}
		}

Here is the log file and the persistent.sfs file.  Note that I am running about 220 mods, this is a long term career save which was upgraded from 1.8.1

Any help would be appreciated

Link to comment
Share on other sites

18 hours ago, linuxgurugamer said:

Having a problem with my career game.  For some reason, apparently when a comet spawns, something is wrong because I get the following errors repeated endlessly:



NullReferenceException: Object reference not set to an instance of an object
  at CometVFXController.LateUpdate () [0x00156] in <c1858a3f77504bd1aaa946fdccf84670>:0 
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

I can fix it temporarily by going into the save file and deleting the comet:


		VESSEL
		{
			pid = 54f8d0d629f941c88626240aa5329f4d
			persistentId = 3893921262
			name = UnknownComet
			type = SpaceObject
			sit = ORBITING
			landed = False
			skipGroundPositioning = False
			vesselSpawning = True
			launchedFrom = 
			landedAt = 
			displaylandedAt = 
			splashed = False
			met = 6225711.4006192945
			lct = 6225711.4006192945
			lastUT = -1
			distanceTraveled = 0
			root = 0
			lat = 9.6270188652078712
			lon = -86.927851974552311
			alt = 28145353356.800259
			hgt = -1
			nrm = 0,1,0
			rot = 0.0685398951,-0.800244808,-0.243902251,0.543527603
			CoM = 0,0,0
			stg = 0
			prst = False
			ref = 0
			ctrl = False
			PQSMin = 0
			PQSMax = 0
			GroupOverride = 0
			OverrideDefault = False,False,False,False
			OverrideActionControl = 0,0,0,0
			OverrideAxisControl = 0,0,0,0
			OverrideGroupNames = ,,,
			altDispState = DEFAULT
			ORBIT
			{
				SMA = 630842177619.66125
				ECC = 0.97469954410955661
				INC = -9.688934326171875
				LPE = 0
				LAN = 144.62237548828125
				MNA = -0.0064265099161463779
				EPH = 6225711.4006192945
				REF = 0
			}
			PART
			{
				name = PotatoComet
				cid = 0
				uid = 1738383386
				mid = 1738383386
				persistentId = 2014826312
				launchID = 0
				parent = 0
				position = 0,0,0
				rotation = 0,0,0,1
				mirror = 1,1,1
				symMethod = Radial
				istg = 0
				resPri = 0
				dstg = 0
				sqor = 0
				sepI = 0
				sidx = 0
				attm = 0
				sameVesselCollision = False
				srfN = None, -1
				mass = 150
				shielded = False
				temp = -1
				tempExt = 0
				tempExtUnexp = 0
				staticPressureAtm = 0
				expt = 1
				state = 0
				attached = True
				autostrutMode = Off
				rigidAttachment = False
				flag = 
				rTrf = 
				modCost = 0
			}
			ACTIONGROUPS
			{
			}
			DISCOVERY
			{
				state = 1
				lastObservedTime = 6225711.4006192945
				lifetime = 1147356.4636230469
				refTime = 1728000
				size = 6
			}
			FLIGHTPLAN
			{
			}
			CTRLSTATE
			{
			}
			VESSELMODULES
			{
				ModularFlightIntegrator
				{
				}
				AxisGroupsModule
				{
				}
				PWBVesselModule
				{
					resource1 = 
					resource2 = 
					resource3 = 
				}
				SnackConsumption
				{
					LastUpdateTime = 0
					supplierMinerCraftId = 
					lastMinerToDepositCraftId = 
				}
				CrewRequirementVesselModule
				{
				}
				PksUpgradeVesselModule
				{
					lastTimeCheck = 0
				}
				ParkingBrake
				{
					lat = 0
					lon = 0
					alt = 0
					positionSet = False
				}
				VesselModuleSave
				{
				}
				KSPWheelVesselDebug
				{
				}
				KSPWheelDustCamera
				{
				}
				WorkshopManager
				{
					Workshops
					{
					}
				}
				BetterBurnTimeData
				{
				}
				ModuleStabilization
				{
				}
				CometVessel
				{
					typeName = long
					cometPartId = 2014826312
					vfxStartDistance = 2.2105851501226423
					comaWidthRatio = 1145895.1771259308
					tailMaxWidthRatio = 1
					tailMaxLengthRatio = 104.03748750686646
					ionTailMaxWidthRatio = 0.29999999999999999
					comaWidth = 2229044.1421592887
					tailWidth = 2229044.1421592887
					tailLength = 231904152.09215087
					ionTailWidth = 668713.24264778662
					hasName = False
					radius = 74.5837173
					seed = 1738383386
					numGeysers = 50
					numNearDustEmitters = 125
					optimizedCollider = False
					fragmentDynamicPressureModifier = 0
				}
				KSPWheelVesselControl
				{
				}
				AlertMonitors_Module
				{
					initted = True
				}
			}
		}

Here is the log file and the persistent.sfs file.  Note that I am running about 220 mods, this is a long term career save which was upgraded from 1.8.1

Any help would be appreciated

Hello @linuxgurugamer,

I think that is strange why the Orbit don't have IDENT (orbit central object):

            {
                SMA = 630842177619.66125
                ECC = 0.97469954410955661
                INC = -9.688934326171875
                LPE = 0
                LAN = 144.62237548828125
                MNA = -0.0064265099161463779
                EPH = 6225711.4006192945
                REF = 0

                IDENT = Sun
            }

Maybe the error is because of that? Still a bug anyway... :)

 

Link to comment
Share on other sites

3 minutes ago, pmborg said:

Hello @linuxgurugamer,

I think that is strange why the Orbit don't have IDENT (orbit central object):

            {
                SMA = 630842177619.66125
                ECC = 0.97469954410955661
                INC = -9.688934326171875
                LPE = 0
                LAN = 144.62237548828125
                MNA = -0.0064265099161463779
                EPH = 6225711.4006192945
                REF = 0

                IDENT = Sun
            }

Maybe the error is because of that? Still a bug anyway... :)

 

I'll try adding that, but I looked at another comet from a totally different save, and it wasn't in that either.

Have you seen the IDENT in any other comets?

Link to comment
Share on other sites

Just now, linuxgurugamer said:

I'll try adding that, but I looked at another comet from a totally different save, and it wasn't in that either.

Have you seen the IDENT in any other comets?

Yes all my comets have it, is a mandatory attribute of an orbit definition.

sample:

...

            ORBIT
            {
                SMA = 14510146109.909868
                ECC = 0.072268052009404268
                INC = 0.17273380632162127
                LPE = 150.36950317684014
                LAN = 271.72275194698381
                MNA = 0.48202389435198006
                EPH = 3762050381.8495355
                REF = 0
                IDENT = Sun
            }
            PART
            {
                name = PotatoRoid

...

Link to comment
Share on other sites

1 hour ago, pmborg said:

Hello @linuxgurugamer,

I think that is strange why the Orbit don't have IDENT (orbit central object):

Would you know offhand what needs to be completed before comets are instantiated?

Edit:  I added that IDENT and tested, it seems that fixed it.  But why it's missing in two different saves/installs?  Weird

What's even weirder is that when I saved while exiting , the IDENT was again missing

Edited by linuxgurugamer
Link to comment
Share on other sites

12 hours ago, linuxgurugamer said:

Would you know offhand what needs to be completed before comets are instantiated?

Edit:  I added that IDENT and tested, it seems that fixed it.  But why it's missing in two different saves/installs?  Weird

What's even weirder is that when I saved while exiting , the IDENT was again missing

"Maybe" you have an "old addon" that is doing that corruption in the save game file, it seams that the old versions of KSP instead of IDENT, were using OBJ=#number

and that number was a code to the central object in orbit, sample:

ORBIT
 {
   SMA = 76875.4600066045
   ECC = 0.136808532664149
   INC = 32.6082297441138
   LPE = 91.4665699628126
   LAN = 305.802690796769
   MNA = 0.556028537338098
   EPH = 19189976.1161395
   REF = 3
   OBJ = 0
 }

Where 0 means Kerbol.

Which is now IDENT=Sun

I would say that now is just a matter of finding which addon is causing it, I would say that all related with Kupernicus are good candidates, but just guessing...

 

Link to comment
Share on other sites

4 minutes ago, pmborg said:

I would say that now is just a matter of finding which addon is causing it, I would say that all related with Kupernicus are good candidates, but just guessing...

Helpful, but not there yet.  I don't have Kopernicus or any planet packs, this is a stock install, with only about 225 mods installed :D

However, in my dev install, I only have 15-20, and it happened there, so that will make it easier to find.

Getting back to a previous question, what are the minimum requirements for a comet to be create?

Edited by linuxgurugamer
Link to comment
Share on other sites

Just now, linuxgurugamer said:

Helpful, but not there yet.  I don't have Kopernicus or any planet packs, this is a stock install, with only about 225 mods installed :D

However, in my dev install, I only have 15-20, and it happened there, so that will make it easier to find

Yes but the problem is the save game, is corrupted, for example  LPE = 0, cant be.

need to go now, catch you later...

Link to comment
Share on other sites

Another thing.  In my dev install, I see the same thing, without the errors:

			ORBIT
			{
				SMA = 593004555714.89502
				ECC = 0.9749194903628563
				INC = -28.734825134277344
				LPE = 0
				LAN = 266.32772827148438
				MNA = -0.0084042778995882528
				EPH = 1024349.080328606
				REF = 0
			}

So it must be a mod.  This occurred after deleting the comet and running though some time.

The only mods I can think of which might have anything to do with this would be the graphics mods.  I'm not running anything strange in this install.  The graphical mods I have installed are:

  • EnvironmentalVisualenhancements
  • PlanetShine
  • Scatterer

BTW, LPE is (from the wiki): 

  • Longitude of periapsis (LPE) specifies the orientation of the orbit within its plane (angle anticlockwise from the ascending node to the periapsis).

and while I agree it's unlikely, LPE values would go from -180 to +180, so 0 is not invalid

Link to comment
Share on other sites

Ok, seems that comet creation is related to the Tracking Station being fully upgraded.

In a brand new install, no mods, I created a career game, cheated lots of funds, upgraded the tracking station to full (also did some other upgrades). and then after a short while and some time warping, exited. 

Looked at the save, and there is a new comet there:

		VESSEL
		{
			pid = 75211c7a8fc04a468ea31cfa57f1f553
			persistentId = 1377070934
			name = UnknownComet
			type = SpaceObject
			sit = ORBITING
			landed = False
			skipGroundPositioning = False
			vesselSpawning = True
			launchedFrom = 
			landedAt = 
			displaylandedAt = 
			splashed = False
			met = 4935047.2916424591
			lct = 4935047.2916424591
			lastUT = -1
			distanceTraveled = 0
			root = 0
			lat = 0.8191854815248053
			lon = 96.170516343981376
			alt = 29980592382.015678
			hgt = -1
			nrm = 0,1,0
			rot = -0.360264778,0.701886177,0.124481767,0.601721942
			CoM = 0,0,0
			stg = 0
			prst = False
			ref = 0
			ctrl = False
			PQSMin = 0
			PQSMax = 0
			GroupOverride = 0
			OverrideDefault = False,False,False,False
			OverrideActionControl = 0,0,0,0
			OverrideAxisControl = 0,0,0,0
			OverrideGroupNames = ,,,
			altDispState = DEFAULT
			ORBIT
			{
				SMA = 42673882359.937744
				ECC = 0.52378602587295031
				INC = -0.82004261016845703
				LPE = 0
				LAN = 336.08987426757813
				MNA = -0.54571695331496684
				EPH = 4935047.2916424591
				REF = 0
			}
			PART
			{
				name = PotatoComet
				cid = 0
				uid = 923041929
				mid = 923041929
				persistentId = 325214204
				launchID = 0
				parent = 0
				position = 0,0,0
				rotation = 0,0,0,1
				mirror = 1,1,1
				symMethod = Radial
				istg = 0
				resPri = 0
				dstg = 0
				sqor = 0
				sepI = 0
				sidx = 0
				attm = 0
				sameVesselCollision = False
				srfN = None, -1
				mass = 150
				shielded = False
				temp = -1
				tempExt = 0
				tempExtUnexp = 0
				staticPressureAtm = 0
				expt = 1
				state = 0
				PreFailState = 0
				attached = True
				autostrutMode = Off
				rigidAttachment = False
				flag = 
				rTrf = 
				modCost = 0
			}
			ACTIONGROUPS
			{
			}
			DISCOVERY
			{
				state = 1
				lastObservedTime = 4935047.2916424591
				lifetime = 358008.56323242188
				refTime = 1728000
				size = 4
			}
			FLIGHTPLAN
			{
			}
			CTRLSTATE
			{
			}
			VESSELMODULES
			{
				FlightIntegrator
				{
				}
				AxisGroupsModule
				{
				}
				CometVessel
				{
					typeName = short
					cometPartId = 325214204
					vfxStartDistance = 2.0666891977190973
					comaWidthRatio = 1081415.2479171753
					tailMaxWidthRatio = 1
					tailMaxLengthRatio = 55.182738304138184
					ionTailMaxWidthRatio = 0.29999999999999999
					comaWidth = 0
					tailWidth = 0
					tailLength = 0
					ionTailWidth = 0
					hasName = False
					radius = 20.8181686
					seed = 923041929
					numGeysers = 4
					numNearDustEmitters = 28
					optimizedCollider = False
					fragmentDynamicPressureModifier = 0
				}
			}
		}

As you can see from the orbit, LPE is 0, and there is no OBJ or IDENT.  The OBJ and IDENT are also not there in any of the asteroids.  Also, in a test vessel in orbit, OBJ and IDENt aren't there either.

Again from the WIKI:

  • REF : a reference number giving the celestial body that the object is orbiting.
Link to comment
Share on other sites

On 9/29/2020 at 9:18 PM, linuxgurugamer said:

Having a problem with my career game.  For some reason, apparently when a comet spawns, something is wrong because I get the following errors repeated endlessly:



NullReferenceException: Object reference not set to an instance of an object
  at CometVFXController.LateUpdate () [0x00156] in <c1858a3f77504bd1aaa946fdccf84670>:0 
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

I can fix it temporarily by going into the save file and deleting the comet:


		VESSEL
		{
			pid = 54f8d0d629f941c88626240aa5329f4d
			persistentId = 3893921262
			name = UnknownComet
			type = SpaceObject
			sit = ORBITING
			landed = False
			skipGroundPositioning = False
			vesselSpawning = True
			launchedFrom = 
			landedAt = 
			displaylandedAt = 
			splashed = False
			met = 6225711.4006192945
			lct = 6225711.4006192945
			lastUT = -1
			distanceTraveled = 0
			root = 0
			lat = 9.6270188652078712
			lon = -86.927851974552311
			alt = 28145353356.800259
			hgt = -1
			nrm = 0,1,0
			rot = 0.0685398951,-0.800244808,-0.243902251,0.543527603
			CoM = 0,0,0
			stg = 0
			prst = False
			ref = 0
			ctrl = False
			PQSMin = 0
			PQSMax = 0
			GroupOverride = 0
			OverrideDefault = False,False,False,False
			OverrideActionControl = 0,0,0,0
			OverrideAxisControl = 0,0,0,0
			OverrideGroupNames = ,,,
			altDispState = DEFAULT
			ORBIT
			{
				SMA = 630842177619.66125
				ECC = 0.97469954410955661
				INC = -9.688934326171875
				LPE = 0
				LAN = 144.62237548828125
				MNA = -0.0064265099161463779
				EPH = 6225711.4006192945
				REF = 0
			}
			PART
			{
				name = PotatoComet
				cid = 0
				uid = 1738383386
				mid = 1738383386
				persistentId = 2014826312
				launchID = 0
				parent = 0
				position = 0,0,0
				rotation = 0,0,0,1
				mirror = 1,1,1
				symMethod = Radial
				istg = 0
				resPri = 0
				dstg = 0
				sqor = 0
				sepI = 0
				sidx = 0
				attm = 0
				sameVesselCollision = False
				srfN = None, -1
				mass = 150
				shielded = False
				temp = -1
				tempExt = 0
				tempExtUnexp = 0
				staticPressureAtm = 0
				expt = 1
				state = 0
				attached = True
				autostrutMode = Off
				rigidAttachment = False
				flag = 
				rTrf = 
				modCost = 0
			}
			ACTIONGROUPS
			{
			}
			DISCOVERY
			{
				state = 1
				lastObservedTime = 6225711.4006192945
				lifetime = 1147356.4636230469
				refTime = 1728000
				size = 6
			}
			FLIGHTPLAN
			{
			}
			CTRLSTATE
			{
			}
			VESSELMODULES
			{
				ModularFlightIntegrator
				{
				}
				AxisGroupsModule
				{
				}
				PWBVesselModule
				{
					resource1 = 
					resource2 = 
					resource3 = 
				}
				SnackConsumption
				{
					LastUpdateTime = 0
					supplierMinerCraftId = 
					lastMinerToDepositCraftId = 
				}
				CrewRequirementVesselModule
				{
				}
				PksUpgradeVesselModule
				{
					lastTimeCheck = 0
				}
				ParkingBrake
				{
					lat = 0
					lon = 0
					alt = 0
					positionSet = False
				}
				VesselModuleSave
				{
				}
				KSPWheelVesselDebug
				{
				}
				KSPWheelDustCamera
				{
				}
				WorkshopManager
				{
					Workshops
					{
					}
				}
				BetterBurnTimeData
				{
				}
				ModuleStabilization
				{
				}
				CometVessel
				{
					typeName = long
					cometPartId = 2014826312
					vfxStartDistance = 2.2105851501226423
					comaWidthRatio = 1145895.1771259308
					tailMaxWidthRatio = 1
					tailMaxLengthRatio = 104.03748750686646
					ionTailMaxWidthRatio = 0.29999999999999999
					comaWidth = 2229044.1421592887
					tailWidth = 2229044.1421592887
					tailLength = 231904152.09215087
					ionTailWidth = 668713.24264778662
					hasName = False
					radius = 74.5837173
					seed = 1738383386
					numGeysers = 50
					numNearDustEmitters = 125
					optimizedCollider = False
					fragmentDynamicPressureModifier = 0
				}
				KSPWheelVesselControl
				{
				}
				AlertMonitors_Module
				{
					initted = True
				}
			}
		}

Here is the log file and the persistent.sfs file.  Note that I am running about 220 mods, this is a long term career save which was upgraded from 1.8.1

Any help would be appreciated

I don't see the log file, but if you are using Kopernicus, we had a kinda similar issue that may be fixed by simply updating.  Maybe try?

Essentially, my first try at spawning comets wasn't spawning all the values they needed.

Edited by R-T-B
Link to comment
Share on other sites

7 hours ago, linuxgurugamer said:

Getting back to a previous question, what are the minimum requirements for a comet to be create?

Hello, @linuxgurugamer

If you want a comet, or force a comet in a save file, you can play the comet mission, it will be added if the size that you want :)

In KSP 1.10 I always have a comet there.

6 hours ago, linuxgurugamer said:

Another thing.  In my dev install, I see the same thing, without the errors:


			ORBIT
			{
				SMA = 593004555714.89502
				ECC = 0.9749194903628563
				INC = -28.734825134277344
				LPE = 0
				LAN = 266.32772827148438
				MNA = -0.0084042778995882528
				EPH = 1024349.080328606
				REF = 0
			}

So it must be a mod.  This occurred after deleting the comet and running though some time.

The only mods I can think of which might have anything to do with this would be the graphics mods.  I'm not running anything strange in this install.  The graphical mods I have installed are:

  • EnvironmentalVisualenhancements
  • PlanetShine
  • Scatterer

BTW, LPE is (from the wiki): 

  • Longitude of periapsis (LPE) specifies the orientation of the orbit within its plane (angle anticlockwise from the ascending node to the periapsis).

and while I agree it's unlikely, LPE values would go from -180 to +180, so 0 is not invalid

Yes that is true the value can be zero, but its like win a lottery have it with zero, so that's why I suspect that is part of some bug, or a force default value as it seams...

 

6 hours ago, linuxgurugamer said:

Ok, seems that comet creation is related to the Tracking Station being fully upgraded.

In a brand new install, no mods, I created a career game, cheated lots of funds, upgraded the tracking station to full (also did some other upgrades). and then after a short while and some time warping, exited. 

Looked at the save, and there is a new comet there:


		VESSEL
		{
			pid = 75211c7a8fc04a468ea31cfa57f1f553
			persistentId = 1377070934
			name = UnknownComet
			type = SpaceObject
			sit = ORBITING
			landed = False
			skipGroundPositioning = False
			vesselSpawning = True
			launchedFrom = 
			landedAt = 
			displaylandedAt = 
			splashed = False
			met = 4935047.2916424591
			lct = 4935047.2916424591
			lastUT = -1
			distanceTraveled = 0
			root = 0
			lat = 0.8191854815248053
			lon = 96.170516343981376
			alt = 29980592382.015678
			hgt = -1
			nrm = 0,1,0
			rot = -0.360264778,0.701886177,0.124481767,0.601721942
			CoM = 0,0,0
			stg = 0
			prst = False
			ref = 0
			ctrl = False
			PQSMin = 0
			PQSMax = 0
			GroupOverride = 0
			OverrideDefault = False,False,False,False
			OverrideActionControl = 0,0,0,0
			OverrideAxisControl = 0,0,0,0
			OverrideGroupNames = ,,,
			altDispState = DEFAULT
			ORBIT
			{
				SMA = 42673882359.937744
				ECC = 0.52378602587295031
				INC = -0.82004261016845703
				LPE = 0
				LAN = 336.08987426757813
				MNA = -0.54571695331496684
				EPH = 4935047.2916424591
				REF = 0
			}
			PART
			{
				name = PotatoComet
				cid = 0
				uid = 923041929
				mid = 923041929
				persistentId = 325214204
				launchID = 0
				parent = 0
				position = 0,0,0
				rotation = 0,0,0,1
				mirror = 1,1,1
				symMethod = Radial
				istg = 0
				resPri = 0
				dstg = 0
				sqor = 0
				sepI = 0
				sidx = 0
				attm = 0
				sameVesselCollision = False
				srfN = None, -1
				mass = 150
				shielded = False
				temp = -1
				tempExt = 0
				tempExtUnexp = 0
				staticPressureAtm = 0
				expt = 1
				state = 0
				PreFailState = 0
				attached = True
				autostrutMode = Off
				rigidAttachment = False
				flag = 
				rTrf = 
				modCost = 0
			}
			ACTIONGROUPS
			{
			}
			DISCOVERY
			{
				state = 1
				lastObservedTime = 4935047.2916424591
				lifetime = 358008.56323242188
				refTime = 1728000
				size = 4
			}
			FLIGHTPLAN
			{
			}
			CTRLSTATE
			{
			}
			VESSELMODULES
			{
				FlightIntegrator
				{
				}
				AxisGroupsModule
				{
				}
				CometVessel
				{
					typeName = short
					cometPartId = 325214204
					vfxStartDistance = 2.0666891977190973
					comaWidthRatio = 1081415.2479171753
					tailMaxWidthRatio = 1
					tailMaxLengthRatio = 55.182738304138184
					ionTailMaxWidthRatio = 0.29999999999999999
					comaWidth = 0
					tailWidth = 0
					tailLength = 0
					ionTailWidth = 0
					hasName = False
					radius = 20.8181686
					seed = 923041929
					numGeysers = 4
					numNearDustEmitters = 28
					optimizedCollider = False
					fragmentDynamicPressureModifier = 0
				}
			}
		}

As you can see from the orbit, LPE is 0, and there is no OBJ or IDENT.  The OBJ and IDENT are also not there in any of the asteroids.  Also, in a test vessel in orbit, OBJ and IDENt aren't there either.

Again from the WIKI:

  • REF : a reference number giving the celestial body that the object is orbiting.

About the REF, yes is true by bad, is on wiki more info: https://wiki.kerbalspaceprogram.com/wiki/Orbit, not OBJ.

 

So in resume:

 IDENT appears when we install Kopernicus, and we save a file with it:

RuntimeUtility.cs:            orbit.AddValue("IDENT", UBI.GetUBI(body));

I was assuming in the begging a touch of Kopernicus :)

 

is the problem now solved, removing the comet, on that old save ?

 

 

Edited by pmborg
Link to comment
Share on other sites

1 hour ago, pmborg said:

Hello, @linuxgurugamer

If you want a comet, or force a comet in a save file, you can play the comet mission, it will be added if the size that you want :)

In KSP 1.10 I always have a comet there.

Yes that is true the value can be zero, but its like win a lottery have it with zero, so that's why I suspect that is part of some bug, or a force default value as it seams...

 

About the REF, yes is true by bad, is on wiki more info: https://wiki.kerbalspaceprogram.com/wiki/Orbit, not OBJ.

 

So in resume:

 IDENT appears when we install Kopernicus, and we save a file with it:

RuntimeUtility.cs:            orbit.AddValue("IDENT", UBI.GetUBI(body));

I was assuming in the begging a touch of Kopernicus :)

 

is the problem now solved, removing the comet, on that old save ?

 

 

Still a problem.  Funny thing is that I see that there are at least 3 comets in the system when I look at the tracking view.

In terms of the LPE, in a virgin clean install, there wasn't a comet until I maxed out the tracking station and possibly the launch pad as well.  

Then I got one, with the following:

			ORBIT
			{
				SMA = 42673882359.937744
				ECC = 0.52378602587295031
				INC = -0.82004261016845703
				LPE = 0
				LAN = 336.08987426757813
				MNA = -0.54571695331496684
				EPH = 4935047.2916424591
				REF = 0
			}

 

I agree about the odds, but there may be something in the game to start it there.

I'm going to clone the entire install and start a removal process to try to identify the mod(s) causing the problem

Edited by linuxgurugamer
Link to comment
Share on other sites

4 hours ago, darthgently said:

I get tons of NULL OBJ refs, from a variety of sources since Breaking Ground on linux.  None of the orbits in my sfs have IDENT.   And I'm running EVE.  If this fixes the issue, I'm going to celebrate with pizza and everything

First, lets see a log file.  Would be good to know what the errors were first.

Then remove EVE and test, and let us know the result.

Regarding the IDENT, that was a red herring, it was a Kopernicus field and had no relation to my problem

Edited by linuxgurugamer
Link to comment
Share on other sites

3 hours ago, linuxgurugamer said:

First, lets see a log file.  Would be good to know what the errors were first.

Then remove EVE and test, and let us know the result.

Regarding the IDENT, that was a red herring, it was a Kopernicus field and had no relation to my problem

Well, the plan was actually to remove EVE and test, then maybe share a log file if it didn't work, but since the fix was a red herring, your plan takes first place.  I'm in the process of building another machine as I get so many low level errors that I need to take this laptop apart and look for a heat issue.  I've already tested the RAM and it is good. 

The machine is a Core i7 with 16GB of RAM and an NVidia GEFORCE GTX in opengl mode on Debian linux.  In KSP,  on days I play, I get daily protected memory accesses leading to hard crashes, often preceeded by lots of NULL OBJECT refs, which are nearly always there to some degree, often in editor in calls to Editor Logic related functions while in the VAB but also in flight related to various mods and unity functions. 

Occasionally I get GPU related low level errors leading to hard crashes.  It is so across the board it smells like corrupted memory leading to multiple outcomes.  Lately the NULL OBJECT errors gather like a storm when using symmetry mode, especially after selecting a subass'y that I'd previously saved; it will get into a state where I can't put down the part/subassembly I was trying to place, nor can I place it.  Ghost symmetric versions of the object will appear and freeze at odd angles and locations.  All I can do is exit the editor. 

The machine has 1/2 a gig of RAM leftover (but linux is strange, iirc, in that it will pre-allocate RAM even if it isn't really used, then really allocate it later; the short version) and I have disk space left over.  I have no issues with other programs but KSP is the biggest load I run on it also.  Blender is ok, as is GIMP.  I don't have a player log as I haven't been launching via the Unity launcher.  But here is link to my KSP.log with the NULL OBJ and other exceptions.

Logs: https://drive.google.com/file/d/1xwmfpA1E0YaXJSTKTUSXKiK7nzpdc7l8/view?usp=sharing

[edit]  Crashed just now with GPU error when loading launch scene (EVE uninstalled):

i965: Failed to submit batchbuffer: Bad address
 

Edited by darthgently
Link to comment
Share on other sites

3 hours ago, darthgently said:

Occasionally I get GPU related low level errors leading to hard crashes.  It is so across the board it smells like corrupted memory leading to multiple outcomes.  Lately the NULL OBJECT errors gather like a storm when using symmetry mode, especially after selecting a subass'y that I'd previously saved; it will get into a state where I can't put down the part/subassembly I was trying to place, nor can I place it.  Ghost symmetric versions of the object will appear and freeze at odd angles and locations.  All I can do is exit the editor. 

I took a look at your file.  First off, I don't see the error I was getting, so ignore the EVE comments.

Secondly, I have no idea what's causing your exception storm.  I'd suggest doing a memory test (in-depth), and then run a cpu monitor while playing the game, see if your cpu is overheating or not.  Finally, if overclocked, remove the overclocking and try again

 

Link to comment
Share on other sites

Just now, linuxgurugamer said:

I took a look at your file.  First off, I don't see the error I was getting, so ignore the EVE comments.

Secondly, I have no idea what's causing your exception storm.  I'd suggest doing a memory test (in-depth), and then run a cpu monitor while playing the game, see if your cpu is overheating or not.  Finally, if overclocked, remove the overclocking and try again

 

Thanks for looking, much appreciated, but now you know why I've been hesitant to get others involved.  But being new-ish to KSP I didn't know how much of this was "normal" for a modded install and how much was peculiar to my set up.  I wanted to get a sense of the context.  Not overclocked, but this model has been known to overheat like many gaming laptops.  So I'm trying to carve out time to disassemble, apply heat sink paste, clean fans, and maybe nerf the speed a bit.  Memory tests showed clean.  But I've never gotten the mmap protected memory error or the low level GPU errors outside of KSP and my understanding is that mods, and obviously KSP, have a free hand in screwing with memory if they so desire or fumble, so who knows.  I'll get what I can under control on this end, then see what remains of the issues.  Again thanks, let me know if you have a coffee fund, patreon, or whatever

Link to comment
Share on other sites

1 hour ago, darthgently said:

Thanks for looking, much appreciated, but now you know why I've been hesitant to get others involved.  But being new-ish to KSP I didn't know how much of this was "normal" for a modded install and how much was peculiar to my set up.  I wanted to get a sense of the context.  Not overclocked, but this model has been known to overheat like many gaming laptops.  So I'm trying to carve out time to disassemble, apply heat sink paste, clean fans, and maybe nerf the speed a bit.  Memory tests showed clean.  But I've never gotten the mmap protected memory error or the low level GPU errors outside of KSP and my understanding is that mods, and obviously KSP, have a free hand in screwing with memory if they so desire or fumble, so who knows.  I'll get what I can under control on this end, then see what remains of the issues.  Again thanks, let me know if you have a coffee fund, patreon, or whatever

Once you get your hardware issues taken care of, you can start the next set of testing.

Make a full copy of the entire KSP directory.  In the copy, move 1/2 of the mods out of the GameData directory, then start the game.  See how the errors look, if none, then you now have an idea as to which mods are the issue.

The other way is to start with a clean install, make sure it's working ok, then add one or two at a time and test again.

I do have a Patreon:  https://www.patreon.com/linuxgurugamer

 

Edit:  Looking again at your file, I see major problems with the IDFlags/Blackheart mod (no idea which mod it is, just see the errors)

So start by removing that

 

Edit 2:  If you installed the DecalStickers, then know it's not listed as compatible with 1.10.1.  Specifically, it has an old version of Firespitter in there

 

 

5 minutes ago, linuxgurugamer said:

Edit:  Looking again at your file, I see major problems with the IDFlags/Blackheart mod (no idea which mod it is, just see the errors)

So start by removing that

 

Edit 2:  If you installed the DecalStickers, then know it's not listed as compatible with 1.10.1.  Specifically, it has an old version of Firespitter in there

 

Pinging @darthgently as I think I posted the change after you read the message.

 

Be sure that all mods are compatible

Edited by linuxgurugamer
Link to comment
Share on other sites

15 hours ago, linuxgurugamer said:

I still have more testing to do, but when I removed EnvironmentalVisualEnhancements, the errors went away

Just did another test, I wasn't satisfied with the first one.

Unfortunately, I got the error again, even with EVE removed

Link to comment
Share on other sites

3 minutes ago, linuxgurugamer said:

Just did another test, I wasn't satisfied with the first one.

Unfortunately, I got the error again, even with EVE removed

This is good news also. EVE is so great.  But bad news because a gremlin still lurks somewhere....

Link to comment
Share on other sites

  • 4 weeks later...
On 10/1/2020 at 2:10 PM, R-T-B said:

I don't see the log file, but if you are using Kopernicus, we had a kinda similar issue that may be fixed by simply updating.  Maybe try?

Essentially, my first try at spawning comets wasn't spawning all the values they needed.

Not using Kopernicus, but thanks

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...