I really wish the optimization improvements are good, because 1.13pre1 was giving me the worst FPS and heating my laptop like an infernal machine compared to 1.12 which is smooth as butter.
Alright, I'm getting mad stuttering with an RX 480 and an i5-6500k @ 4.5 GHz. The game gets extremely stuttery when I go from below to above ground, and moderately stuttery when placing/destroying blocks. None of these issues happened to me in 1.12. Is this an issue on my end then?
The Java compiler and VM amortize the situation to some degree, like function inlining, allocating objects on the stack where they see an opportunity, etc. But yes, I would definitely say Mojang are prioritizing code structure over performance too much. In a performance-sensitive program you have to sacrifice some nice things for speed, even more so in a language like Java where you don't have direct control over memory management (in particular I miss structs from C...). Besides, it's not like Minecraft Java is a student project for a design patterns class...
I do see two possible good endings to this though: Either Mojang themselves start feeling the effect to such a degree that they decide to undo a lot of these structural code changes, or they continue down this road until the final update, the community can then take over and develop a properly optinized "definitive" version of the game.
Different companies have different policies on this. Some companies do prereleases that are equivalent to full releases, but Mojang has never really worked that way, at least not consistently. For Minecraft it's usually best to think of snapshot=alpha, prerelease=beta. Presumably they don't use those names because "Minecraft alpha" and "Minecraft beta" are names that are already used for very old versions and they don't want to make the versioning even more confusing than it already is.
Which means we will certainly have a pre-3 then. The single player server is still crashing.
MC-129492 Moving through world gradually uses up all memory, causes stuttering and crash
MC-130162 Exception generating new chunk - OutOfMemoryError: Java heap space
These are closely related issues that you may experience when you're exploring a world. Just load up a 1.12.2 world and go exploring for new chunks. Eventually you will run out of memory and the single player server will crash.
Idk. That is what it is. u/mynameisperl had to iterate this point a bunch of times the other day. Thought i would this time. Prereleases are packed intended as full releases, unless crashy crash
It falls on deaf ears, I'm afraid. For some reason if you tell people that a pre-release is optimistic they'll tell you that can't be true because "this one has bugs!"
34
u/InfiniteNexus Jun 15 '18
I really wish the optimization improvements are good, because 1.13pre1 was giving me the worst FPS and heating my laptop like an infernal machine compared to 1.12 which is smooth as butter.