using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class WeaponFire : MonoBehaviour
{
public ParticleSystem gunsmoke;
public int selectedweapon;
public AudioSource brrrt;
// Start is called before the first frame update
private void Start()
{
selectedweapon = 1;
}
// Update is called once per frame
void Update()
{
if (Input.GetButton("Fire1"))
{
if (selectedweapon == 1)
{
gunsmoke.Play();
}
if (Input.GetButtonDown("1Key"))
{
selectedweapon = 1;
Debug.Log("hi");
}
else
{
if (Input.GetButtonDown("2Key"))
{
selectedweapon = 2;
}
else
{
if (Input.GetButtonDown("3Key"))
{
selectedweapon = 3;
}
else
{
if (Input.GetButtonDown("4Key"))
{
selectedweapon = 4;
}
}
}
}
}
}
}
Can you be more specific? What part isnāt working?
Maybe start by placing a Debug.Log(āHelloā); straight after line 19 and shift everything else down. Is that displaying a message in your console? I expect it will.
If that works, start putting Debug.log() in other if blocks to see which ones arenāt working and go from there.
Itās hard to say more since you didnāt say what you expected to happen vs what actually happened.
I think your logic is faulty, or at least highly questionable.
NONE of your weapon select code runs unless you are holding down the fire button.
And while youāre holding down the fire button, EVERY FRAME you are restarting the smoke particle (if you have weapon 1 selected).
Rather than untangle this tiny piece of problematic code, just go start with a weapon and weapon select tutorial, get it right the first time. It is nothing anyone is going to retype for you in this little text box. It has more than code, such as setting up the scene / prefabs.
Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:
How to do tutorials properly, two (2) simple steps to success:
Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. Thatās how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.
Fortunately this is the easiest part to get right: Be a robot. Donāt make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!
If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.
Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.
Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.
Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If thereās an error, you will NEVER be the first guy to find it.
Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!
When you are trying to debug your logic, use this approach:
You must find a way to get the information you need in order to reason about what the problem is.
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
youāre getting an error or warning and you havenāt noticed it in the console window
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 supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as Debug.Log("Problem!",this);
If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.
You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.
You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.
You could also just display various important quantities in UI Text elements to watch them change as you play the game.
Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.
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:
When in doubt, print it out!ā¢
Note: the print() function is an alias for Debug.Log() provided by the MonoBehaviour class.
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class WeaponFire : MonoBehaviour
{
public ParticleSystem gunsmoke;
public int selectedweapon;
public AudioSource brrrt;
// Start is called before the first frame update
private void Start()
{
selectedweapon = 1;
}
// Update is called once per frame
void Update()
{
if (Input.GetButton("Fire1"))
{
if (selectedweapon == 1)
{
gunsmoke.Play();
}
if (Input.GetButtonDown("1Key"))
{
selectedweapon = 1;
}
else
{
if (Input.GetButtonDown("2Key"))
{
selectedweapon = 2;
}
else
{
if (Input.GetButtonDown("3Key"))
{
selectedweapon = 3;
}
else
{
if (Input.GetButtonDown("4Key"))
{
selectedweapon = 4;
}
}
}
}
}
}
}
I click the keys and the values of selectedweapon donāt change. BTW I did the debug log thing ages ago and it didnāt print. I put it in the āif buttondown oneā.
Those if statements that change the selected weapon will only run if the fire button is held down at the same time as you press one of the number keys.
One fix would be to pull those weapon select if statements out on their own so theyāre not inside the āFire1ā if block. Then they should work when you press one of the number keys even when not holding that fire button down.
