afreytes 🇵🇷

I have very simple Node3D scene on Godot Engine. It keeps instancing box meshes in random bounded positions until the FPS drops below 60 while the camera pivots around the scene. It has a label with a counter.

If you were making this on Godot Engine and using GDScript, what would you add to this scene to expand/improve the benchmark so that FPS drops faster?

No wrong answers, but it has to be doable with GDscript. The purpose is to tax the system until 60fps is hit, not crash it.

Nov 3 at 8:11pmWeb
Show threadHarvey SandstromNov 3
@afreytes You could add random point lights, though I imagine that you'll drop to 60 before you reach double digits. (Unless youre on Forward+ and the clustering saves you, in which case double digits should be doable.)
Show threaditsybitesyspiderNov 4
@afreytes Attach a script to the nodes so they update in some way every frame.
Show threadsanyaNov 4
@afreytes you can use physics in benchmark like balls in tank, maybe with manual impulse-based bouncing to prevent freezing.
Show threadOff The BooksNov 8
@afreytes right now this looks like it’s heavily weighted towards geometry count, but not necessarily fille rate which can be a bottle neck too.