I was working on an infinite scrolling game and I needed the background to scroll so I was copying a tutorial and here is the code I got (please keep in mind that this is my first game and I was following a tutorial).
There’s potentially other issues with the code, but the specific problem you mention is due to case-sensitivity. i.e. when coding in C# (and most other languages) the case matters. It’s GetComponent, not Getcomponent.
thanks, it helped now it works properly
For future reference, photographs of code are not a thing. If you post a code snippet, ALWAYS USE CODE TAGS:
How to use code tags: https://discussions.unity.com/t/481379
Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration, and to avoid completely wasting your time:
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:
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.
I’m actually wondering how you managed to write GetComponent wrong. Visual Studio should immediately pick it up and correct it as you’re typing. At least my VS does that. Even if it doesn’t. Moving the cursor onto your “Getcomponent” and pressing CTRL+space should bring up the auto-complete window. Just hitting return to pick the first suggestion should have fixed it as well. So I’m really confused how people manage to actually make such mistakes.
Ahhh, I just took another look at the screenshot and now it’s obvious… Visual Studio wasn’t setup correctly. Signs are: “Miscellaneous Files” at the top instead of “Assembly-CSharp”. Also MonoBehaviour wasn’t recognised as a type. That means the actual C# project is not loaded.
Make sure your VS has the Unity Tools installed. Go to VS–>Tools–>Get Tools and Features. This should bring up the Visual Studio Installer. Under Workloads you should find the category Gaming. Make sure the Unity tools have a checkmark. If not, install them.
Second step, if you’re sure that your Visual Studio has the Unity tools installed, make sure VS is actually selected as the scripting editor in Unity. In Unity go to Edit->Preferences->External Tools. Make sure the right version of Visual Studio is selected as the “External Script Editor”. Sometimes it helps to first select something else and then back to VS.
Once that’s done, when you now double click on a script inside the Unity editor, Unity should open the actual C# project in Visual Studio with the choosen file open. Now the auto complete features should work.
