• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Enough to run Minecraft?

Homerboy

Lifer
Trying to cobble together some old parts for my son/daughter so they can have their own PC to play minecraft.

Basically I have:

AMD 5600+
2GB RAM
Radeon 4350 512MB GPU

Slapping in an old Dell Dimension 521 MB/Case running WinXP

Will that be enough to run MC?
 
Can't you run Minecraft on a toaster?

Nope, and thanks for adding absolutely nothing to this thread.

Lowest hardware I have ever attempted MC on was an Atom N270 netbook and it was of course unplayable.

The problem, IMO, is the heavy use of Java and although you can run the 64 bit client, it still can be heavy on RAM usage, especially if using texture packs. As each new chunk is generated, it hits the CPU hard and can cause huge lag spikes while exploring.

For what you get on the screen, Minecraft is actually a very inefficient game. I have a laptop with an i7 3615 HD4000/GT630M and I have to get the nV chip involved to make the game really playable.
 
Nope, and thanks for adding absolutely nothing to this thread.

Lowest hardware I have ever attempted MC on was an Atom N270 netbook and it was of course unplayable.

The problem, IMO, is the heavy use of Java and although you can run the 64 bit client, it still can be heavy on RAM usage, especially if using texture packs. As each new chunk is generated, it hits the CPU hard and can cause huge lag spikes while exploring.

For what you get on the screen, Minecraft is actually a very inefficient game. I have a laptop with an i7 3615 HD4000/GT630M and I have to get the nV chip involved to make the game really playable.
The problem isn't Java per say but inefficient coding.
 
Nope, and thanks for adding absolutely nothing to this thread.

Lowest hardware I have ever attempted MC on was an Atom N270 netbook and it was of course unplayable.

The problem, IMO, is the heavy use of Java and although you can run the 64 bit client, it still can be heavy on RAM usage, especially if using texture packs. As each new chunk is generated, it hits the CPU hard and can cause huge lag spikes while exploring.

For what you get on the screen, Minecraft is actually a very inefficient game. I have a laptop with an i7 3615 HD4000/GT630M and I have to get the nV chip involved to make the game really playable.

to be fair, that's what the graphics chip is there for. the hd4000 is fine for video playback, but hopeless for any game i'd want to play.
 
Nope, and thanks for adding absolutely nothing to this thread.

Lowest hardware I have ever attempted MC on was an Atom N270 netbook and it was of course unplayable.

The problem, IMO, is the heavy use of Java and although you can run the 64 bit client, it still can be heavy on RAM usage, especially if using texture packs. As each new chunk is generated, it hits the CPU hard and can cause huge lag spikes while exploring.

For what you get on the screen, Minecraft is actually a very inefficient game. I have a laptop with an i7 3615 HD4000/GT630M and I have to get the nV chip involved to make the game really playable.

You're welcome! Whodathunk a terrible looking game needed more hardware?
 
Back
Top