On this beautiful #screenshotsaturday I did some benchmarking of Saturday Morning Marble Game.

Took my sandbox level and turned on ALL the marbles.

I easily reached the 360 max-FPS target at lowest settings with my 4080 being utilized ~35%. At highest settings, this shot up to 75% and FPS going down to 250.

Considering the ridiculous polycount of some meshes, this is really good. And I noticed utilization going DOWN as I moved away to get more meshes into view which means LOD does its job.

That the GPU never went to 100% is probably due to the game being essentially CPU bottlenecked. The game uses a VERY high physics tick rate (currently 90 times per second, but I may go back to 100) to keep the simulation stable. And tons of moving parts demand their CPU cycles, too.

And naturally the game being a sandbox with the player being able to manipulate everything means less optimization.

So whatever the CPU needs to do to aid the GPU will suffer a bit.

This is also why I don't fuss too much about polygon budget as the CPU will likely always be the bottleneck.

Now I am sure there are still things I could optimize if I knew better, but I can't will knowledge into my head. All I can do is read up, learn and try to apply that.

But being able to simulate a few hundred marbles and not drop below 60 FPS is what I consider a win.

@memoriesin8bit Your dedication to your game never fails to impress me!
@playmedusa Thank you. :)
I will say tho, there is probably some black magic I do not know about which a wizard could perform and easily run circles around what I am doing. But... I can only do what I know.