I want to use a 256x256 texturepack and its exactly 135Mb big and everytime i start minecraft it crashes because of the resourcepack. I got an error log but i dont know what exactly the crash causes.
This is the logfile
---- Minecraft Crash Report ----
// Why did you do that?
Time: 03.07.13 02:19
Description: Registering texture
bhy
at bhv.c(SourceFile:58)
at bhz.b(SourceFile:92)
at bhz.a(SourceFile:59)
at bib.a(SourceFile:69)
at bib.a(SourceFile:58)
at bib.a(SourceFile:49)
at atn.O(SourceFile:377)
at atn.d(SourceFile:598)
at net.minecraft.client.main.Main.main(SourceFile:101)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at bhv.c(SourceFile:58)
at bhz.b(SourceFile:92)
at bhz.a(SourceFile:59)
-- Resource location being registered --
Details:
Resource location: minecraft:textures/atlas/blocks.png
Texture object class: bhz
Stacktrace:
at bib.a(SourceFile:69)
at bib.a(SourceFile:58)
at bib.a(SourceFile:49)
at atn.O(SourceFile:377)
-- Initialization --
Details:
Stacktrace:
at atn.d(SourceFile:598)
at net.minecraft.client.main.Main.main(SourceFile:101)
-- System Details --
Details:
Minecraft Version: 1.6.1
Operating System: Windows 7 (x86) version 6.1
Java Version: 1.7.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 50200688 bytes (47 MB) / 148299776 bytes (141 MB) up to 1037959168 bytes (989 MB)
JVM Flags: 1 total; -Xmx1G
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: No suspicious classes found.
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.6.1
LWJGL: 2.9.0
OpenGL: AMD Radeon HD 6650M GL version 4.1.10834 Compatibility Profile Context, ATI Technologies Inc.
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Pack: S.T.A.L.K.E.R 256x256 V5
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
Linked issues
is duplicated by 3
Attachments
Comments 4
What is wrong is that your system is incapable of creating the big texture needed to host all your 256x textures. You are simply using a too high-resolution texturepack.
The error you get is improved in the next version though.
Oh wow was the last comment so offensive? I am soooo sorry 😉
Well atleast you could write here how the problem was fixed. For other people who got eventual the same problem.
yeah well thanks but what does that exactly mean? Is that a number for a specific texture?
EDIT: I figured one thing out. It is caused from the /texture/blocks folder. If i remove 5 texture it runs the texturepack but if i add 1 texture back it crashes. The crash is not caused from a specific texture. What the hell is wrong? Is there now a limit how big texturepacks can be?
Help please 😞