SetFPSLimit - Revision history

Azure at 17:13, 2 July 2025

2025-07-02T17:13:48Z

← Older revision		Revision as of 17:13, 2 July 2025
Line 52:		Line 52:

	if (setNewFPS) then		if (setNewFPS) then
	outputChatBox("Your FPS ~~has~~ been limited to: " .. newFPS .. ".")		outputChatBox("Your FPS have been limited to: " .. newFPS .. ".")
	setFPSLimit(newFPS)		setFPSLimit(newFPS)
	end		end

2025-06-27T01:06:44Z

← Older revision		Revision as of 01:06, 27 June 2025
Line 39:		Line 39:

	if not newFPS then		if not newFPS then
	outputChatBox("Syntax: /"..commandName.." [FPS] - to limit your own FPS.")		outputChatBox("Syntax: /" .. commandName .. " [FPS] - to limit your own FPS.")
	return false		return false
	end		end
Line 52:		Line 52:

	if (setNewFPS) then		if (setNewFPS) then
	outputChatBox("Your FPS has been limited to: "..newFPS..".")		outputChatBox("Your FPS has been limited to: " .. newFPS .. ".")
	setFPSLimit(newFPS)		setFPSLimit(newFPS)
	end		end

2025-06-27T01:06:01Z

← Older revision		Revision as of 01:06, 27 June 2025
Line 35:		Line 35:
	<section name="Client" class="client" show="true">		<section name="Client" class="client" show="true">
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	~~local minFPS = 25~~
	~~local maxFPS = 100~~

	function fpsFunction(commandName, fpsLimit)		function fpsFunction(commandName, fpsLimit)
	local newFPS = tonumber(fpsLimit)		local newFPS = tonumber(fpsLimit)
	~~local displaySyntax = (not newFPS) or (newFPS < minFPS) or (newFPS > maxFPS)~~

	if ~~(displaySyntax)~~ then		if not newFPS then
	outputChatBox("Syntax: /"..commandName.." [~~"..minFPS.." ~ "..maxFPS.."~~] - limit your own FPS.")		outputChatBox("Syntax: /"..commandName.." [FPS] - to limit your own FPS.")
			return false
			end

			if newFPS < minFPS or newFPS > maxFPS then
			outputChatBox("Please enter a value between " .. minFPS .. " and " .. maxFPS .. ".")
	return false		return false
	end		end
Line 56:		Line 56:
	end		end
	end		end
	~~addCommandHandler("limitfps", fpsFunction)~~
	addCommandHandler("fpslimit", fpsFunction)		addCommandHandler("fpslimit", fpsFunction)
	</syntaxhighlight>		</syntaxhighlight>

2025-05-19T05:27:23Z

← Older revision		Revision as of 05:27, 19 May 2025
Line 12:		Line 12:

	===Required Arguments===		===Required Arguments===
	*'''fpsLimit:''' An integer value representing the maximum FPS. Refer to the note above for possible values. You can also pass '''0''' or '''false''', in which case the FPS limit will be the one set in the client settings (by default, '''100 FPS''' and the client fps limit should also be manually changed via "'''fps_limit=0'''" in console or '''MTA San Andreas\MTA\config\coreconfig.xml''').		*'''fpsLimit:''' An integer value representing the maximum FPS. Refer to the note above for possible values. You can also pass '''0''' or '''false''', in which case the FPS limit will be the one set in the client settings (by default '''100 FPS''' and the client fps limit should also be manually changed via "'''fps_limit=0'''" in console or '''MTA San Andreas\MTA\config\coreconfig.xml''').

	===Returns===		===Returns===

2025-04-18T12:08:19Z

Required Arguments

← Older revision		Revision as of 12:08, 18 April 2025
Line 12:		Line 12:

	===Required Arguments===		===Required Arguments===
	*'''fpsLimit:''' An integer value representing the maximum FPS. Refer to the note above for possible values. You can also pass '''0''' or '''false''', in which case the FPS limit will be the one set in the client settings (by default, '''100 FPS''' and the client fps limit should also be manually changed via "'''fps_limit=0'''" in console or '''MTA San Andreas ~~1.5~~\MTA\config\coreconfig.xml''').		*'''fpsLimit:''' An integer value representing the maximum FPS. Refer to the note above for possible values. You can also pass '''0''' or '''false''', in which case the FPS limit will be the one set in the client settings (by default, '''100 FPS''' and the client fps limit should also be manually changed via "'''fps_limit=0'''" in console or '''MTA San Andreas\MTA\config\coreconfig.xml''').

	===Returns===		===Returns===

