I think this belongs in the unmodified client? Not 100% sure. I use MC Patcher and texture packs, and that's it. If it needs to be moved to the Modified Client forum, that's understandable.
I have 1.5.1 approved Texture Pack (FaerieLights), and MC Patcher 3.0.3_01
What happens is one or the other:
Black Screen after the Mojang logo (when the texture pack is active I think). If the texture pack is inactive and I go to activate it, I get a grey screen followed by the crash report.
This is the error report I get:
---- Minecraft Crash Report ----
// Don't be sad, have a hug! <3
Time: 4/20/13 3:42 AM
Description: Rendering screen
java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferInt.<init>(Unknown Source)
at java.awt.image.Raster.createPackedRaster(Unknown Source)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(Unknown Source)
at java.awt.image.BufferedImage.<init>(Unknown Source)
at bip.b(SourceFile:254)
at bis.b(SourceFile:154)
at bgf.d(SourceFile:350)
at bgf.c(SourceFile:301)
at bjy.a(SourceFile:146)
at axt.a(SourceFile:175)
at bjx.a(SourceFile:109)
at bfr.b(SourceFile:768)
at net.minecraft.client.Minecraft.K(SourceFile:597)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at java.awt.image.DataBufferInt.<init>(Unknown Source)
at java.awt.image.Raster.createPackedRaster(Unknown Source)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(Unknown Source)
at java.awt.image.BufferedImage.<init>(Unknown Source)
at bip.b(SourceFile:254)
at bis.b(SourceFile:154)
at bgf.d(SourceFile:350)
at bgf.c(SourceFile:301)
at bjy.a(SourceFile:146)
at axt.a(SourceFile:175)
at bjx.a(SourceFile:109)
-- Screen render details --
Details:
Screen name: bjx
Mouse location: Scaled: (192, 145). Absolute: (768, 497)
Screen size: Scaled: (480, 270). Absolute: (1920, 1080). Scale factor of 4
Stacktrace:
at bfr.b(SourceFile:768)
at net.minecraft.client.Minecraft.K(SourceFile:597)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)
-- System Details --
Details:
Minecraft Version: 1.5.1
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_11, Oracle Corporation
Java VM Version: Java HotSpotâ„¢ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 407412056 bytes (388 MB) / 873136128 bytes (832 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -Xms512m -Xmx1024m
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: [com.prupe.mcpatcher.MCPatcherUtils, Config, MCLogger, ...], [com.prupe.mcpatcher.mod.ColorizeItem, AAHelper, TessellatorUtils, ...]
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: GeForce GTX 570/PCIe/SSE2 GL version 4.3.0, NVIDIA Corporation
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Texture Pack: 1.5 Faerielight 256x256 v1a.zip
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
Out of Memory usually means it ran out of RAM...
and yes this should be under modified client, anything that involves opening the jar and replacing stuff is considered modded i think.
Redpower 2, Industrial Craft 2, Buildcraft, Forestry, Extra Bees, Logic Pipes, EnderChests, IronChests, Thermal Expansion, Teleport pipes, and the must have ComputerCraft
I don't think it's the Memory. I've allocated 3GB to Java and it's still doing this. Though oddly, Java had wiped my previous setting and I had to reset it, but unfortunately it didn't fix my issue.
BTW: On the rare occasions I can get to the main menu with the Texture pack enabled, I just get 1FPS. It's not my computer, it's plenty fast for running 256x256 texture packs (I've done it a lot before this update).
I have 1.5.1 approved Texture Pack (FaerieLights), and MC Patcher 3.0.3_01
What happens is one or the other:
Black Screen after the Mojang logo (when the texture pack is active I think). If the texture pack is inactive and I go to activate it, I get a grey screen followed by the crash report.
This is the error report I get:
and yes this should be under modified client, anything that involves opening the jar and replacing stuff is considered modded i think.
what other things did you add to your jar?
I don't think it's the Memory. I've allocated 3GB to Java and it's still doing this. Though oddly, Java had wiped my previous setting and I had to reset it, but unfortunately it didn't fix my issue.
BTW: On the rare occasions I can get to the main menu with the Texture pack enabled, I just get 1FPS. It's not my computer, it's plenty fast for running 256x256 texture packs (I've done it a lot before this update).
GTX 570 x2
6GB Ram