What's the proper way to document and report the black screen issue? I think a lot of people call this a "crash", and it's what I'm getting every session now, after 5-15 minutes of play, since the Halloween update. I'm on the verge of just quitting it altogether.
In the previous version, the black screen would be followed by Minecraft's crash reporting screen. It's just a matter of patience. If it never shows up after a couple minutes, well we're all SOL.
Like I said, I don't get any crashes since this update... so if someone could actually give me a crash dump from something that can be consistently manifested, that would be great and I can look into fixing that. Just telling me that you crash does absolutely no good.
Now that this forum is back up, I can say that I am not crashing at all in this new update... seems at least for me there is not a need for this type of fix. If any of you are still crashing in a similar manner despite the Halloween update, give me your full crash dump and I'll try to see if it is indeed related.
If you apply this fix to the files of the Halloween update, you will encounter problems because fz.class is no longer the same as it was before. Do NOT apply it to the Halloween-updated client!
After extensive testing in single player and online, I can report that this does not work at all. I still get the black screen every few minutes when not in Normal rendering mode.
If you're not getting a crash dump, you're not crashing in any sort of way that this mod will fix. If you do get a crash dump, paste it for me.
There are a handful of different socket errors and this only addresses 1 kind (which is what it manifests as, from the server perspective), but does handle this particular render crash for those who have it.
Which crash exactly? It would help if you paste the entire thing.
If you do not have a /META-INF directory in your minecraft.jar, you're talking about a non-standard installation or you are modifying the wrong jar. A fresh download of the game DOES have this directory so whatever your situation is, you can consider it unsupported currently.
guys i replaced it using 7 zip (without making a back up becuase im stupid like that lol)
This is what i get i cant go on multiplayer SMP's but i can go on singleplayer... :sad.gif:
java.lang.SecurityException: SHA1 digest error for fz.class
at sun.security.util.ManifestEntryVerifier.verify(Unknown Source)
at java.util.jar.JarVerifier.processEntry(Unknown Source)
at java.util.jar.JarVerifier.update(Unknown Source)
at java.util.jar.JarVerifier$VerifierStream.read(Unknown Source)
at sun.misc.Resource.getBytes(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$000(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at bn.a(SourceFile:152)
at e.a(SourceFile:942)
at iq.c(SourceFile:342)
at iq.b(SourceFile:284)
at net.minecraft.client.Minecraft.run(SourceFile:608)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 78947623 ----------
Anyone help? or give me a deafualt file so i can replace it again xD
This is why you need to delete the MOJANG files like the instructions say.
java.lang.SecurityException: SHA1 digest error for fz.class
at sun.security.util.ManifestEntryVerifier.verify(Unknown Source)
at java.util.jar.JarVerifier.processEntry(Unknown Source)
at java.util.jar.JarVerifier.update(Unknown Source)
at java.util.jar.JarVerifier$VerifierStream.read(Unknown Source)
at sun.misc.Resource.getBytes(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$000(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at e.a(SourceFile:263)
at iq.c(SourceFile:351)
at iq.b(SourceFile:284)
at net.minecraft.client.Minecraft.run(SourceFile:608)
at java.lang.Thread.run(Unknown Source)
How to use: Open minecraft.jar in your favorite archive program such as 7zip and replace the existing fz.class with this one. Also be sure to delete the MOJANG files located in /META-INF - leave the Manifest file!
java.lang.NullPointerException
at bs.a(SourceFile:24)
at ev.a(SourceFile:75)
at eu.a(SourceFile:193)
at dm.a(SourceFile:187)
at ly.a(ly.java:286)
at nj.c(SourceFile:86)
at net.minecraft.client.Minecraft.a(SourceFile:757)
at net.minecraft.client.Minecraft.i(SourceFile:1053)
at net.minecraft.client.Minecraft.run(SourceFile:589)
at java.lang.Thread.run(Thread.java:637)
Is it the same problem, or different?
Different - haven't seen that one myself but perhaps resolvable through the same or similar means as this particular crash fix.
0
Bukkit will be a change for the better
0
In the previous version, the black screen would be followed by Minecraft's crash reporting screen. It's just a matter of patience. If it never shows up after a couple minutes, well we're all SOL.
0
0
If you apply this fix to the files of the Halloween update, you will encounter problems because fz.class is no longer the same as it was before. Do NOT apply it to the Halloween-updated client!
0
0
Your exact crash dump is...?
0
There are a handful of different socket errors and this only addresses 1 kind (which is what it manifests as, from the server perspective), but does handle this particular render crash for those who have it.
0
0
There is a Mac client modding guide somewhere in this subforum, I would start with that.
0
If you do not have a /META-INF directory in your minecraft.jar, you're talking about a non-standard installation or you are modifying the wrong jar. A fresh download of the game DOES have this directory so whatever your situation is, you can consider it unsupported currently.
0
This is why you need to delete the MOJANG files like the instructions say.
0
0
0
He's slightly sloppy, in many places of his code - it adds up... this is just a bandaid and a simple one at that.
0
Different - haven't seen that one myself but perhaps resolvable through the same or similar means as this particular crash fix.