Question Help!

Hi,
I have a problem with the script for camera movement,
more precisel this error:

Assets \ Scripts \ CameraFollow.cs (27.18): error CS0111: Type 'CameraFollow' already defines a member called 'HandleTranslation' with the same parameter types

Here's the script

Code (CSharp):

1.  
2. using System.Collections;
3. using System.Collections.Generic;
4. using UnityEngine;
5.  
6. public class CameraFollow : MonoBehaviour
7. {
8.  
9.     [SerializeField] private Vector3 offset;
10.     [SerializeField] private Transform target;
11.     [SerializeField] private float translateSpeed;
12.     [SerializeField] private float rotationSpeed;
13.  
14.     void FixedUpdate()
15.     {
16.        HandleTranslation();
17.        HandleRotation();
18.      
19.     }
20.  
21.     private void HandleTranslation()
22.     {
23.         var targetPosition = target.TransformPoint(offset);
24.         transform.position = Vector3.Lerp(transform.position, targetPosition, translateSpeed * Time.deltaTime);
25.     }
26.    
27.    
28.     private void HandleTranslation()
29.     {
30.         var direction = target.position = transform.position;
31.         var rotation = Quaternion.LookRotation(direction(Vector3.up));
32.         transform.rotation = Quaternion.Lerp(transform.rotation, rotation, rotationSpeed * Time.deltaTime);
33.     }
34.  
35.    
36. }
37.  

 

The error is quite specific. Notice that you have HandleTranslation defined twice, I believe the second one should be named HandleRotation.

 

thank you very much
I fixed it!!
Thanks @JeffDUnity3D

 

Glad you're back up and running. This will save you a LOT of time in the future:

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 list, 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)

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.

How to understand compiler and other errors and even fix them yourself:

https://forum.unity.com/threads/ass...3-syntax-error-expected.1039702/#post-6730855

ALSO... if you are going to monkey-bang tutorial code in , this will ALSO save you a lot of time:

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.

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!