Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Join us on Dec 8, 2022, between 7 am & 7 pm EST, in the DOTS Dev Blitz Day 2022 - Q&A forum, Discord, and Unity3D Subreddit to learn more about DOTS directly from the Unity Developers.
    Dismiss Notice
  3. Have a look at our Games Focus blog post series which will show what Unity is doing for all game developers – now, next year, and in the future.
    Dismiss Notice

Question Error Code CS1026 Can somone help?

Discussion in 'Scripting' started by RafuRuffs, Nov 25, 2022.

  1. RafuRuffs

    RafuRuffs

    Joined:
    Apr 3, 2022
    Posts:
    5
    using System.Collections;
    using System.Collections.Generic;
    using UnityEngine;

    public class PlayerController : MonoBehaviour
    {
    public float upKeyPressed = 1;
    public float torqueAmount = 2;
    public float torqueMinus = -2;
    Rigidbody2D rb2d;
    // Start is called before the first frame update
    void Start()
    {
    rb2d = GetComponent<Rigidbody2D>();



    }


    // Update is called once per frame
    void Update()
    {
    // Alr so i need to use a input.getaxis to trigger a method. That method will then cause the true or false thing. I can use the if else statement to check if its being used or not and do smth if not.

    upKeyPressed = Input.GetAxis("Vertical");

    TorqueRotation();
    RespondToBoost();
    KeyPressUpdate();
    }
    private void RespondToBoost()
    {
    if (Input.GetAxis("Vertical")
    {
    Debug.Log("Work.");


    }
    else
    {
    Debug.Log("Hope");
    }
    }
     
  2. RafuRuffs

    RafuRuffs

    Joined:
    Apr 3, 2022
    Posts:
    5
    I have tried rewriting parts of the code, deleting the unused things but nothing seems to work
     
  3. MelvMay

    MelvMay

    Unity Technologies

    Joined:
    May 24, 2013
    Posts:
    8,629
    Please edit your post to use code-tags and not plain text. Also, you should post the complete script; the above isn't. Your problem will be just bad typing though.

    The error code is useless. The actual error gives you a description of what is wrong, it even states the line and column number.
     
  4. jvo3dc

    jvo3dc

    Joined:
    Oct 11, 2013
    Posts:
    1,507
    The code is for missing ) and indeed it's stated (roughly) where it's missing. Solution, add the missing ), even without the line number it's easy to spot:
    Code (csharp):
    1.  
    2. if (Input.GetAxis("Vertical")
    3.  
     
  5. MelvMay

    MelvMay

    Unity Technologies

    Joined:
    May 24, 2013
    Posts:
    8,629
    I know, no need to quote me. ;)
     
  6. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    29,824
    Exactly ZERO of those things are useful. There's only TWO steps to doing tutorials, and here they are:

    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.