Using Vector3

Unity Engine
1

Hello, I would like some help with a line of code, I have copied a tutorial because I am new to coding and game development and I am trying to make a block go forward, in this tutorial they put in transform.Translate(Vector3.foward*speed * Time.deltaTime); so I copied it in and it says I don’t have a definition of forward, I can’t find how to actually do it so help is wanted.

Thanks, MYSTICPORKY

1 Like
2

Hello,
for those in need of solution for this issue, I would bet it’s because Vector3 comes from the wrong namespace;
Vector.forward needs using UnityEngine; and not System.Numerics;

If anything, Vector3.forward is just a shorthand for new Vector3(0, 0, 1);.

3

How do you know they were using System.Numerics? @MYSTICPORKY please show the code from the tutorial and your full code.

4

To be fair, I didn’t actually “know”, but reading this :

I assumed he used Alt+Enter to make the error on Vector3 go away, and with such propositions:

He literally had a 50/50 chance of getting the wrong one. I could reproduce his error using System.Numerics, so I assumed it could be that.
A lot of assumptions, I know, but well, this is the kind of mistakes that can happen to anyone who’s not familiar with an API.

1 Like
5

If the code you have put in your post is exactly what you have typed, then I don’t think that is the actual error message as you have typed transform.Translate(Vector3.foward*speed * Time.deltaTime);. So I would expect the message to say you don’t have a definition of foward because you were supposed to type forward.
You need to be exact with your spelling.

1 Like
6

You must copy it with zero errors, so foward is definitely an error.

This might save you a LOT of time, as BaBiAGameStudio points out above:

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.

If you get any errors, learn how to read the error code and fix it. Google is your friend here. Do NOT continue until you fix the error. The 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.

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