My method to patch 32x textures, if u use huge amount of mods, like i )
First go in to "bin" folder, backup u "minecraft.jar" in to "minecraft.original.jar"
Then start "mcpatcher-1.1.9_04" (but better re-download u "minecraft.jar" on original) use options what u like. and of course 32x fix. press "patch"
Then unpack from u "minecraft.jar" so files: ad.class ae.class ba.class et.class ez.class fu.class is.class iz.class ku.class ln.class nq.class oe.class WaterAnimation.class and "net\minecraft\client\Minecraft.class"
in to folder 32xfix
Del u "minecraft.jar", creat a copy of u "minecraft.original.jar", rename copy in to "minecraft.jar"
and put all files from 32xfix in to "minecraft.jar"
Then change in "minecraft.jar" (or it will not work) terrain.png and gui\items.png on u 32x
one bug, clock not work correctly
In my situation, if i use "gp.class(Watch)" game crash! :smile.gif:
Rollback Post to RevisionRollBack
DF2MC - Convert Dwarf Fortress maps into Minecraft Maps!
My Ideas,My Minecraft Starter,My Easy Texture Pack Compiler,My Russian Translation,My BackUP Manager - My Easy Soft
The main problem I have with these higher-resolution textures is shimmer at shallow angles and at a distance, some give moire patterns or noise like crazy. I suspect we've all seen this problem. It's pretty easy to fix this if you can modify the java code, just use mipmapping. It takes changing two OpenGL calls and an addition of gluBuild2DMipmaps (and probably something else I'm forgetting...), read this article.
That said, I'm not a java decompilation/recreation whiz, so I'm hoping someone reading this forum who is will try out these easy changes. Mipmapping will blur the texture when seen from far away or at a shallow angle. It looks a lot better, and any modern game uses it. For example:
Technical guys wanting to try this, read on: I believe you'll want to use GL_NEAREST instead of GL_LINEAR for magnification, and GL_NEAREST_MIPMAP_LINEAR for minification, in glTexParameterf, as otherwise you'll sample off the block's texture and get nearby samples from other blocks. So the mipmaps will still show some noise between levels, but it should still improve the look, especially for higher resolution textures. You'll also want to limit how high up the mipmap pyramid you can go with gluBuild2DMipmaps (i.e. what you set for "max", see this call), since beyond a certain point you'll then be blurring together a number of blocks' textures (e.g. for a 16x16 you'd want to go just 4 levels up at most: 8x8, 4x4, 2x2, 1x1).
I hope this post inspires someone out there to try it out - the patcher should easily be able to add this as an option (hint, hint). Without mipmapping available I just don't use anything higher than 16x16 block tiles.
Alright: I figured out my problem (I think) by putting my 32x32 texture in a zip file. I selected it in mcpatcher and no error messages. But when I click "patch" it goes up to 22% and doesn't move. The "copy to clipboard" button won't respond either. Did I mess up? Thanks
EDIT: I tried the same thing again and it worked. Don't know why...
Rollback Post to RevisionRollBack
Minecraft is the bomb. And by bomb, i mean creeper.
GENERATION 24: The first time you see this, copy it into your sig on any forum and add 1 to the generation. Social experiment.
Now that SMP Health is out I was stoked to try the 256x256 patch option, only when launching the client after the "successful" patch, I get this:
--- BEGIN ERROR REPORT a1dce528 --------
Generated 11/24/10 8:24 PM
Minecraft: Minecraft Alpha v1.2.3_01
OS: Windows 7 (x86) version 6.1
Java: 1.6.0_22, Sun Microsystems Inc.
VM: Java HotSpot(TM) Client VM (mixed mode), Sun Microsystems Inc.
LWJGL: 2.4.2
OpenGL: ATI Radeon HD 5800 Series version 4.0.10243 Compatibility Profile Context, ATI Technologies Inc.
java.lang.ArrayIndexOutOfBoundsException: 262144
at es.<init>(SourceFile:50)
at net.minecraft.client.Minecraft.a(SourceFile:256)
at net.minecraft.client.Minecraft.run(SourceFile:563)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 5ce3bde8 ----------
The 128x128 works fine, though.
THANK YOU XAU YOU ARE A GOD
have you found a fix for that ? it also crashes here on any 256x texture pack !?
No fix. Even with the newest patcher I get something similar:
#### Success! ...probably ####
[java, -cp, C:\Users\Austin\AppData\Roaming\.minecraft\bin/minecraft.jar;C:\Users\Austin\AppData\Roaming\.minecraft\bin/lwjgl.jar;C:\Users\Austin\AppData\Roaming\.minecraft\bin/lwjgl_util.jar;C:\Users\Austin\AppData\Roaming\.minecraft\bin/jinput.jar, -Djava.library.path=C:\Users\Austin\AppData\Roaming\.minecraft\bin/natives, -Xmx1024M, -Xms512M, net.minecraft.client.Minecraft]
28
WARNING: Found unknown Windows version: Windows 7
Attempting to use default windows plug-in.
Loading: net.java.games.input.DirectAndRawInputEnvironmentPlugin
Starting up SoundSystem...
Initializing LWJGL OpenAL
(The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
OpenAL initialized.
java.lang.ArrayIndexOutOfBoundsException: 262144
at et.<init>(SourceFile:50)
at net.minecraft.client.Minecraft.a(SourceFile:252)
at net.minecraft.client.Minecraft.run(SourceFile:559)
at java.lang.Thread.run(Unknown Source)
starting without the mcpatcher launcher re-downloads the original files again
This shouldn't happen. Are you sure it's happening every time? Maybe there was just an oddly-timed update (or 3)?
Quote from Misa »
I can send what I have to you privately if it'd aid in your work though.
It would definitely help, I turned my PMs back on so you can send me something that way. If you have it in a format that would make creating animations easier I'd be interested in that too. I thought about gif but looks like you have varying transparencies too.
Quote from know15 »
Exception in thread "Minecraft main thread" java.lang.LinkageError: Version mismatch: jar version is '22', native libary version is '12'
at org.lwjgl.Sys.<clinit>(Sys.java:103)
This sounds like a Minecraft problem and not something this patcher has anything to do with.
Quote from Blackop2 »
java.lang.ArrayIndexOutOfBoundsException: 262144
at et.<init>(SourceFile:50)
This is something to do with the portals, I think it just was never tested for 256x256 (because 256x256 usually looks awful (and you should be ashamed for wanting to use it)) but I will look into it.
Quote from slothy89 »
I'm not that stupid.. I wouldn't post without falling those steps first. I've double and triple, even quadruple checked it's properly updated minecraft.
The log messages I quoted indicate that the minecraft.jar the patcher is reading and operating on is not the version it was created for when you ran it that time. Here's why:
Every time a Minecraft update adds new classes, some of the existing classes get different obfuscated names, usually one or two letters further in the alphabet. For everything except custom lava and water, the patcher does not care about the names. It looks for identifying things in the actual compiled bytecode: maybe the portal code says "Hey I'm a portal" somewhere, or maybe lava is drawn with a very specific algorithm, whatever.
The custom water and lava though use replacement classes for the 2 water and 2 lava animation classes. These are all new code and just dropped on top of the old ones. I have to manually change the names every time there is an update. So these log messages:
Found FlowLava: ey.class
Replacing ez.class
indicate that the patcher found the actual code that looks like the Flowing Lava code in ey.class. But when I compiled the patcher, I named it ez.class, because that's what it was in my minecraft.jar. So the log you posted shows, with 100% certainty, that the minecraft.jar you patched was not the same as the minecraft.jar the patcher was compiled for.
I realize this doesn't help you actually solve the problem, but there's not really anything else I can tell you. That's what's happening. If you've quadruple checked that everything is right, maybe you are getting a different error now without noticing.
Quote from copperdomebodha »
Do you think that you could modify this to also alter the offsets for /minecraft.jar/font/default.png file?
I'll look into it but no promises.
Quote from Tornament »
My method to patch 32x textures, if u use huge amount of mods, like i )
I assume you have a specific reason for doing this, but I just want to point out that, in general, pulling the patched class files out and treating them as opaque replacement classes will just make the patcher less compatible with other mods. The patcher dynamically determines what needs to be fixed, so if some mod makes minor changes to a class the patcher affects, the patcher will still work fine. If you use the whole class files and there is a collision, you will have to choose one class file or the other.
java.lang.ArrayIndexOutOfBoundsException: 262144
at et.<init>(SourceFile:50)
This is something to do with the portals, I think it just was never tested for 256x256 (because 256x256 usually looks awful (and you should be ashamed for wanting to use it)) but I will look into it.
Beauty is in the eye of the beholder :wink.gif: It's ok, xau, you're still my god for assuaging us HD crazies! I don't know where you are on the map, but I would so FedEx you a beer :biggrin.gif:
getting an error. load textures and get a black screen when i try to run the game..
texture packs iv tried to run are
BumpmaftV1_3_5.rar extracted and used the .jar
AzasAridTexPack.zip
and even a remake of the defalt at 128x128 as a template
and still each attempt after patching and running the game i just get a black screen after the logo
here is what i get in the patcher log.
#### Success! ...probably ####
[java, -cp, C:\Users\Danz\AppData\Roaming\.minecraft\bin/minecraft.jar;C:\Users\Danz\AppData\Roaming\.minecraft\bin/lwjgl.jar;C:\Users\Danz\AppData\Roaming\.minecraft\bin/lwjgl_util.jar;C:\Users\Danz\AppData\Roaming\.minecraft\bin/jinput.jar, -Djava.library.path=C:\Users\Danz\AppData\Roaming\.minecraft\bin/natives, -Xmx1024M, -Xms512M, net.minecraft.client.Minecraft]
28
WARNING: Found unknown Windows version: Windows 7
Attempting to use default windows plug-in.
Loading: net.java.games.input.DirectAndRawInputEnvironmentPlugin
Starting up SoundSystem...
Initializing LWJGL OpenAL
(The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
OpenAL initialized.
########## GL ERROR ##########
@ Pre render
1281: Invalid value
system specs are
Motherboard XFX G8300
AMD Phenom II X3 720 BE
3.5 gigs of random ram
random drives ranging from 160 Gig EIDE to
250 Gig SATA II
Nvidia Geforce GTX 460 OC
getting an error. load textures and get a black screen when i try to run the game..
texture packs iv tried to run are
BumpmaftV1_3_5.rar extracted and used the .jar
AzasAridTexPack.zip
and even a remake of the defalt at 128x128 as a template
and still each attempt after patching and running the game i just get a black screen after the logo
here is what i get in the patcher log.
#### Success! ...probably ####
[java, -cp, C:\Users\Danz\AppData\Roaming\.minecraft\bin/minecraft.jar;C:\Users\Danz\AppData\Roaming\.minecraft\bin/lwjgl.jar;C:\Users\Danz\AppData\Roaming\.minecraft\bin/lwjgl_util.jar;C:\Users\Danz\AppData\Roaming\.minecraft\bin/jinput.jar, -Djava.library.path=C:\Users\Danz\AppData\Roaming\.minecraft\bin/natives, -Xmx1024M, -Xms512M, net.minecraft.client.Minecraft]
28
WARNING: Found unknown Windows version: Windows 7
Attempting to use default windows plug-in.
Loading: net.java.games.input.DirectAndRawInputEnvironmentPlugin
Starting up SoundSystem...
Initializing LWJGL OpenAL
(The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
OpenAL initialized.
########## GL ERROR ##########
@ Pre render
1281: Invalid value
system specs are
Motherboard XFX G8300
AMD Phenom II X3 720 BE
3.5 gigs of random ram
random drives ranging from 160 Gig EIDE to
250 Gig SATA II
Nvidia Geforce GTX 460 OC
running windows 7 x64
oooooh...
########## GL ERROR ########## @ Pre render 1281: Invalid value
The game is trying to render textures at a different resolution than it was patched for. The patcher replaces the default Minecraft textures and this is the only supported use case at this time. Either delete options.txt or switch back to the default texture pack before patching. This will be fixed in future versions.
Hi guys. I used this fix last night and it took me a while to stop the "black screen" error. After searching through many pages of this thread, I found that some have gotten rid of the black screen by deleting their options folder. I renamed the folder and it worked. I then realized that the reason I was getting the black screen (and the open GL error) was because I had a texture pack that was enabled from the in-game menu. I restored my options folder, loaded MC and switched back to default textures (from the in-game menu) and repeated the install process and everything works fine. Author may want to put this in the first post. I don't recall seeing it there, probably because the in-game texture loader was recently implemented. I posted this to try to save other idiots like me some time. If this was mentioned in the OP, I apologize in advance for my stupidity.
The only way I can get my 128x128 texture pack to work is by putting it in minecraft.jar and then applying the patch. Please help! I want to be able to put my texture pack in the texture pack folder and NOT minecraft.jar. Please help!!!
I have a request. I want you to add in an option on your texture patcher for different sized paintings. I don't know if this is necessarily possible, but I would find it very useful if you did. The reason for this is that I recently made a new 128p art for my 32p texture, and it sadly didn't work. I don't want the time to go to waste. I'm sure others would also appreciate this.
And BobtheFat:
The reason you are getting this is because you are trying to pick a different minecraft.jar for the original, correct? After you do that it automatically trys to patch it. All you have to do is go into the %appdata% and put your minecraft.jar you want to patch there. If you were going to find your default and have the patcher install your textures automatically, it will have automatically found your minecraft.jar, you don't need to find it.
Rollback Post to RevisionRollBack
↑It makes sense if you don't think about it.↑
Creepers only explode because they want to hug you, but when they reach you, they realize they have no arms, and then explode with anger.
Now that SMP Health is out I was stoked to try the 256x256 patch option, only when launching the client after the "successful" patch, I get this:
--- BEGIN ERROR REPORT a1dce528 --------
Generated 11/24/10 8:24 PM
Minecraft: Minecraft Alpha v1.2.3_01
OS: Windows 7 (x86) version 6.1
Java: 1.6.0_22, Sun Microsystems Inc.
VM: Java HotSpot(TM) Client VM (mixed mode), Sun Microsystems Inc.
LWJGL: 2.4.2
OpenGL: ATI Radeon HD 5800 Series version 4.0.10243 Compatibility Profile Context, ATI Technologies Inc.
java.lang.ArrayIndexOutOfBoundsException: 262144
at es.<init>(SourceFile:50)
at net.minecraft.client.Minecraft.a(SourceFile:256)
at net.minecraft.client.Minecraft.run(SourceFile:563)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 5ce3bde8 ----------
The 128x128 works fine, though.
THANK YOU XAU YOU ARE A GOD
have you found a fix for that ? it also crashes here on any 256x texture pack !?
That doesn't work BECAUSE your computer Might not be good enough to run a 256x256 Pixels. I can't even run a 128x128 or above texture pack, cause my computer sucks so bad!
The Meaning of Life, the Universe, and Everything.
Join Date:
10/31/2010
Posts:
57
Minecraft:
WindowsBunny
Member Details
Quote from OoJUGG3RN4UToO »
Quote from nadine »
Quote from Xechorizo »
Now that SMP Health is out I was stoked to try the 256x256 patch option, only when launching the client after the "successful" patch, I get this:
--- BEGIN ERROR REPORT a1dce528 --------
Generated 11/24/10 8:24 PM
Minecraft: Minecraft Alpha v1.2.3_01
OS: Windows 7 (x86) version 6.1
Java: 1.6.0_22, Sun Microsystems Inc.
VM: Java HotSpot(TM) Client VM (mixed mode), Sun Microsystems Inc.
LWJGL: 2.4.2
OpenGL: ATI Radeon HD 5800 Series version 4.0.10243 Compatibility Profile Context, ATI Technologies Inc.
java.lang.ArrayIndexOutOfBoundsException: 262144
at es.<init>(SourceFile:50)
at net.minecraft.client.Minecraft.a(SourceFile:256)
at net.minecraft.client.Minecraft.run(SourceFile:563)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 5ce3bde8 ----------
The 128x128 works fine, though.
THANK YOU XAU YOU ARE A GOD
have you found a fix for that ? it also crashes here on any 256x texture pack !?
That doesn't work BECAUSE your computer Might not be good enough to run a 256x256 Pixels. I can't even run a 128x128 or above texture pack, cause my computer sucks so bad!
How can a computer not be good enough to handle 128x128?
Oh, I see...
The actual terrain.png that Minecraft has to load is 16x16 blocks so multiple the texture size by 16 to get the actual size.
On my old computer, which can only handle textures up to 1024x1024, that limits me to 64x64 for my minecraft textures, and on this new computer, which can handle up to 8192x8192, I'm limited to a whopping 512x512
Third issue I ever have with this fix is my own dufus fault. To explain what I was thinking at the time I made the mistake: *click click CLICK* "WHY ISNT THE DOWNLOAD AT THE TOP OF THE PAGE WORKING??!?!!?!" *five seconds later* "that's the link to the topic, not the download genuis." facepalm.jpg
The first was that the texture I tried using was just a folder with all of the pictures randomly thrown in there, and the second was easily fixed with what I read as the fix in op about switching water/lava animations off for more recent mc versions, in case you are wondering.
Rollback Post to RevisionRollBack
Quote from Detsuahxe »
No one using a creeper avatar has ever posted anything worth reading.
Fact.
So I'm not sure if its my computer or minecraft or my luck, or something I did wrong.
But I get this error after selecting a 64x64 or 128x128 pack in game as well as every time I try to start the game after selecting said pack I get the same error. After removing said pack I can play again. So I'm completely stumped on the issue.
java.nio.BufferOverflowException
at java.nio.DirectByteBuffer.put(Unknown Source)
at java.nio.ByteBuffer.put(Unknown Source)
at fu.a(SourceFile:148)
at fu.b(SourceFile:355)
at dk.a(SourceFile:81)
at kb.b(SourceFile:331)
at net.minecraft.client.Minecraft.run(SourceFile:622)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 265ce979 ----------
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
First go in to "bin" folder, backup u "minecraft.jar" in to "minecraft.original.jar"
Then start "mcpatcher-1.1.9_04" (but better re-download u "minecraft.jar" on original) use options what u like. and of course 32x fix. press "patch"
Then unpack from u "minecraft.jar" so files: ad.class ae.class ba.class et.class ez.class fu.class is.class iz.class ku.class ln.class nq.class oe.class WaterAnimation.class and "net\minecraft\client\Minecraft.class"
in to folder 32xfix
Del u "minecraft.jar", creat a copy of u "minecraft.original.jar", rename copy in to "minecraft.jar"
and put all files from 32xfix in to "minecraft.jar"
Then change in "minecraft.jar" (or it will not work) terrain.png and gui\items.png on u 32x
one bug, clock not work correctly
In my situation, if i use "gp.class(Watch)" game crash! :smile.gif:
My Ideas,My Minecraft Starter,My Easy Texture Pack Compiler,My Russian Translation,My BackUP Manager - My Easy Soft
That said, I'm not a java decompilation/recreation whiz, so I'm hoping someone reading this forum who is will try out these easy changes. Mipmapping will blur the texture when seen from far away or at a shallow angle. It looks a lot better, and any modern game uses it. For example:
Technical guys wanting to try this, read on: I believe you'll want to use GL_NEAREST instead of GL_LINEAR for magnification, and GL_NEAREST_MIPMAP_LINEAR for minification, in glTexParameterf, as otherwise you'll sample off the block's texture and get nearby samples from other blocks. So the mipmaps will still show some noise between levels, but it should still improve the look, especially for higher resolution textures. You'll also want to limit how high up the mipmap pyramid you can go with gluBuild2DMipmaps (i.e. what you set for "max", see this call), since beyond a certain point you'll then be blurring together a number of blocks' textures (e.g. for a 16x16 you'd want to go just 4 levels up at most: 8x8, 4x4, 2x2, 1x1).
I hope this post inspires someone out there to try it out - the patcher should easily be able to add this as an option (hint, hint). Without mipmapping available I just don't use anything higher than 16x16 block tiles.
EDIT: I tried the same thing again and it worked. Don't know why...
GENERATION 24: The first time you see this, copy it into your sig on any forum and add 1 to the generation. Social experiment.
No fix. Even with the newest patcher I get something similar:
#### Success! ...probably #### [java, -cp, C:\Users\Austin\AppData\Roaming\.minecraft\bin/minecraft.jar;C:\Users\Austin\AppData\Roaming\.minecraft\bin/lwjgl.jar;C:\Users\Austin\AppData\Roaming\.minecraft\bin/lwjgl_util.jar;C:\Users\Austin\AppData\Roaming\.minecraft\bin/jinput.jar, -Djava.library.path=C:\Users\Austin\AppData\Roaming\.minecraft\bin/natives, -Xmx1024M, -Xms512M, net.minecraft.client.Minecraft] 28 WARNING: Found unknown Windows version: Windows 7 Attempting to use default windows plug-in. Loading: net.java.games.input.DirectAndRawInputEnvironmentPlugin Starting up SoundSystem... Initializing LWJGL OpenAL (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) OpenAL initialized. java.lang.ArrayIndexOutOfBoundsException: 262144 at et.<init>(SourceFile:50) at net.minecraft.client.Minecraft.a(SourceFile:252) at net.minecraft.client.Minecraft.run(SourceFile:559) at java.lang.Thread.run(Unknown Source)Looks like Blackop2 is getting the same thing...
This shouldn't happen. Are you sure it's happening every time? Maybe there was just an oddly-timed update (or 3)?
It would definitely help, I turned my PMs back on so you can send me something that way. If you have it in a format that would make creating animations easier I'd be interested in that too. I thought about gif but looks like you have varying transparencies too.
This sounds like a Minecraft problem and not something this patcher has anything to do with.
This is something to do with the portals, I think it just was never tested for 256x256 (because 256x256 usually looks awful (and you should be ashamed for wanting to use it)) but I will look into it.
The log messages I quoted indicate that the minecraft.jar the patcher is reading and operating on is not the version it was created for when you ran it that time. Here's why:
Every time a Minecraft update adds new classes, some of the existing classes get different obfuscated names, usually one or two letters further in the alphabet. For everything except custom lava and water, the patcher does not care about the names. It looks for identifying things in the actual compiled bytecode: maybe the portal code says "Hey I'm a portal" somewhere, or maybe lava is drawn with a very specific algorithm, whatever.
The custom water and lava though use replacement classes for the 2 water and 2 lava animation classes. These are all new code and just dropped on top of the old ones. I have to manually change the names every time there is an update. So these log messages:
indicate that the patcher found the actual code that looks like the Flowing Lava code in ey.class. But when I compiled the patcher, I named it ez.class, because that's what it was in my minecraft.jar. So the log you posted shows, with 100% certainty, that the minecraft.jar you patched was not the same as the minecraft.jar the patcher was compiled for.
I realize this doesn't help you actually solve the problem, but there's not really anything else I can tell you. That's what's happening. If you've quadruple checked that everything is right, maybe you are getting a different error now without noticing.
I'll look into it but no promises.
I assume you have a specific reason for doing this, but I just want to point out that, in general, pulling the patched class files out and treating them as opaque replacement classes will just make the patcher less compatible with other mods. The patcher dynamically determines what needs to be fixed, so if some mod makes minor changes to a class the patcher affects, the patcher will still work fine. If you use the whole class files and there is a collision, you will have to choose one class file or the other.
Beauty is in the eye of the beholder :wink.gif: It's ok, xau, you're still my god for assuaging us HD crazies! I don't know where you are on the map, but I would so FedEx you a beer :biggrin.gif:
texture packs iv tried to run are
BumpmaftV1_3_5.rar extracted and used the .jar
AzasAridTexPack.zip
and even a remake of the defalt at 128x128 as a template
and still each attempt after patching and running the game i just get a black screen after the logo
here is what i get in the patcher log.
system specs are
Motherboard XFX G8300
AMD Phenom II X3 720 BE
3.5 gigs of random ram
random drives ranging from 160 Gig EIDE to
250 Gig SATA II
Nvidia Geforce GTX 460 OC
running windows 7 x64
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumoooooh...
thats new...
P.S the texture pack is Peasant's Pack
And BobtheFat:
The reason you are getting this is because you are trying to pick a different minecraft.jar for the original, correct? After you do that it automatically trys to patch it. All you have to do is go into the %appdata% and put your minecraft.jar you want to patch there. If you were going to find your default and have the patcher install your textures automatically, it will have automatically found your minecraft.jar, you don't need to find it.
That doesn't work BECAUSE your computer Might not be good enough to run a 256x256 Pixels. I can't even run a 128x128 or above texture pack, cause my computer sucks so bad!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHow can a computer not be good enough to handle 128x128?
Oh, I see...
The actual terrain.png that Minecraft has to load is 16x16 blocks so multiple the texture size by 16 to get the actual size.
On my old computer, which can only handle textures up to 1024x1024, that limits me to 64x64 for my minecraft textures, and on this new computer, which can handle up to 8192x8192, I'm limited to a whopping 512x512
Froze at 67%
Edit: Dw fixed it
The first was that the texture I tried using was just a folder with all of the pictures randomly thrown in there, and the second was easily fixed with what I read as the fix in op about switching water/lava animations off for more recent mc versions, in case you are wondering.
I'm aiming lower, yet still hopeful
But I get this error after selecting a 64x64 or 128x128 pack in game as well as every time I try to start the game after selecting said pack I get the same error. After removing said pack I can play again. So I'm completely stumped on the issue.