Postagem 1–7 de 7
1
por
Firefly3 anos atrás
I don't think there's any reason why a single block of water would cause problems. You can try lowering the 'view distance' menu option to see if it makes a difference. Other than that I'm pretty sure watery areas are no different compared to non-watery areas. Can you record and send me a video of this problem happening in real-time?
por
Leyenda3 anos atrás
If I would like to demonstrate it in a video about how it slows down the game where there is water but apparently it doesn't let me record either in an app, it gets too slow and takes me out of the game. What I know for now is that where there is a lot of water, the game is slow, I don't know why it's weird and then apparently my phone can't hold it and it appears that the system interface doesn't respond.
por
Firefly3 anos atrás
The goalpost subtly moved from 'water' to 'a lot of water'. Without seeing it in action, my best guess is that the animation of the many water blocks is overloading one of your CPU cores, which in turn lags the kernel and/or other threads like the network interface. Currently the only way to reduce load on your CPU is to reduce the view distance, with the idea being that less water = less animation = more processing power left over for everything else. Let me know if this actually works out. There's also not much I can really do about this. The water animation is very efficient, especially for ARM-based CPUs.
Postagem 1–7 de 7
1
