How to make a FPS Counter

Resources Community Tutorials
,
#23

You’re right in saying I got the fps confused with the average fps as that was what the other guy was doing but I’ll put a reply to this post with an fps one

To address that edit, it wouldn’t be representative of the average FPS or the FPS at all as all the starting values for when you join the game will remain constant and would lead to the fps counter not updating properly.
Proof as to why its wrong:
https://gyazo.com/ffc2b9781fa54aeb7d91390bd9dfa858

2 Likes
#24 
local RunService = game:GetService("RunService")

local FrameQueue = table.create(100)

RunService.RenderStepped:Connect(function(dt)

table.insert(FrameQueue, 1)

task.wait(1)

table.remove(FrameQueue, 1)

script.Parent.Text = #FrameQueue

end)
2 Likes
#25

Why so there two periods between frames and “FPS””

2 Likes
#26

.. is the string concatenation operator.

local frames = 10

local str = frames .. " FPS"
print(str) -->> "10 FPS"
4 Likes
#27 

-- 1 / dT

local gui = script.Parent
local format = "FPS: %.1f"

game:GetService("RunService").RenderStepped:Connect(function(deltaTime)
	script.Parent.Text = string.format(format, 1 / deltaTime)
end)

-- frames += 1

local gui = script.Parent
local format = "FPS: %.1f"

local frames = 0

game:GetService("RunService").RenderStepped:Connect(function()
	frames += 1
end)

while task.wait(1) do
	gui.Text = string.format(format, frames)
	
	frames = 0
end

-- average fps (yours + slight tweaking)

local gui = script.Parent
local format = "FPS: %.1f"

local frameHistory = table.create(60, 0)
local index = 0

local function ComputeAverage()
	local average = 0

	for _, deltaTime in ipairs(frameHistory) do
		average += deltaTime
	end

	return average / 60
end

game:GetService("RunService").RenderStepped:Connect(function(deltaTime)
	index = (index + 1) % 61
	
	frameHistory[index] = deltaTime
	
	gui.Text = string.format(format, 1 / ComputeAverage())
end)

The scripts used for each gui are shown above, based on these results, we can draw a few conclusions:

  • 1 / dT is so bizarre it doesn’t even pick up the frame throttling that studio does by default when you unfocus the window, extending beyond studio and into a place where a player is experiencing a frame dip, they may not even know because their sporadic frame counter is saying 60 and 50, so it must be fine right?

  • Counting the frames seems to be the most accurate & readable at any given frame, and is efficient enough

  • Using the average framerate shows dip trends quicker, but less accurately about what’s going on in the current frame, and also may increase frametime on devices with weaker processors with all the table shifting going around just to count frames.

Also sorry about the quality of the video, that’s the best my recorder can go without freezing lol

19 Likes
#28

I’ll keep this in mind! Thankyou so much! :happy2:

2 Likes
#29

Glad that I could help! Have a amazing day. :happy3:

1 Like
#30

Glad I could help with your game. :happy3:

#31

I’m sorry if anyone had a problem or concern with this. I just tried to help some people that needed a quick minute Fps Counter. I know this isn’t the best and I’ll sure make it better next time. :happy1:

2 Likes
#32

Still I wanna see AN EXAMPLE of a module using this.

1 Like
#34

Your FPS Counter is not that accurate. You could easily make it more accurate by using task.wait(1) instead. I will come back with a better solution a little bit later when I have access to Studio.

1 Like
#35

Or you know, using actually reliable methods of counting fps?
There’s tons of posts that describe those more reliable methods. There’s even a official way of seeing your in-game fps that don’t rely on less reliable methods.
Also, wait() isn’t as evil as all of those ““top devs”” say.

2 Likes
#36

Thank You, This Really Helps Me! THANK YOU!

1 Like
#37

I’m confused…
why over-complicate this instead of just using

https://developer.roblox.com/en-us/api-reference/function/Workspace/GetRealPhysicsFPS

1 Like
#38

Because it’s not the actual framerate. It’s instead the framerate for the physics solver (which is very inaccurate, and hence the word “physics” in the function name.)

4 Likes
#39

No problem. Have a good day. :happy1:

#40

I’ll make a improved Fps Counter using that resource. Thankyou.

#41

Theres actually a better way to do this. Thats way simpler. And more accurate:

local FPSGui = script.Parent
while wait() do
	FPSGui.Text = "FPS: " ..   math.floor(workspace:GetRealPhysicsFPS()) -- gets the fps, and removes the decimals.
	
end
2 Likes
#42

That function returns the speed of which the physics system is running at, this is not what is being outputted and processed by the gpu
the api reference summarises this function as

Returns the number of frames per second that physics is currently being simulated at.

4 Likes
#43

Its for physics not graphical FPS.

2 Likes