Vectors Explained (Scripting) - Revision history

Mooshua at 19:41, 19 May 2024

2024-05-19T19:41:30Z

Xerox8521: Updated to 1.7 Syntax

2015-08-14T01:55:38Z

Updated to 1.7 Syntax

Cybermind: /* Velocity Vectors */

2011-03-22T01:27:44Z

‎Velocity Vectors

CrimsonGT at 01:56, 12 November 2008

2008-11-12T01:56:26Z

CrimsonGT at 22:54, 8 October 2008

2008-10-08T22:54:02Z

CrimsonGT: New page: =Introduction= Vectors in general tend to be rather confusing until they are explained. There are three different types you will see. Position Vectors, Velocity Vectors, and Angle Vectors....

2008-10-08T21:52:07Z

New page: =Introduction= Vectors in general tend to be rather confusing until they are explained. There are three different types you will see. Position Vectors, Velocity Vectors, and Angle Vectors....

New page

=Introduction=
Vectors in general tend to be rather confusing until they are explained. There are three different types you will see. Position Vectors, Velocity Vectors, and Angle Vectors. While in most basic cases you will probably only use one of these at a time, it doesn't hurt to know what the other two parameters are there for. Here is an example of the native 'TeleportEntity' to show you what it looks like:

<pawn>
native TeleportEntity(entity, const Float:origin[3], const Float:angles[3], const Float:velocity[3]);
</pawn>

'''Position Vector''': The first Vector in this native, declared as origin[3], is the Position Vector. This simply tells us the entities absolute position in the world. The position vector could look something like {15.0, 30.0, 15.0} and this would mean the entity is 15 units along the X axis, 30 units along the Y axis, and 15 units along the Z axis.

'''Angles Vector''': The second Vector in this native, declared as angles[3], is the Angle Vector. This specifies the rotation of an object. This vector would follow the format {pitch, yaw, roll} which modifies the angles at which the object is looking. 'Pitch' is the up & down angles, 'Yaw' is the left & right, and 'Roll' is the spin along the up/down/left/right vector.

'''Velocity Vector''': The last Vector in the native is the Velocity Vector, declared as velocity[3] in the example. This vector tells the game where the object will be on the next frame. So on the next game frame, the Position Vector of this object will be the sum of the Position Vector and the Velocity Vector from our current frame.

==Velocity Vectors==
<pawn>
decl vecOrigin[32], vecVelocity[3], vecResult[3];

AddVectors(vecOrigin, vecVelocity, vecResult);
</pawn>

← Older revision		Revision as of 01:56, 12 November 2008
Line 18:		Line 18:
	AddVectors(vecOrigin, vecVelocity, vecResult);		AddVectors(vecOrigin, vecVelocity, vecResult);
	</pawn>		</pawn>
−
−	~~=Vector Natives=~~
−
−	~~Will finish code block above and add more tommorow. Sleepy time...~~

← Older revision		Revision as of 22:54, 8 October 2008
Line 18:		Line 18:
	AddVectors(vecOrigin, vecVelocity, vecResult);		AddVectors(vecOrigin, vecVelocity, vecResult);
	</pawn>		</pawn>
		+
		+	=Vector Natives=
		+
		+	Will finish code block above and add more tommorow. Sleepy time...

@@ Line 6: / Line 6: @@
 </pawn>
 '''Position Vector''': The first Vector in this native, declared as origin[3], is the Position Vector. This simply tells us the entities absolute position in the world. The position vector could look something like {15.0, 30.0, 15.0} and this would mean the entity is 15 units along the X axis, 30 units along the Y axis, and 15 units along the Z axis.
-'''Angles Vector''': The second Vector in this native, declared as angles[3], is the Angle Vector. This specifies the rotation of an object. This vector would follow the format {pitch, yaw, roll} which modifies the angles at which the object is looking. 'Pitch' is the up & down angles, 'Yaw' is the left & right, and 'Roll' is the spin along the up/down/left/right vector.
+=== Angles ===
-'''Velocity Vector''': The last Vector in the native is the Velocity Vector, declared as velocity[3] in the example. This vector tells the game where the object will be on the next frame. So on the next game frame, the Position Vector of this object will be the sum of the Position Vector and the Velocity Vector from our current frame.
+Most angles are sanitized between -180 and 180 within the source engine (for up/down on players this is -89/89!), however some weird physics shenanigans and cheating clients can exceed these values so always ensure your angles are well formed before using them.
 ==Velocity Vectors==

@@ Line 3: / Line 3: @@
 <pawn>
-native TeleportEntity(entity, const Float:origin[3], const Float:angles[3], const Float:velocity[3]);
+native int TeleportEntity(int entity, const float origin[3], const float angles[3], const float velocity[3]);
 </pawn>
@@ Line 14: / Line 14: @@
 ==Velocity Vectors==
 <pawn>
-decl vecOrigin[3], vecVelocity[3], vecResult[3];
+float vecOrigin[3], vecVelocity[3], vecResult[3];
 AddVectors(vecOrigin, vecVelocity, vecResult);
 </pawn>