Question Turn the car towards waypoints

Hi everyone.
Here I have a question. Please don't be brief and short. I need as detail information as possible.

Here I have a simple task. Yellow car is under keyboard control and here I have no problems/questions. The question is regarding green car. It should move towards waypoints and also turn towards moving direction.
Here is the code for moving car:

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4.  
5. public class gr_car_move : MonoBehaviour
6. {
7.     public float speed;
8.     public Transform[] targets;
9.  
10.     private int currentTargetIndex = 0;
11.  
12.     // Start is called before the first frame update
13.     void Start()
14.     {
15.         if (targets.Length == 0)
16.         {
17.             Debug.LogError("No targets assigned to script!");
18.         }
19.     }
20.  
21.     // Update is called once per frame
22.     void Update()
23.     {
24.         var step = speed * Time.deltaTime;
25.         transform.position = Vector3.MoveTowards(transform.position, targets[currentTargetIndex].position, step);
26.  
27.         if (transform.position == targets[currentTargetIndex].position)
28.         {
29.             if (currentTargetIndex == targets.Length - 1)
30.             {
31.                 // reached last target, stop cycling
32.                 return;
33.             }
34.             currentTargetIndex = (currentTargetIndex + 1) % targets.Length;
35.         }
36.  
37.  
38.     }
39. }

As for now , it doesn't turn towards its moving direction. Requesting assistance

 

That's not a simple task.

You might THINK it is simple because you can describe it to another human, but vehicle waypoint following and navigation is a deep topic and nobody is going to retype everything you need here in this little tiny text window. That's just not a thing.

Instead, work from tutorials. Fortunately there are thousands of them. Do the first two or three that come up on Google, but MAKE SURE you do them properly.

Pay particular attention to Step #2 below:

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! 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:

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

 

instead of this text someone could post something useful anyway I got your point even if this is a standard message for those who (in your point of view) doesn't look for, before asking questions ...

and furthermore , I already found my own solution for this case , traditional or custom , but anyway it works fine for me.

Thank you for your reply