3 ms·
Instead of open sourcing code, they should fix the Aquatic update. All Minecraft versions after 1.13 are literally unplayable for me (mid to high end gamer PC)
by Kenji 8y ago
Instead of open sourcing code, they should fix the Aquatic update. All Minecraft versions after 1.13 are literally unplayable for me (mid to high end gamer PC) due to freezes. Every 5 seconds, the game freezes for two seconds for me. Increasing RAM for the JVM was useless. After the update, the game needed more than 3GB of RAM when before it ran just fine on 1GB (I have 16GB of RAM so no problem there, but the game still freezes). I have never seen more broken updates except with Skype - which, now that I think about it, makes perfect sense, considering it's also from Microsoft.
Why would I use their game library when they ship such incredibly broken updates?
- yjftsjthsd-h 8y agoIf they open source that, then everyone else can fix their bugs. Of course, it would usually be wildly optimistic, but looking at with the mod scene has already done, I'm optimistic.
- myrandomcomment 8y ago1m people play the game with no issues. Did you open a support case? Did you open a bug? What’s the ID? Also giving more RAM to Java is a bad thing as GC can cause lag. I run 1.13.1 on an old AMD 2ghz under Windows 7 with a Nvidia cards from 2011 and get 30-90fps. Also runs fine on my 2017 MacBook and on an intel compute stick (i5, 4gb ram, Win10 on a 4K screen). Something else is your issue and you just see it in the game.
- Kenji 8y agoI updated my Nvidia graphics driver and that fixed the issue. It's probably a case of Minecraft using the OpenGL API wrong and the driver needing to compensate for this broken usage of the API.
- chungy 8y agoI would check to see if you have 32- or 64-bit Java installed. I've seen similar issues (years before 1.13 was a thing) due to 32-bit Java. Install 64-bit and should be good to go.
- Kenji 8y agoThe Java runtime is bundled with minecraft. I use 64-bit and I use the same JRE everyone else uses.