Trying to open a door when pressing down a key, however. I’ve created the reference and instance to call the animation when pushing the key, but it simply won’t let me drop the reference (Trying to place the DoorAnimated Game Object into the ‘Door’ instance on the right.)
I’ve created a prefab for the door, removed the prefab, changed the name - nothing, still won’t drop.
public class DoorTriggerButton : MonoBehaviour
{
[SerializeField] private DoorAnimated door;
private void Update()
{
if (Input.GetKeyDown(KeyCode.E))
{
door.OpenDoor();
{
if (Input.GetKeyDown(KeyCode.F))
{
door.CloseDoor();
}
}
}
}
}
I was following Code Monkey’s video (2nd door) and I had this issue on the first door and now this one. I don’t know if something between 2D and 3D is the issue, but I’m totally lost atm.
The code above looks fine but maybe it has typographic errors. Most likely whatever you are dragging in does not satisfy the target field type (you did not say which field), or else you have unresolved compiler errors. You MUST fix 100% of all compiler errors first.
If you see no errors, make sure your log console selector buttons are enabled. See this graphic:
If you have errors, remember: NOBODY here memorizes error codes. That’s not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.
The complete error message contains everything you need to know to fix the error yourself.
The important parts of the error message are:
the description of the error itself (google this; you are NEVER the first one!)
the file it occurred in (critical!)
the line number and character position (the two numbers in parentheses)
also possibly useful is the stack trace (all the lines of text in the lower console window)
Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.
All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don’t have to stop your progress and fiddle around with the forum.
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:
Tutorials are a GREAT idea. Tutorials should be used this way:
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!
Well, does the gameobject you try to drag onto your reference variable actually has a script attached that is called DoorAnimated? The name of the gameobject is irrelevant. Your reference wants to reference a component named DoorAnimated. So are you sure the object you want to assign does have this component?
Also keep in mind you can not reference an object that lives in a scene from a prefab. You can only reference it from another object in the scene. Prefabs live outside of scenes. So scene objects can reference prefabs, but not the other way round. Project assets are always available and therefore can be referenced from anywhere. Objects in scenes only exist when that scene is loaded which may not be the case. So referencing scene objects from assets is not possible.
Just to make that clear. At 11:30 he creates the DoorAnimated script and at 11:39 he drags the script onto the door object which creates an instance of that script component on the dooranimated gameobject. Now you can drag the gameobject onto that variable and the editor would link up the component on the door to the variable. This is an absolute basic Unity principle.
