Which one do you prefer ?!

[u/Human-Criticism4130]

I am trying to make an endless runner (not for commercial game) in Godot 3.6 similar to the the game "Subway Surfers" but in Minecraft style, but in the way I found there are lot more challenges than i expected.

This is just for fun and I do not own any copyright protected content from Minecraft and subway surfers

[u/Human-Criticism4130]

Thanks a lot for the explanation 🙏 I actually also used Mineways and cleaned up extra polygons, but my chunk spawning/despawning system is built a bit differently, so that might be where my performance issues come from. Also, I don’t have a GPU in my PC, so I’m not sure if the problem is my setup or my implementation. Do you have a playable demo or project available? I’d love to test it out to compare and see what’s causing the slowdown on my end.

[u/me6675 → u/Human-Criticism4130]

How would playing another game let you see what's causing the slowdown in your game? You should use the profilers built into Godot to identify performance issues.

[u/Human-Criticism4130 → u/me6675]

Yeah, I get what you mean 👍 I actually did try the Godot profilers, but since my PC doesn’t have a GPU I was curious to compare with a similar project. My thought was: if his game (with similar Minecraft-style geometry and endless spawning) runs much better on my machine, then I know my implementation is the issue. But if both run at the same FPS, then it’s probably just my hardware holding me back. That’s why I was asking about a demo 🙂

[u/me6675 → u/Human-Criticism4130]

Unless you have some exceptionally weak PC, this should be feasible to do at 60FPS with Godot, it's more than likely your implementation.

This kind of geometry is super simple and if spawning chunks is the issue you should see drops in FPS, not a constant low FPS. Calculating shadows here should be the largest performance drain.

You don't need a GPU to profile what actually takes the most resources. What did the profiler tell you?