Getting an error : Assets/HandPresence.cs(52,39): error CS1003: Syntax error, ',' expected

Hi,

Trying to set up HandPresence but keep getting this error:

Assets/HandPresence.cs(52,39): error CS1003: Syntax error, ‘,’ expected

The code:
```csharp
**using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.XR;

public class HandPresence : MonoBehaviour
{
public List controllerPrefabs;
private InputDevice targetDevice;
private GameObject spawnedController;

// Start is called before the first frame update
void Start()
{
    List<InputDevice> devices = new List<InputDevice>();
    InputDeviceCharacteristics rightControllerCharacteristics = InputDeviceCharacteristics.Right | InputDeviceCharacteristics.Controller;
    InputDevices.GetDevicesWithCharacteristics(rightControllerCharacteristics, devices);

    foreach (var item in devices)
    {
        Debug.Log(item.name + item.characteristics);
    }

    if(devices.Count > 0)
    {
        targetDevice = devices[0];
        GameObject prefab = controllerPrefabs.Find(controller => controller.name == targetDevice.name);
        if (prefab)
        {
            spawnedController = instantiate(prefab, transform);
        }
        else
        {
            Debug.LogError("Did not find Corresponding controller model");
            spawnedController = Instantiate(controllerPrefabs[0], transform);
        }
    }
   
}

// Update is called once per frame
void Update()
{
    if (targetDevice.TryGetFeatureValue(CommonUsages.primaryButton, out bool primaryButtonValue) && primaryButtonValue)
     Debug.Log("Pressing Primary Button");

    if (targetDevice.TryGetFeatureValue(CommonUsages.trigger, out float triggerValue) && triggerValue > 0.1f)
     Debug.Log("Trigger pressed" + triggerValue);

    if (targetDevice.TryGetFeatureValue(CommonUsages.primary2DAxis, out Vector2 primary2DAxisValue) && primary2DAxisValue != Vector2.zero)
     Debug.Log("Primary Touchpad" primary2DAxisValue);
}

}**
```
what am I doing wrong?

The error tells you the line 52 and even the column (39) so all you have to do is carefully look at it…

See the difference between that and your previous Debug.Log? You are missing a “+”.

1 Like

Your code has a problem on line 52, as the error says. Look at that line closely.

1 Like

You are making typographic errors. You must make exactly ZERO of those.

Let me save you a LOT of time wrestling with this sort of silly stuff:

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:

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 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…

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.

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.

1 Like

Thanks for the answers all! being a noob here obviously

Remember, the compiler messages are there to help you find your typos. Everybody makes typos, we’re human. When you learn how to read error messages (see above) it becomes no different than a typo in an email. You just fix it and move on.

1 Like

Ok just writing here that I fixed it! TY for all the help:

  1. Missed the “+” on line 52
  2. On the line 31 I didn’t capitalise the “I” on Instantiate