All I get are errors with footstep & no sound works pls help

[kjettil]

I'm using Unity 2021.3.9f1

I'm using the Paid shooter/melee/3rd person version 2.6.2a

The error I'm receiving is this (for both feet):

NullReferenceException: Object reference not set to an instance of an object Invector.vFootStep.StepOnTerrain (Invector.FootStepObject footStepObject) (at Assets/Invector-3rdPersonController/Basic Locomotion/Scripts/FootStep/Scripts/vFootStep.cs:201)

I have not changed the script in any way from the way it was in the package.

I am also getting this note in the errors along with the above:  nvector.vFootStepTrigger.OnTriggerEnter (UnityEngine.Collider other) (at Assets/Invector-3rdPersonController/Basic Locomotion/Scripts/FootStep/Scripts/vFootStepTrigger.cs:77)

Essentially what is happening is the Footstep system is not working. I looked at the audio mixer with it on, and that doesn't even move. All other package sounds and systems seem to be working.  My terrain layers are set to default, they have terrain colliders.  The feet triggers are set to Ignore Raycast, this is how they came.  I've watched the footsteps tutorial video and that did not helop (very out of date actually), as well as the "Recreating the Shooter TechDemo Scene" video (same issue). 

Please help, I am beyond stuck and spent an entire day reading and watching and trying to find videos and it's all for the old version, and I can't find anyone with these problems or explain the current system.

Thank you!!!

[axbaby123]

The footstep audio mixer made 2 of my other assets to have errors. Lipsync Pro and Game Options ( For some reason it thought footstep mixer was master mixer. easy fix) 

I suggest try a different Invector prefab like Basic locomotion, mellee or shooter.
Create your own character and see if the footstep system gets installed on your player properly.

2021.3 still has problems (and slower) ,try anything 2020.3 as a test.

[kjettil]

Thank you for the reply, I am using shooter though. The one that has all three in it.

[manwitch]

I would say go through every part of the footstep component in the inspector and make sure it is exactly the same as any of the demo scenes.

I've had this problem pop up, and always fixed it by going through each thing in the inspector component and making sure it's right, most often it is something with the triggers, like I copied them from a demo character and pasted to mine so the component is still looking for them from the demo character.

So make sure you drag the foot triggers directly from your character in the hierarchy to the inspector and things like that.

Hope this helps.

[kjettil]

Cool, I'll do that. Thanks manwitch