I recently got a new setup with 16 GB of RAM, a 3080 and a Ryzen 9 and I can only seem to manage like 200 FPS? When I've seen people with an i5 and like 4 GB allocated manage to get 400-500 FPS while recording..? Are my settings just screwed or am I dumb-
In-game settings, especially render distance? Render distance has a huge impact on FPS since the rendered areas increases by the square of the distance; 16 chunks is 4 times the area of 8 chunks and 32 chunks is 16 times the area (instead of 2 and 4 times), and while FPS may not be directly proportional to this it is still significant (I see more of a 2-3x decrease from 8-16 chunks, and this can be more significant if much of the visible area is hidden behind mountains, etc as the game doesn't render what is behind them, hence FPS is higher when underground), other factors that significantly affect FPS include entities (example without and with 100 chickens - which lowers FPS on a default Superflat world at 8 chunks more than 16 chunks on a normal world) and tile entities that use "entity" rendering, particularly chests; if you have a large storage room you may want to use barrels instead. The exact impact of any single thing also varies with the computer and game version (newer versions are more multithreaded, though actually rendering to the screen is still single-threaded; some things may render faster or slower in different versions due to rewrites of the rendering code); dynamic FPS is also highly affected by the complexity of rendered chunks (the more chunk updates the lower the FPS, with particularly complex chunks causing noticeable single lag spikes); all these factors are why a built-up world gets lower FPS than a new world, or an unbuilt area of the same world.
I recently got a new setup with 16 GB of RAM, a 3080 and a Ryzen 9 and I can only seem to manage like 200 FPS? When I've seen people with an i5 and like 4 GB allocated manage to get 400-500 FPS while recording..? Are my settings just screwed or am I dumb-
What you believe is what you experience.
In-game settings, especially render distance? Render distance has a huge impact on FPS since the rendered areas increases by the square of the distance; 16 chunks is 4 times the area of 8 chunks and 32 chunks is 16 times the area (instead of 2 and 4 times), and while FPS may not be directly proportional to this it is still significant (I see more of a 2-3x decrease from 8-16 chunks, and this can be more significant if much of the visible area is hidden behind mountains, etc as the game doesn't render what is behind them, hence FPS is higher when underground), other factors that significantly affect FPS include entities (example without and with 100 chickens - which lowers FPS on a default Superflat world at 8 chunks more than 16 chunks on a normal world) and tile entities that use "entity" rendering, particularly chests; if you have a large storage room you may want to use barrels instead. The exact impact of any single thing also varies with the computer and game version (newer versions are more multithreaded, though actually rendering to the screen is still single-threaded; some things may render faster or slower in different versions due to rewrites of the rendering code); dynamic FPS is also highly affected by the complexity of rendered chunks (the more chunk updates the lower the FPS, with particularly complex chunks causing noticeable single lag spikes); all these factors are why a built-up world gets lower FPS than a new world, or an unbuilt area of the same world.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?