Project

General

Profile

Bug #2835

PART.NODE{} throws exception if PART.NODE.transform doesn't exist, which crashes the part loader

Added by Greys almost 10 years ago. Updated almost 8 years ago.

Status:
Closed
Severity:
Normal
Assignee:
-
Category:
Parts
Target version:
-
Start date:
07/25/2014
% Done:

100%

Version:
0.24
Platform:
Any
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

If the .mu associated with a part does not contain a transform corresponding to the value of PART.NODE.transform, the following exception will be thrown

Part: Cannot add attach node. Transform of name 'Top'

NullReferenceException: Object reference not set to an instance of an object
  at AttachNode..ctor (System.String id, UnityEngine.Transform transform, Int32 size, AttachNodeMethod attachMethod) [0x00000] in <filename unknown>:0 

  at Part.AddAttachNode (.ConfigNode node) [0x00000] in <filename unknown>:0 

  at PartLoader.ParsePart (.UrlConfig urlConfig, .ConfigNode node) [0x00000] in <filename unknown>:0 

  at PartLoader+.MoveNext () [0x00000] in <filename unknown>:0 
UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
:MoveNext()
UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
PartLoader:StartLoad()
:MoveNext()@

No parts including the part throwing the error, and all parts alphabetically following it (per standard loading order depth first 0-9 a-z search) will fail to be loaded and be missing from KSP until restarted with the transform fixed

History

#1 Updated by Greys almost 10 years ago

typo correction:

No parts including the part throwing the error, and all parts alphabetically following it (per standard loading order depth first 0-9 a-z search) will be loaded and will be missing from KSP until restarted with the transform fixed

#2 Updated by TriggerAu almost 8 years ago

  • Status changed from New to Needs Clarification

#3 Updated by TriggerAu almost 8 years ago

  • Status changed from Needs Clarification to Closed
  • % Done changed from 0 to 100

Closing this report out for now. If you find it is still occuring in the latest version of KSP please open a new report (and this one can be linked to it.) For best results, the wiki contains really useful info for when creating a report http://bugs.kerbalspaceprogram.com/projects/ksp/wiki.

You can also ask questions about the bug cleanup in the forum here: http://forum.kerbalspaceprogram.com/index.php?/topic/143980-time-to-clean-up-the-bug-tracker/ and tag @TriggerAu to get my attention

Also available in: Atom PDF