I am trying to make a missile launcher system on a mech that I have created. It has 4 Launch tube points, so far it fires one missile from one of the launch points. I would like to have the missiles fire from the launch tube points in sequence. I have tried creating a public transform array called LaunchTube and added the launch tube points in the inspector.
It still launchers 1 missile from the same point. Not 100% sure what to do next, I’m guessing I will need to loop through the FireMissile() code?
I’m pretty sure @diXime has found at least one of your problems, but let me offer you a robust way to find any future problems like this, since this type of logic stuff comes up all the time. I don’t think I can code for ten minutes without inadvertently doing the same thing.
With most simple malfunctions like this, what is often happening in these cases is one of the following:
the code you think is executing is not actually executing at all
the code is executing far EARLIER or LATER than you think
the code is executing far LESS OFTEN than you think
the code is executing far MORE OFTEN than you think
the code is executing on another GameObject than you think it is
To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.
Doing this should help you answer these types of questions:
is this code even running? which parts are running? how often does it run? what order does it run in?
what are the values of the variables involved? Are they initialized? Are the values reasonable?
are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)
Knowing this information will help you reason about the behavior you are seeing.
You can also put in Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene
You could also just display various important quantities in UI Text elements to watch them change as you play the game.
If you are running a mobile device you can also view the console output. Google for how on your particular mobile target.
Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong: