Question idk want is wrong can someone help me ? th error is : Assets\scripts\mechgenerator.cs(17,20): error

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
RequireComponent(typeof(Meshfilter));
public class mechgenerator : MonoBehaviour
{
mesh mesh;

Vector3[] vertices;
int[] triangles;



// Start is called before the first frame update
void Start()
{
mech = New mech();

getcomponent<mechhFillter>().mech = mesh;

CreateShape();
updatemesh();
}


void CreateShape ()
{
vertices = new Vector3[]
{
new Vector3 (0,0,0),
new Vector3 (0,0,1),
new Vector3 (1,0,0)
};

triangles = new int[]
{
0, 1, 2
};

}

void updatemesh()
{
mech.clear();

mech.vertices = vertices;
mech.triangles = triangles;
}

}

 

1. You have failed to actually provide us the error.
2. You have not posted your code in code tags, which makes it hard for us to find the error.
3. You have spelling errors throughout your script:

-

mech

should probably be

mesh

as you do not have a variable called

mech

defined anywhere in your script.
- You have incorrectly typed

GetComponent

as

getcomponent

. C# is a case-sensitive language, so your spelling and capitalisation needs to be 100% correct.
- You have put your required component as

RequireComponent(typeof(Meshfilter));

but then are attempting to access

mechhFillter

later in your script (where you also try to get

mech

from that component when it probably should be

mesh

- as mentioned earlier in my response).​

I suspect that you are not using a proper IDE (Visual Studio or VS Code) as this should be showing you all your errors and underlining your mistakes in your scripts.

You need to go back through your entire script and take your time with your spelling and capitalisation as you are not being careful enough with what you are typing. For any in-built Unity commands/functions (like

GetComponent

you should be looking at the scripting API documentation as that clearly shows you how it should be written.

 

You're making typos, as babia notes above.

You can fix all your typing mistakes yourself. 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.

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.

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, don't post here... just go fix your errors! See above...

 

New -> new

Edit: actually nevermind... You have like 30 typos and misspelling. Rewrite everything.

 

sorry for my typos (i have dislexia)

but tx fot the tips

 

oke

 

Sorry to hear that. Compiler doesn't care. It requires zero errors.

You should have intellisense already working in your browser to help you with these simple typing mistakes.

If not, this may help you with intellisense and possibly other Visual Studio integration problems:

Sometimes the fix is as simple as doing Assets -> Open C# Project from Unity. Other times it requires more.

Other times it requires you also nuke the userprefs and .vsconfig and other crufty low-value high-hassle files that Visual Studio tends to slowly damage over time, then try the above trick.

Barring all that, move on to other ideas:

https://forum.unity.com/threads/intellisense-not-working-with-visual-studio-fix.836599/

Also, try update the VSCode package inside of Unity: Window -> Package Manager -> Search for Visual Studio Code Editor -> Press the Update button

Also, this: https://forum.unity.com/threads/no-suggestions-in-vscode.955197/#post-6227874