2025-04-18T12:07:54Z

Example

← Older revision		Revision as of 12:07, 18 April 2025
Line 42:		Line 42:
	local displaySyntax = (not newFPS) or (newFPS < minFPS) or (newFPS > maxFPS)		local displaySyntax = (not newFPS) or (newFPS < minFPS) or (newFPS > maxFPS)

	if displaySyntax then		if (displaySyntax) then
	outputChatBox("Syntax: /"..commandName.." ["..minFPS.." ~ "..maxFPS.."] - limit your own FPS.")		outputChatBox("Syntax: /"..commandName.." ["..minFPS.." ~ "..maxFPS.."] - limit your own FPS.")

Line 51:		Line 51:
	local setNewFPS = (newFPS ~= currentLimit)		local setNewFPS = (newFPS ~= currentLimit)

	if setNewFPS then		if (setNewFPS) then
	outputChatBox("Your FPS has been limited to: "..newFPS..".")		outputChatBox("Your FPS has been limited to: "..newFPS..".")
	setFPSLimit(newFPS)		setFPSLimit(newFPS)

2025-04-04T06:37:32Z

Fix for climbing over certain objects

← Older revision		Revision as of 06:37, 4 April 2025
Line 66:		Line 66:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function onClientPlayerDamage(attackerElement, damageType, bodyPart)		function onClientPlayerDamage(attackerElement, damageType, bodyPart)
	local fallDamage = damageType == 54		local fallDamage = (damageType == 54)

	if not fallDamage then		if (not fallDamage) then
	return false		return false
	end		end

	local playerTask = getPedSimplestTask(localPlayer)		local playerTask = getPedSimplestTask(localPlayer)
	local playerClimbing = playerTask == "TASK_SIMPLE_CLIMB"		local playerClimbing = (playerTask == "TASK_SIMPLE_CLIMB")

	if playerClimbing then		if (playerClimbing) then
	cancelEvent()		cancelEvent()
	end		end

2023-06-14T01:01:04Z

Fix for climbing over certain objects

← Older revision		Revision as of 01:01, 14 June 2023
Line 62:		Line 62:

	== Fix for climbing over certain objects==		== Fix for climbing over certain objects==
			You can use this small code to fix one of high FPS issues, specifically the one which would instantly kill player climbing over some objects.
	<section name="Client" class="client" show="true">		<section name="Client" class="client" show="true">
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

2023-06-14T00:59:24Z

Issues when increasing FPS

← Older revision		Revision as of 00:59, 14 June 2023
Line 26:		Line 26:

	* Pressing the horn button to turn on and off sirens gets really hard at very high FPS. For instance, at 100 FPS, you are more likely to hit the regular horn 3 times (inconsistent) before eventually triggering the siren, besides taking a similar amount of tries to turn off the siren.		* Pressing the horn button to turn on and off sirens gets really hard at very high FPS. For instance, at 100 FPS, you are more likely to hit the regular horn 3 times (inconsistent) before eventually triggering the siren, besides taking a similar amount of tries to turn off the siren.
	* At very high FPS, climbing over certain objects will result in instant death. Example at: 2520.108, -1681.407, 19.406, 266		* At very high FPS, climbing over certain objects will result in instant death. Example at: 2520.108, -1681.407, 19.406, 266 - [https://wiki.multitheftauto.com/wiki/SetFPSLimit#Fix_for_climbing_over_certain_objects you can use this Lua code to fix it.]
	* The higher your FPS, the more of a penalty in satchel throwing distance (up to ~10% at very high FPS) will apply.		* The higher your FPS, the more of a penalty in satchel throwing distance (up to ~10% at very high FPS) will apply.

2023-06-14T00:58:15Z

Add fix for climbing certain objects.

@@ Line 58: / Line 58: @@
 addCommandHandler("limitfps", fpsFunction)
 addCommandHandler("fpslimit", fpsFunction)
 </syntaxhighlight>
 </section>