256x and 512x crash

[jamjarz]

I have read the FAQ and attempted other solutions (running the game from the .minecraft folder with a .bat, increasing priority, increasing RAM allocation in the launcher etc). After trying the previously mentioned solutions, I still get 'Minecraft has run out of memory' on startup. Any solutions to this?

[BradleyRWatson]

You need to allocate more RAM (Memory). If it's on 1.8 you might need quite a beefy comp. Only some with 32gb's of RAM and rarely 16gb's have been able to run 512x and 256x.

[jamjarz]

You need to allocate more RAM (Memory). If it's on 1.8 you might need quite a beefy comp. Only some with 32gb's of RAM and rarely 16gb's have been able to run 512x and 256x.

I have a high end pc (16 gb RAM, 64- bit win7, gtx 780, i7) and I have been able to run these textures on previous lower end builds with the same amount of RAM.

[HanFox]

How much RAM are you actually providing and what version of MC are you running?

As you have previously been told packs in MC1.8 need a lot more RAM then before due to poor optimization in Minecraft itself.

[xaruum]

Hello,

I am running in to this as well. Never had a problem running x512 before. I have tested several other x512 packs with 1.8.1 now as well with no problems what so ever - and those packs are actually much larger. My pc is i7-870 16GB R9-290x4GB. My launcher uses only the options "-Xmx8196M -Xms8196M". Also running MCpatcher 5.0.0_01.

Here is the 1 error that keeps popping up in the Java Console every time in both x256 and x512 even if I set the Java Memory options to 12Gb::

Show

---- Minecraft Crash Report ----
// Don't be sad. I'll do better next time, I promise!

Time: 12/21/14 2:15 PM
Description: Initializing game

ctz: Unable to fit: minecraft:items/gold_nugget - size: 512x512 - Maybe try a lowerresolution resourcepack?
at ctw.c(SourceFile:60)
at cua.b(SourceFile:197)
at cua.a(SourceFile:77)
at cxh.j(SourceFile:553)
at cxh.a(SourceFile:139)
at cxk.a(SourceFile:23)
at cvt.a(SourceFile:99)
at bss.ak(SourceFile:440)
at bss.a(SourceFile:302)
at net.minecraft.client.main.Main.main(SourceFile:124)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
at ctw.c(SourceFile:60)
at cua.b(SourceFile:197)
at cua.a(SourceFile:77)
at cxh.j(SourceFile:553)
at cxh.a(SourceFile:139)
at cxk.a(SourceFile:23)
at cvt.a(SourceFile:99)
at bss.ak(SourceFile:440)

-- Initialization --
Details:
Stacktrace:
at bss.a(SourceFile:302)
at net.minecraft.client.main.Main.main(SourceFile:124)

-- System Details --
Details:
Minecraft Version: 1.8.1
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 5825862520 bytes (5555 MB) / 8236040192 bytes (7854 MB) up to 8236040192 bytes (7854 MB)
JVM Flags: 3 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx8196M -Xms8196M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8.1
LWJGL: 2.9.1
OpenGL: AMD Radeon R9 200 Series GL version 4.4.13283 Compatibility Profile Context 14.501.1003.0, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Using VBOs: No
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: [Sphax PureBDcraft 512x MC18.zip]
Current Language: English (US)
Profiler Position: N/A (disabled)
#@!@# Game crashed! Crash report saved to: #@!@# C:\Users\Rudy\AppData\Roaming\.minecraft\crash-reports\crash-2014-12-21_14.15.27-client.txt
[14:15:27] [Client Shutdown Thread/INFO]: Stopping server
AL lib: (EE) alc_cleanup: 1 device not closed
--------------------------------------------------------

It is just the gold nugget that keeps tripping the system. Is that particular texture corrupted?

[HanFox]

It is just the gold nugget that keeps tripping the system. Is that particular texture corrupted?

It means you don't have enough RAM available to Minecraft. Either assign more or use lower resolution textures.

[ChaoGirDja]

It is just the gold nugget that keeps tripping the system. Is that particular texture corrupted?

It means you don't have enough RAM available to Minecraft. Either assign more or use lower resolution textures.

He hase said, that he uses other x512-RP-Packs with no issue...
Maybe Sphax has done something wrong?...

[HanFox]

Sphax has added a lot of custom models, which add a lot of custom textures and Minecraft just isn't cut out to handle them very well.

Generally it appears you need to have at least 32GB to run 512x, and 16GB+ for 256x (and quite possibly having to use Linux instead of Windows). After that requirements drop off fairly quickly to about 3GB for 128x and less for others.

It's an issue with Minecraft with HD textures and models.

If you can find fault in the files or the way Sphax has done things (baring in mind he's written an entire program that actually optimizes the Minecraft models supplied in MC1.8 before even adding textures) feel free to share. I'm not saying Sphax is infallible but he seems pretty on-the-pulse when it comes to MC vanilla features.