I'm getting a weird glitch where the sides of zombie and skeletons' heads are very bright, especially when hit that doesn't occur when it's un-patched.
Rollback Post to RevisionRollBack
"Some may say I'm 10 pounds of crap, but I'd say it's more like 11 and a half..."
I'm Getting a weird glich with MCpatcher and Misa's Texturepack. I installed the latest patcher and latest misa onto a fresh minecraft jar as usual when i update, log in and my performance is slashed down from an average of 70fps to 1 fps which has NEVER happend before when i use misa, and minecraft repeatedly crashes with patcher saying there is a memory allocation error, even though minecraft says it is using only 30% of it's allocated memory.. Help?
(using latest patcher and MC1.4.5 with current version of Misa's Realistic on Windows XP 5.1)
EDIT: Sorry, i fixed my issue- I was unaware that i had mipmapping enabled and apparently it was screwing everything up- when i noticed it and turned it off all of my issues vanished..
Still getting black screen each and every attempt. Mac Snow Leopard
Fresh MCPatcher download, fresh minecraft install, no mods, no options chanced from default MCPatcher.
Log when I test the patched client:
Launching /Users/DepthAfield/Library/Application Support/minecraft/bin/minecraft.jar
java -cp "/Users/DepthAfield/Library/Application Support/minecraft/bin/minecraft.jar:/Users/DepthAfield/Library/Application Support/minecraft/bin/lwjgl.jar:/Users/DepthAfield/Library/Application Support/minecraft/bin/lwjgl_util.jar:/Users/DepthAfield/Library/Application Support/minecraft/bin/jinput.jar:" "-Djava.library.path=/Users/DepthAfield/Library/Application Support/minecraft/bin/natives" -Xmx1024M -Xms512M net.minecraft.client.Minecraft
Exception in thread "main" java.lang.NoClassDefFoundError: com/pclewis/mcpatcher/TexturePackAPI$ChangeHandler
at ll.b(SourceFile:164) [Potion]
at ll.<clinit>(SourceFile:17)
at vs.<clinit>(SourceFile:74)
at uk.<clinit>(SourceFile:131)
at amj.<clinit>(SourceFile:335)
at bdb.<init>(SourceFile:14)
at net.minecraft.client.Minecraft.<init>(SourceFile:126)
at asi.<init>(SourceFile:36)
at net.minecraft.client.MinecraftApplet.init(SourceFile:36)
at net.minecraft.client.Minecraft.main(SourceFile:1670)
Caused by: java.lang.ClassNotFoundException: com.pclewis.mcpatcher.TexturePackAPI$ChangeHandler
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 10 more
Trying to play on a server that requires MCPatcher, and am feeling pretty out in the cold of late, because I cannot get past the very beginning of the use of your mod.
edit: If I kill the better sky option and then patch, I can get past the black screen. The new version (12/16?) looks to have solved the purple fire and lava issue, but the white artifacts surrounding distant torches is still happening. ONLY happens with MCPatcher running.
choc walker, to avoid an exceedingly long post, try putting your error report in a spoiler tag.
And i'd like to point out my issue one more time for the water rendering in the distance being really strange and would love to know as I'm about to do an LP series and I don't want to riddled with these odd bugs that many people will see.
Rollback Post to RevisionRollBack
Wisemen say forgiveness is divine, but never pay full price for late pizza.
I'm still getting the same problem that existed in MCPatcher 2.4.4. The options for mipmapping and water animations are still not changing how the game is patched. I have mipmapping unchecked in the patcher options, and it still gets applied. I also have water animations set to 'Default', since I'm using Faithful 32x32, but they aren't set to default in-game.
I'm still getting the same problem that existed in MCPatcher 2.4.4. The options for mipmapping and water animations are still not changing how the game is patched. I have mipmapping unchecked in the patcher options, and it still gets applied. I also have water animations set to 'Default', since I'm using Faithful 32x32, but they aren't set to default in-game.
Can confirm with MCPatcher 2.4.4_01.
Weird behaviour: When starting the minecraft.jar on one PC (Win 7-64, Java 7U9-64) mipmapping is switched off, but when starting the exactly same minecraft.jar on another PC (Win XP, Java 7U9-32) mipmapping is active.
Switching MipMapping on and off in the options doesn't have any effect, also deleting mcpatcher.xml and starting from scratch doesn't help.
Can confirm with MCPatcher 2.4.4_01.
Weird behaviour: When starting the minecraft.jar on one PC (Win 7-64, Java 7U9-64) mipmapping is switched off, but when starting the exactly same minecraft.jar on another PC (Win XP, Java 7U9-32) mipmapping is active.
Switching MipMapping on and off in the options doesn't have any effect, also deleting mcpatcher.xml and starting from scratch doesn't help.
Do you have the game installed somewhere besides the default location? Does this happen with both the Test Minecraft button and the normal Minecraft launcher?
If you use Test Minecraft, you should see this line in the log window:
<path> is where it is going to look for mcpatcher.xml, so if that's different from where the game actually is, it would explain why it can't find it.
Then run the the normal launcher from a cmd.exe window (java -jar Minecraft.jar) and look for the same line in that output. Post your results here and I'll see if I can get to the bottom of why this is happening.
Do you have the game installed somewhere besides the default location? Does this happen with both the Test Minecraft button and the normal Minecraft launcher?
If you use Test Minecraft, you should see this line in the log window:
<path> is where it is going to look for mcpatcher.xml, so if that's different from where the game actually is, it would explain why it can't find it.
Kahr,
thanks, you gave the final tip.
The problem was that there was no mcpatcher.xml on the PC of my wife.
My default procedure is to patch Minecraft on my PC (thus working) and copy just the minecraft.jar on the PC of my wife.
I thought up to now that the mcpatcher.xml only stores the settings for the patching process and isn't needed at runtime - lesson learned.
I have been looking around for an answer to my issue but haven't found one. I recently downloaded a fresh minecraft (wasn't enjoying my modded game anymore), I deleted my minecraft folder and my first plan was to patch my game so I could use my favorite texture packs.
I opened to fresh minecraft to make sure it worked then closed it. I next downloaded this patcher, following the instructions I patched my game, the log and whatnot said 'Done!' so I assumed it had properly worked. I opened minecraft once again and... nothing. A black screen for ever. Never giving a crash report or anything.
I was wondering if anyone could give an explanation to this odd result.
I have mcpatcher but when i press patch i let it do it's thing. then i open up minecraft and after i login in the screen is black any help. please i really need it.
Also if you are still reading please look up on youtube BlazingWolf731 and subscribe
Why would I subscribe to you? No offence, or anything, but seriously...
Hi. Not sure if this has been mentioned yet (forgive me if it has), but I've heard quite a few people wondering if an option could be added to the Custom Colors mod to allow custom durability bar colors. Would such a thing be possible?
Don't know if this has already been reported but the compass needle has a bug when a compass is in a frame.
When you look at a compass in a frame, the needle is displayed as default one for the compass you handle and the needle always stay as default one for the compass in a frame...
I have a couple of really dumb problems that I can't solve because I'm also really dumb:
- HD textures and Custom Colors is greyed out. I know it covers this in the troubleshooting but I can't seem to figure it out
-When I patch a texture pack in, it becomes the default, and the old default goes away. Not that big of a deal, but it'd be nice to know if theres an easy fix.
(using latest patcher and MC1.4.5 with current version of Misa's Realistic on Windows XP 5.1)
EDIT: Sorry, i fixed my issue- I was unaware that i had mipmapping enabled and apparently it was screwing everything up- when i noticed it and turned it off all of my issues vanished..
Fresh MCPatcher download, fresh minecraft install, no mods, no options chanced from default MCPatcher.
Log when I test the patched client:
Trying to play on a server that requires MCPatcher, and am feeling pretty out in the cold of late, because I cannot get past the very beginning of the use of your mod.
edit: If I kill the better sky option and then patch, I can get past the black screen. The new version (12/16?) looks to have solved the purple fire and lava issue, but the white artifacts surrounding distant torches is still happening. ONLY happens with MCPatcher running.
And i'd like to point out my issue one more time for the water rendering in the distance being really strange and would love to know as I'm about to do an LP series and I don't want to riddled with these odd bugs that many people will see.
are you able to check or uncheck them?
I stated this problem in a previous post, but it was ignored...
http://www.minecraftforum.net/topic/1496369-12w50b-145-132-etcupdate-1216-mcpatcher-hd-fix-244-01/page__st__6920#entry19702305
Can confirm with MCPatcher 2.4.4_01.
Weird behaviour: When starting the minecraft.jar on one PC (Win 7-64, Java 7U9-64) mipmapping is switched off, but when starting the exactly same minecraft.jar on another PC (Win XP, Java 7U9-32) mipmapping is active.
Switching MipMapping on and off in the options doesn't have any effect, also deleting mcpatcher.xml and starting from scratch doesn't help.
Do you have the game installed somewhere besides the default location? Does this happen with both the Test Minecraft button and the normal Minecraft launcher?
If you use Test Minecraft, you should see this line in the log window:
<path> is where it is going to look for mcpatcher.xml, so if that's different from where the game actually is, it would explain why it can't find it.
Then run the the normal launcher from a cmd.exe window (java -jar Minecraft.jar) and look for the same line in that output. Post your results here and I'll see if I can get to the bottom of why this is happening.
Kahr,
thanks, you gave the final tip.
The problem was that there was no mcpatcher.xml on the PC of my wife.
My default procedure is to patch Minecraft on my PC (thus working) and copy just the minecraft.jar on the PC of my wife.
I thought up to now that the mcpatcher.xml only stores the settings for the patching process and isn't needed at runtime - lesson learned.
Thanks a lot !
Kumasasa
I opened to fresh minecraft to make sure it worked then closed it. I next downloaded this patcher, following the instructions I patched my game, the log and whatnot said 'Done!' so I assumed it had properly worked. I opened minecraft once again and... nothing. A black screen for ever. Never giving a crash report or anything.
I was wondering if anyone could give an explanation to this odd result.
Should I post my Log information?
No, that's the problem.
I use Wolfcraft which is an HD texture pack, and i haven't had any problems. Do you have any mods besides what comes with MCPatcher?
Why would I subscribe to you? No offence, or anything, but seriously...
Hi there
When you look at a compass in a frame, the needle is displayed as default one for the compass you handle and the needle always stay as default one for the compass in a frame...
Creator of PureBDcraft and other things... https://BDcraft.net / @Sphax84 / @Cubik_Studio
- HD textures and Custom Colors is greyed out. I know it covers this in the troubleshooting but I can't seem to figure it out
-When I patch a texture pack in, it becomes the default, and the old default goes away. Not that big of a deal, but it'd be nice to know if theres an easy fix.
Help would be greatly appreciated, thanks!