mi code isent working error 1002 why how do i fix

Unity Engine
1

her is the code

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using unityEngine.imputSystem;
using System.Diagnostics;

[DebuggerDisplay($“{{{nameof(GetDebuggerDisplay)}(),nq}}”)]
public class playercontroller : MonoBehaviour
{
private rigidbody rb;
private float movementX;
private float movementY;
// Start is called before the first frame update
void Start()
{
rb = Getcomponent();
}

// Update is called once per frame
void Update()
{

}

void OnMove(inputvalue movementvalue)
{
Vector2 movementVector = movementvalue.get();

movementX = movementVector.X;
movementY = movementVector.Y;
}

void fixedupdate()
{

Vector3 movement = New Vector3(movementX, 0.0f, movementY);

rb.addforce(movement);
}

private string GetDebuggerDisplay() => ToString();
}

2

I would seriously suggest that you start with some C# basic tutorials because there are so many things wrong with your script. You just seem to be typing stuff in without using the correct case for your functions or commands.
Just for starters, the following are all wrong (and you can see this by looking in the manual or using an IDE that actually shows your errors):
private rigidbody rb;
rb = Getcomponent();
void fixedupdate()
Vector3 movement = New Vector3(movementX, 0.0f, movementY);
rb.addforce(movement);

Those are the ones that I noticed straight away, but I can only assume that there will be more as it appears you are not typing things in properly.

If you are following a tutorial, then you need to go back through it and make sure you are typing it in exactly as it is shown. You must use the exact uppercase/lowercase letters and have to be perfect.

Also for future reference:

  • When posting code on the forum, use code tags (it’s in the guidelines that you should be following).
  • If you are going to post an error, then post the full message as that has the line number and character number where the error is happening (and it also says what file it is occurring in). The code (that you provided) give no information for anyone to follow, so is the least important thing to provide.
1 Like
3

Everything that @BABIA_GameStudio above says, plus this:

If you’re gonna monkey-hammer-bang tutorial code in, here is how to do tutorials properly:

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 single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly. 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 it. Google is your friend here. Do NOT continue until you fix the error. The 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.

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…

Remember: NOBODY memorizes error codes. 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.

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors.

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)

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.