CS0118 CS0119 Errors

Im beginner at unity pls help.
Errors:
Assets\Scripts\Cursor.cs(20,9): error CS0118: 'Ray' is a type but is used like a variable
Assets\Scripts\Cursor.cs(23,30): error CS0119: 'Ray' is a type, which is not valid in the given context

There is my code:

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4.  
5. public class Cursor : MonoBehaviour
6. {
7.     SpriteRenderer spriteRenderer;
8.     int layerMask;
9.  
10.     // Start is called before the first frame update
11.     void Start()
12.     {
13.         spriteRenderer = GetComponent<SpriteRenderer>();
14.         layerMask = LayerMask.GetMask("Ground");
15.     }
16.  
17.     // Update is called once per frame
18.     void Update()
19.     {
20.         Ray = Camera.main.ScreenPointToRay(Input.mousePosition);
21.  
22.         RaycastHit hit;
23.         if (!Physics.Raycast(Ray, out hit, 1000, layerMask))
24.             spriteRenderer.enabled = false;
25.         else {
26.             transform.position = new Vector3(hit.point.x, transform.position.y, hit.point.z);
27.             spriteRenderer.enabled = true;
28.         }
29.     }
30. }

 

You are simply making typing mistakes. Don't do that... that is only going to seriously impair your progress. Errors happen when you make typos, and in this case looks like you missed a bunch of critical words from the tutorial you were following.

You can fix your own typing mistakes without our help. Here's how:

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.

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.

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... go back to the top of this post!

 

Where is my typo? I`ve seached for it like 10 times.... and i dont see it....

 

Oh wait

I`ve found it!

it was
Ray ray = Camera.main.ScreenPointToRay(Input.mousePosition);
Ive needed to type a 2nd ray here and
if (!Physics.Raycast(ray, out hit, 1000, layerMask))
and here ray

But now there is another problem:
Code

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. public class Cursor : MonoBehaviour
5. {
6.     SpriteRenderer spriteRenderer;
7.     int layerMask;
8.     // Start is called before the first frame update
9.     void Start()
10.     {
11.         spriteRenderer = GetComponent<SpriteRenderer>();
12.         layerMask = LayerMask.GetMask("Ground");
13.     }
14.     // Update is called once per frame
15.     void Update()
16.     {
17.         Ray ray = Camera.main.ScreenPointToRay(Input.mousePosition);
18.         RaycastHit hit;
19.         if (!Physics.Raycast(ray, out hit, 1000, layerMask))
20.             spriteRenderer.enabled = false;
21.         else {
22.             transform.position = new Vector3(hit.point.x, transform.position.y, hit.point.z);
23.             spriteRenderer.enabled = true;
24.         }
25.     }
26. }

The ERROR:
NullReferenceException: Object reference not set to an instance of an object
Cursor.Update () (at Assets/Scripts/Cursor.cs:20)

 

This error is appear when i start the game.

 

This error also does not require a forum post. The answer is ALWAYS the same. ALWAYS.

How to fix a NullReferenceException error

https://forum.unity.com/threads/how-to-fix-a-nullreferenceexception-error.1230297/

Three steps to success:
- Identify what is null
- Identify why it is null
- Fix that

 

I will try.

 

The fact that it's pointing to line 20 seems to indicate spriteRenderer is null (hence the error' s name: NullReferenceException).

This in turn would indicate that your GetComponent call on line 11 is failing to... well, get that component!

Are you sure the object the Cursor script is attached to actually has a SpriteRenderer component?

 

You really should name your classes properly. The name

Cursor

is already present in the

UnityEngine

namespace. If you attempt to access

UnityEngine.Cursor

you will become extremely confused when nothing in that space works.