Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

videocardz.com

Post reply on HN
Print view View original

41–50 of 85 posts

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#41

Post by bigyabai »

bspammer wrote: post #29
amarant wrote: post #12

Earlier quoted context omitted.

As one of the Devs responsible for the technical part of that transition: thank you. We tried real hard to give users the best possible experience, but I think it has nevertheless been the least appreciated piece of code I have ever written. So it's nice to finally hear some positive accounts from users! So, again, just thanks for saying this.

I paid for Minecraft and can no longer play it. I'm supposed to be thankful for this? If you choose to work for EvilCorp don't be surprised when you get assigned to work on tickets that make people unhappy.

When you "buy" anything digital, you're not ever owning it.

It's unfortunate, and Microsoft is no saint, but Mojang's depreciation was inevitable.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#42

Post by inigyou »

h4x0rr wrote: post #38
nesk_ wrote: post #17

It will only cost you $200 in RAM, definitely a good time to raise the minimum/recommended specifications.

It's only a change on paper, in reality it was unrealistically low for a long time

Is that ever since 1.8 made the whole game engine vastly less efficient? The game used to run with 256MB.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#43

Post by Filligree »

inigyou wrote: post #42
h4x0rr wrote: post #38

Earlier quoted context omitted.

It's only a change on paper, in reality it was unrealistically low for a long time

Is that ever since 1.8 made the whole game engine vastly less efficient? The game used to run with 256MB.

Less efficient but faster, which is a fun combination. At least they seem to have improved FPS.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#44

Post by cl3misch »

linker3000 wrote: post #7

Is this the evolution of something that used to run moderately well on a mid-range Raspberry pi? Don Priestley (Mazogs), stares down with a withering look.

Wasn't that the Bedrock edition? Or "Minecraft Education Edition"? An alternative C++ version, anyway.

I can't imagine Java Minecraft ever to have run well on a mid-range Raspi.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#45

Post by ezfe »

jandrese wrote: post #28
ezfe wrote: post #3

Earlier quoted context omitted.

I have lots of problems with Microsoft but the Minecraft transition was handled very responsibly.

I ran into problems because some time before the transition happened some bot use my email address to sign up for an XBox account, in German for some reason. So I have to first do an account takeover on some bot account that has been used for no doubt unsavory purposes meaning my Minecraft account is now tied to something that's likely to be randomly locked. Also, some communication has to be done in German because t…

> can I say what a mess the whole Microsoft account thing

absolutely agree

Fun fact, Xbox profiles can be disconnected from Microsoft accounts without doing 2FA verification. It's a whole problem right now.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#46

Post by Filligree »

jandrese wrote: post #28
ezfe wrote: post #3

Earlier quoted context omitted.

I have lots of problems with Microsoft but the Minecraft transition was handled very responsibly.

I ran into problems because some time before the transition happened some bot use my email address to sign up for an XBox account, in German for some reason. So I have to first do an account takeover on some bot account that has been used for no doubt unsavory purposes meaning my Minecraft account is now tied to something that's likely to be randomly locked. Also, some communication has to be done in German because t…

Using a third-party launcher (e.g. Prism) mostly fixes that nonsense, at least.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#47

Post by inigyou »

Nextgrid wrote: post #39
Sohcahtoa82 wrote: post #34

Earlier quoted context omitted.

1.6.4 released in 2013. I'm pretty sure I had 8 GB back then, possibly 16 GB. I can't imagine how poorly that ran.

He is probably referring to Beta 1.6.x. I remember running 1.7.3 in 2011-2012 on a potentially 1 or 2GB RAM machine and some Nvidia 7xxx series card (7600?). It worked fine on Linux.

No reason it couldn't be Not-Beta 1.6.x besides the 1.3 singleplayer server split, which doubled memory requirements, but 1GB was enough after the split.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#48

Post by inigyou »

bigyabai wrote: post #41
bspammer wrote: post #29

Earlier quoted context omitted.

I paid for Minecraft and can no longer play it. I'm supposed to be thankful for this? If you choose to work for EvilCorp don't be surprised when you get assigned to work on tickets that make people unhappy.

When you "buy" anything digital, you're not ever owning it. It's unfortunate, and Microsoft is no saint, but Mojang's depreciation was inevitable.

Notch's terms of sale were that you get access to every version of Minecraft forever.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#49

Post by inigyou »

cl3misch wrote: post #44
linker3000 wrote: post #7

Is this the evolution of something that used to run moderately well on a mid-range Raspberry pi? Don Priestley (Mazogs), stares down with a withering look.

Wasn't that the Bedrock edition? Or "Minecraft Education Edition"? An alternative C++ version, anyway. I can't imagine Java Minecraft ever to have run well on a mid-range Raspi.

Well it did used to run on early Raspis. Maybe you don't realise how much less efficient it's gotten? It used to run fine in 256MB with small render distance.

So how did they break that?

* run both server and client when in singleplayer - doubles memory use

* turn byte block IDs into object pointers - octuples memory use for blocks

* make all game content into JSON object trees with huge amounts of indirection - adds about a GB of objects deserialized at startup that used to be simple if/then ladders

* add a whole bunch of code to handle these object trees, don't know how much this adds but probably 100MB of code when you include the raw class files through to the JIT-optimized assembly.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#50

Post by Nicook »

functionmouse wrote: post #2

This might have impacted me, had Microsoft not deleted my legacy account. So I suppose I'll just stick to Tekkit Classic on my pirated client.

Made it through the account migration. But later lost my account after some hacker compromised my microsoft account. Microsoft kindly let me know about some unauthorized access, and then promptly deleted the account :) .

That was the last straw from Microsoft for me. Never again.

Post reply on HN