NullReferenceException problem

[Kurt-Dekker]

I’m not even sure what is going on here.

You’re marking the thruster field for serialization so it shows in the editor, and gets serialized.

Then you’re new-ing a fresh non-MonoBehaviour thruster script up at Awake

As part of that you expect it to be the same one and have the ParticleSystem you might have set in the inspector.

I assure you the class you create with a new won’t have that ParticleSystem defined. I also have no idea where you intend to set that. It won’t be in the inspector because obviously when you run, Awake() will happily wipe it out with the new call.

Serialized properties in Unity are initialized as a cascade of possible values, each subsequent value (if present) overwriting the previous value:

• what the class constructor makes (either default(T) or else field initializers)

• what is saved with the prefab

• what is saved with the prefab override(s)/variant(s)

• what is saved in the scene and not applied to the prefab

• what is changed in Awake(), Start(), or even later etc.

Make sure you only initialize things at ONE of the above levels, or if necessary, at levels that you specifically understand in your use case. Otherwise errors will seem very mysterious.

Field initializers versus using Reset() function and Unity serialization:

Sensitivity in my MouseLook script.

Whatever value you set and save in your scene or prefab will wipe out the field initializer value you change in the code above. This is a common source of confusion: the object is created, so at that instant in time it has the value you set in code, but before the object is put into use, if Unity has a saved scene or saved prefab that this is already in, then the value saved is overwritten. It's best to remove the initialization value above and instead provide it in a Reset function: publi…

Crouch speed is faster than Movement Speed

If something is public: The instant you add that to your scene / prefab it is 10f … AND THEN IT GETS SERIALIZED. Now go change the value in code. Note that it has no effect: the serialized value writes over the code value. This is how Unity serialization works. If you want to define it in code, make the variable private. If you want to define it in the editor, make it public and DO NOT INITIALIZE IT. Instead, make a Reset function, which ONLY runs at the instant it is added: void Reset(…

This might also be useful to you:

Here is some timing diagram help:

Unity - Manual: Order of execution for event functions