OnClientRender - Revision history

XNikoXD at 09:23, 26 October 2025

2025-10-26T09:23:02Z

← Older revision		Revision as of 09:23, 26 October 2025
Line 4:		Line 4:

	{{Warning\|		{{Warning\|
	This event and [[~~onClientPreRender~~]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.		This event [[onClientPreRender]], [[onClientPedsProcessed]] and [[onClientHUDRender]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.

	As a result, this event may cause severe lag and/or even crashes if not used cautiously.}}		As a result, this event may cause severe lag and/or even crashes if not used cautiously.}}

2025-06-01T17:47:25Z

formatting

← Older revision		Revision as of 17:47, 1 June 2025
Line 2:		Line 2:
	{{Client event}}		{{Client event}}
	This event is triggered every time GTA renders a new frame. It is required for the DirectX drawing functions, and also useful for other clientside operations that have to be applied repeatedly with very short time differences between them.		This event is triggered every time GTA renders a new frame. It is required for the DirectX drawing functions, and also useful for other clientside operations that have to be applied repeatedly with very short time differences between them.

			{{Warning\|
			This event and [[onClientPreRender]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.

			As a result, this event may cause severe lag and/or even crashes if not used cautiously.}}

	==Parameters==		==Parameters==
Line 18:		Line 23:
	addEventHandler("onClientRender", root, updateCamera)		addEventHandler("onClientRender", root, updateCamera)
	</syntaxhighlight>		</syntaxhighlight>

	~~==Warning==~~
	This event and [[onClientPreRender]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.

	~~As a result, this event may cause severe lag and/or even crashes if not used cautiously.~~

	==See Also==		==See Also==

2025-03-28T14:04:55Z

← Older revision		Revision as of 14:04, 28 March 2025
Line 12:		Line 12:
	This example makes the camera follow the player in a GTA2-like way. This will be a little bit laggy. If you want the camera to follow something (eg. player or vehicle) then use [[onClientPreRender]] instead.		This example makes the camera follow the player in a GTA2-like way. This will be a little bit laggy. If you want the camera to follow something (eg. player or vehicle) then use [[onClientPreRender]] instead.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function updateCamera ()		function updateCamera()
	local x, y, z = getElementPosition ( localPlayer )		local x, y, z = getElementPosition(localPlayer)
	setCameraMatrix ( x, y, z + 50, x, y, z )		setCameraMatrix(x, y, z + 50, x, y, z)
	end		end
	addEventHandler ( "onClientRender", root, updateCamera )		addEventHandler("onClientRender", root, updateCamera)
	</syntaxhighlight>		</syntaxhighlight>

2024-05-26T18:37:08Z

Revert "onClientRender instead of onClientPreRender" (Mistake)

← Older revision		Revision as of 18:37, 26 May 2024
Line 20:		Line 20:

	==Warning==		==Warning==
	This event and [[~~onClientRender~~]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.		This event and [[onClientPreRender]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.

	As a result, this event may cause severe lag and/or even crashes if not used cautiously.		As a result, this event may cause severe lag and/or even crashes if not used cautiously.

2024-05-26T18:36:45Z

onClientRender instead of onClientPreRender

← Older revision		Revision as of 18:36, 26 May 2024
Line 20:		Line 20:

	==Warning==		==Warning==
	This event and [[~~onClientPreRender~~]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.		This event and [[onClientRender]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.

	As a result, this event may cause severe lag and/or even crashes if not used cautiously.		As a result, this event may cause severe lag and/or even crashes if not used cautiously.

2014-03-02T11:06:07Z

← Older revision		Revision as of 11:06, 2 March 2014
Line 18:		Line 18:
	addEventHandler ( "onClientRender", root, updateCamera )		addEventHandler ( "onClientRender", root, updateCamera )
	</syntaxhighlight>		</syntaxhighlight>

			==Warning==
			This event and [[onClientPreRender]] will trigger whatever function it is attached to with every frame. Depending on the server's maximum FPS and what your computer might handle - you might end up triggering the function 30-60 times '''per second'''.

			As a result, this event may cause severe lag and/or even crashes if not used cautiously.

	==See Also==		==See Also==

2013-06-29T21:52:09Z

← Older revision		Revision as of 21:52, 29 June 2013
Line 13:		Line 13:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function updateCamera ()		function updateCamera ()
	local x, y, z = getElementPosition ( ~~getLocalPlayer ()~~ )		local x, y, z = getElementPosition ( localPlayer )
	setCameraMatrix ( x, y, z + 50, x, y, z )		setCameraMatrix ( x, y, z + 50, x, y, z )
	end		end

2013-06-29T21:51:36Z

← Older revision		Revision as of 21:51, 29 June 2013
Line 12:		Line 12:
	This example makes the camera follow the player in a GTA2-like way. This will be a little bit laggy. If you want the camera to follow something (eg. player or vehicle) then use [[onClientPreRender]] instead.		This example makes the camera follow the player in a GTA2-like way. This will be a little bit laggy. If you want the camera to follow something (eg. player or vehicle) then use [[onClientPreRender]] instead.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	~~root = getRootElement ()~~
	function updateCamera ()		function updateCamera ()
	local x, y, z = getElementPosition ( getLocalPlayer () )		local x, y, z = getElementPosition ( getLocalPlayer () )

2012-04-20T02:41:07Z

Added a link to the game processing order page.

← Older revision		Revision as of 02:41, 20 April 2012
Line 21:		Line 21:

	==See Also==		==See Also==
			===[[Game_Processing_Order\|Game Processing Order]]===
	===Other client events===		===Other client events===
	{{Client_other_events}}		{{Client_other_events}}
	===Client event functions===		===Client event functions===
	{{Client_event_functions}}		{{Client_event_functions}}

2010-08-06T17:44:28Z

Example - happy now?!

← Older revision		Revision as of 17:44, 6 August 2010
Line 17:		Line 17:
	setCameraMatrix ( x, y, z + 50, x, y, z )		setCameraMatrix ( x, y, z + 50, x, y, z )
	end		end
	addEventHandler ( "~~onClientPreRender~~", root, updateCamera )		addEventHandler ( "onClientRender", root, updateCamera )
	</syntaxhighlight>		</syntaxhighlight>


	==See Also==		==See Also==