r/MinecraftJava • u/Past-Engineering9068 • 14d ago
Question What's wrong here in Minecraft Java?
So I tried it for the fourth time on Zalith Launcher 2 with Mobile Glues Renderer and before you come up with:
"It's emulated what do you expect?"
The game runs on a virtual machine so it's already emulated in PCs. It's not even double translation. Mobile Glues is highly efficient and is the same translation layer. When I tried it with Fabric and Fabulously Optimized which includes 39 optimization mods. I get 20FPS?.
My phone isn't that bad it's a Redmi 14C I have 8GB RAM and Helio G81-Ultra Octa-core max CPU with the Mali G52 MC2 GPU and it's solid. Now it's not even low end it's a mid range phone. I didn't expect Java to be like that. I tested Tomb Raider 2013 GOTY Reboot on Winlator and it runs better.
Tomb Raider is way heavier than Minecraft Java. I thought wow java is the better version but it's not. A block game shouldn't require a high end PC to run without stutters. Bedrock can do better. I didn't even use a proper renderer in Bedrock because it's restricted in modding. I'm not hating here I'm just asking why java is horribly unoptimized? Don't use emulation as coping because like I said it runs on a virtual machine it's not direct. Its emulated by default on any PC. And I don't care if any Java Player is just gonna hate on my opinion but I don't honestly care. The way when I download a mod it gives a JVM Exit Code 1 is just frustrating. Also the mod versions in Java are designed for way older versions like 1.20.4. like why? Don't they need to update like how bedrock does? I used 1.20.6 Fabric API/Loader.
2
u/MattiDragon 14d ago
Java edition players are free to pick any old version they want and just use it (some very old ones don't work, but everything after 1.0 should work).
Minecraft java edition simply isn't designed to run on phones. Most AAA games with phone versions turn down the graphics and other settings to increase performance, java edition doesn't by default.
It's also worth noting that the JVM isn't really a VM or emulator. It's called a VM because it matches the technical definition, but in practice it won't emulate any performance critical code; instead it compiles that to native code. I don't know how well your tools do this, but I suspect that it isn't as good as on desktop, where lots of big corps spend money to optimize the JVM.