ProcessLineAgainstMesh - Revision history

Blond6: --

2026-04-05T17:03:09Z

← Older revision		Revision as of 17:03, 5 April 2026
Line 38:		Line 38:

	==Example==		==Example==
	-- This example prints the name of the texture hit by the player's crosshair on any vehicle in the world. It uses processLineAgainstMesh to check for collisions between a line from the camera to a point in front of it and the meshes of vehicles.		This example prints the name of the texture hit by the player's crosshair on any vehicle in the world. It uses processLineAgainstMesh to check for collisions between a line from the camera to a point in front of it and the meshes of vehicles.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	addEventHandler("onClientRender", root,		addEventHandler("onClientRender", root,

Blond6: This example demonstrates how to use processLineOfSight to determine what the player is looking at. It gets the camera position and a point in front of it, then checks for a line of sight between those points. If something is hit, it outputs the coordinates and the type of element hit.

2026-04-05T17:02:33Z

This example demonstrates how to use processLineOfSight to determine what the player is looking at. It gets the camera position and a point in front of it, then checks for a line of sight between those points. If something is hit, it outputs the coordinates and the type of element hit.

@@ Line 38: / Line 38: @@
 ==Example==
-{{Needs Example}}
+-- This example prints the name of the texture hit by the player's crosshair on any vehicle in the world. It uses processLineAgainstMesh to check for collisions between a line from the camera to a point in front of it and the meshes of vehicles.
 ==See Also==
 {{Client world functions}}

FileEX at 18:15, 24 December 2024

2024-12-24T18:15:56Z

← Older revision		Revision as of 18:15, 24 December 2024
Line 36:		Line 36:
	*'''frameName:''' hit frame's name		*'''frameName:''' hit frame's name
	*'''worldX, worldY, worldZ:''' collision position in world space		*'''worldX, worldY, worldZ:''' collision position in world space

			==Example==
			{{Needs Example}}

	==See Also==		==See Also==
	{{Client world functions}}		{{Client world functions}}

Fernando187: Remove obsolete Requirements section

2024-11-07T17:34:10Z

Remove obsolete Requirements section

← Older revision		Revision as of 17:34, 7 November 2024
Line 36:		Line 36:
	*'''frameName:''' hit frame's name		*'''frameName:''' hit frame's name
	*'''worldX, worldY, worldZ:''' collision position in world space		*'''worldX, worldY, worldZ:''' collision position in world space

	~~==Requirements==~~
	~~{{Requirements\|n/a\|1.6.0-9.22173\|}}~~

	==See Also==		==See Also==
	{{Client world functions}}		{{Client world functions}}

SaintsTalles: /* Syntax */

2023-10-31T16:52:10Z

Syntax

← Older revision		Revision as of 16:52, 31 October 2023
Line 7:		Line 7:

	==Syntax==		==Syntax==

			Single line for convenience.
			<syntaxhighlight lang="lua">
			bool, float, float, string, string, float, float, float processLineAgainstMesh(element toTest, float startX, float startY, float startZ, float endX, float endY, float endZ)
			</syntaxhighlight>

	Return values labelled for ease of reference.		Return values labelled for ease of reference.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

Zangomangu: New feature tag

2023-09-30T16:08:41Z

New feature tag

← Older revision		Revision as of 16:08, 30 September 2023
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Client function}}		{{Client function}}
	{{~~Added~~ feature/item\|3.0161\|1.6.0\|~~22173~~\|Does a raycast against an element's renderable mesh model directly}}		{{New feature/item\|3.0161\|1.6.0\|22219\|Does a raycast against an element's renderable mesh model directly}}
	Does a raycast against an element's renderable mesh model [not the collision model!].		Does a raycast against an element's renderable mesh model [not the collision model!].
	The same functionality is already present in [[processLineOfSight]], but the latter is a little buggy due to the fact that the collision model is always simplified, and not exactly the same as the mesh, which leads to situations where no hit is detected, even though the visible mesh is hittable [or vice versa].		The same functionality is already present in [[processLineOfSight]], but the latter is a little buggy due to the fact that the collision model is always simplified, and not exactly the same as the mesh, which leads to situations where no hit is detected, even though the visible mesh is hittable [or vice versa].

Pirulax at 17:38, 23 September 2023

2023-09-23T17:38:28Z

← Older revision		Revision as of 17:38, 23 September 2023
Line 30:		Line 30:
	*'''frameName:''' hit frame's name		*'''frameName:''' hit frame's name
	*'''worldX, worldY, worldZ:''' collision position in world space		*'''worldX, worldY, worldZ:''' collision position in world space

			==Requirements==
			{{Requirements\|n/a\|1.6.0-9.22173\|}}

	==See Also==		==See Also==
	{{Client world functions}}		{{Client world functions}}

Pirulax: Add "Added feature/item" header

2023-09-23T17:37:23Z

Add "Added feature/item" header

← Older revision		Revision as of 17:37, 23 September 2023
Line 1:		Line 1:
			__NOTOC__
	{{Client function}}		{{Client function}}
	~~__NOTOC__~~		{{Added feature/item\|3.0161\|1.6.0\|22173\|Does a raycast against an element's renderable mesh model directly}}
	Does a raycast against an element's renderable mesh model [not the collision model!].		Does a raycast against an element's renderable mesh model [not the collision model!].
	The same functionality is already present in [[processLineOfSight]], but the latter is a little buggy due to the fact that the collision model is always simplified, and not exactly the same as the mesh, which leads to situations where no hit is detected, even though the visible mesh is hittable [or vice versa].		The same functionality is already present in [[processLineOfSight]], but the latter is a little buggy due to the fact that the collision model is always simplified, and not exactly the same as the mesh, which leads to situations where no hit is detected, even though the visible mesh is hittable [or vice versa].

Pirulax: Add "See Also"

2023-09-23T17:33:37Z

Add "See Also"

← Older revision		Revision as of 17:33, 23 September 2023
Line 29:		Line 29:
	*'''frameName:''' hit frame's name		*'''frameName:''' hit frame's name
	*'''worldX, worldY, worldZ:''' collision position in world space		*'''worldX, worldY, worldZ:''' collision position in world space

			==See Also==
			{{Client world functions}}

Pirulax: Create the page. Needs an example!

2023-09-23T17:32:56Z

Create the page. Needs an example!

New page

{{Client function}}
__NOTOC__
Does a raycast against an element's renderable mesh model [not the collision model!].
The same functionality is already present in [[processLineOfSight]], but the latter is a little buggy due to the fact that the collision model is always simplified, and not exactly the same as the mesh, which leads to situations where no hit is detected, even though the visible mesh is hittable [or vice versa].
Also, when one is interested in a specific element the overhead is a lot smaller [as we can skip all the collision detection done by the before-mentioned function].

==Syntax==
Return values labelled for ease of reference.
<syntaxhighlight lang="lua">
bool -- hit
float float -- texU, texV
string -- textureName
string -- frameName
float float float -- worldX, worldY, worldZ
processLineAgainstMesh(element toTest,
float startX, float startY, float startZ,
float endX, float endY, float endZ)
</syntaxhighlight>

===Required Arguments===
*'''toProcess:''' The element to process the line against
*'''startX, startY, startZ:''' The start [origin] of the line
*'''endX, endY, endZ:''' The end of the line

===Returns===
*'''hit:''' ''true'' if there is a collision with the given element's mesh, ''false'' otherwise [in which case all other values are nil]
*'''texU, texV:''' the U, V coordinates on the hit geometry's texture
*'''textureName:''' name of the hit geometry's texture
*'''frameName:''' hit frame's name
*'''worldX, worldY, worldZ:''' collision position in world space