Aaron Bell
Comments
Hi Jonathan. In my tests I noted that the Max FPS slider directly impacted the chunk updates number. This seems a good measurable metric.
In your screenshot I see chunk updates=8, which is low. Could you do a test to see if that number changes when you set your Max FPS slider at different places?
I believe this is actually linked to the Max FPS setting, not vsync (though vsync has a secondary effect).
1.7.2 suffers from slow chunk updates. After watching http://www.youtube.com/watch?v=yc565Rqt3lY and experimenting, it is clear that the Max FPS slider alone is directly linked to chunk updates.
If your Max FPS slider is set high - even if your client is totally incapable of reaching that FPS - your chunk updates will be crippled. The lower your max FPS slider, the better the chunk rate - even if you are not actually capping your FPS.
So the workaround is: set your Max FPS as low as you can tolerate.
Holes in the landscape are caused by slow chunk updates, as reported in the debug screen.
1.7.2 suffers from slow chunk updates. After watching http://www.youtube.com/watch?v=yc565Rqt3lY and experimenting, it is clear that the Max FPS slider alone is directly linked to chunk updates.
If your Max FPS slider is set high - even if your client is totally incapable of reaching that FPS - your chunk updates will be crippled. The lower your max FPS slider, the better the chunk rate - even if you are not actually capping your FPS.
So the workaround is: set your Max FPS as low as you can tolerate.
Hi Jonathan,
I just tried 14w17b, and chunk updates do seem dramatically slower than in stable 1.7.9: unloaded chunks everywhere no matter where I put the FPS slider.
Jonathan maybe you could try on 1.7.9 to compare results.
On the stable version 1.7.9 on my 8-core desktop:
Cap at 60 FPS or lower = chunk updates go as high as 850 ⚠️
Unlimited FPS = chunk updates are much lower, ranging 30-60 and never above 60.
Hence the idea that capping your FPS has a real effect on chunk updates.