Component is not working.

Unity Engine
,
1

So i’m new to making games with unity and visual studio so im going off the videos i have seen,i have written code that should make my “character” move velocity up but when i put getcomponent into c# it doesnt seem to recognise that there is a rigidbody component in my “player” model can anyone help?
this is my code.
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class Player : MonoBehaviour
{
// Start is called before the first frame update
void Start()
{

}
// Update is called once per frame
void Update()
{
//check if spacebar is pressed down
if (Input.GetKeyDown(KeyCode.Space) == true)
{
GetComponent().AddForce(Vector3.up, ForceMode.VelocityChange);
}
}
}

2

Is there a reason why you need to add it via code, and not add it via the inspector?

3

This part sounds strange. First of all you said it doesn’t recognise that there is a rigidbody component in your player. The method AddComponent is supposed to add a new component. It sounds like your player already has a Rigidbody component, so you should use GetComponent because you can not add more than one Rigidbody components to the same object.

Also make sure you spelled Rigidbody correctly. It would help to actually include your code in your question. That would clear up a lot of potential issues when we see the actual code you’re using.

What does

actually mean? Do you get a compile time error? If so, what’s the error and on which line? Again, show your actual code. If you get a runtime error when playing, what exact error do you get?

4

As others point out above, there would absolutely NEVER be:

or

For the simple reason that it is spelled Rigidbody. It’s right here in the documentation, which should be your first stop:

While you’re at it, there is no addcomponent either. It’s called AddComponent, also clearly outlined in the documentation:

https://docs.unity3d.com/ScriptReference/GameObject.AddComponent.html

Now, armed with this new knowledge that spelling and capitalization is absolutely critical, go back to where you started from and check your work over. Here’s how:

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!

Finally, when you have errors, don’t post here… just go fix your errors! Here’s how:

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.

Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

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.