es03_scripting
An introduction to the main concepts associated with Scripting are covered in this YouTube playlist.
On this page, you can find an overview of the project contents seen in the video.
All the videos refer to scenes and scripts contained in the "Assets/_Scripting" folder.
- 00-Callbacks-Debug
- 01-TargetFollower
- 02-DeltaTime
- 03-Keyboard-GetKey
- 04-KeyBoard-Input-Movement
- 05-Camera-Independent-Movement
This scene simply contains a red cube with a script attached to it that prints to the editor console, using the Debug.Log(), the different Unity callbacks.
An even more detailed description on the execution order of Unity callbacks can be found in this Unity thread
This scene shows a following behaviour scripted in the file, TargetFollowe.cs. The MonoBehaviour collects the referenced object from the Target property in the script and then follows rotating and moving with according to the other properties of the script.
This scene simply sows the importance of using the property Time.deltaTimewhen moving objects during runtime. The proper usage of this property ensures to have an application which is not frame-dependant (i.e., the objects' behaviour is not affected by the framerate the application is capable to run on a given hardware).
A further explanation of this concept, and other examples are detailed also in this Unity manual page.
This scene shows how to use the Input class and specifically the GetKey() function to detect input from the keyboard and act accordingly. In this action the example is very simple: the color of each cube is randomly assigned, using the Random class:
private Color[] _colors = new[] {Color.red, Color.blue, Color.green, Color.magenta, Color.white, Color.cyan, Color.yellow, Color.black};
private void ChangeColor()
{
if(_renderer == null)
return;
_renderer.material.color = _colors[Random.Range(0, _colors.Length)];
}
This scene demonstrates how to read directional input from either WASD or arrow keys. The cubes on the left have their movement continuously updated in order to maintain changes. The cubes on the right are translated from their original starting position based on the input read either through Input.GetKey() or Input.GetAxis(). This is to show how the input read through the first method is simply a boolean which can be either true or false. On the contrary, using the GetAxis() method the read input gradually increases and decreases from one of the extremes -1 or 1 to the rest value of 0.
Further details on the GetAxis() function can be found in the documentation page or in this YouTube video.
TBD