I know it is possible to use a 64px pack with a 128px pack or any other combination, but does anyone know if this causes any render problems or something? or is there no problem at all and it works just as good as a clean pack where everything is the same size?
it will automatically scale everything up to the largest resolution being used. there can be issues with bleeding and quality loss yes, but it doesn't happen very often when scaling up.
the only problem you would find visually is when the textures aren't cached... you might get white textures with black stripes, but switching to default and loading the world, then restarting minecraft usually fixes that.
Since november 2012 exists a bug with animated textures in SP. When you animate the book arrows that appear when the mouse hovers over the normal book arrows the animation jumps to one frame and freezes. In MP it works fine.
(example texturepack: https://dl.dropbox.c...j/book.zip?dl=1)
All animations freeze while a GUI is up in single-player. This is true in an unpatched MC as well. The fact that this affects custom GUI animations is an unfortunate side effect.
Maybe someone is interested ... http://www.minecraft...n_Minecraft_1.5
Just some information about the upcoming 1.5 texturepack format written by Jeb ...
Good: We can customize compasses and we can use properties files to fully customize terrain and item animations ..
Bad: Many many many other basic features are still missing ... (CTM support, animation support for all textures, no way to edit the skybox, probably even HD font support is missing)
Just saw that. The way they did the watch and compass textures is just odd to say the least. How many frames will it take just to have a decent-looking compass needle? I guess you could make a digital watch though.
It's nice that animations can specify custom frame order and timing, but the .txt format they chose isn't very flexible. I use .properties files in MCPatcher because they're simple and it's easy to add new values to them later.
So yeah, tomorrow's going to be interesting. I expect all of MCPatcher's mods will greyed out due to the class file changes. It will take some time to sort through the changes and will likely be too difficult to support 1.4 and 1.5 with the same patcher. I may just bite the bullet and break backward compatibility at that point.
All animations freeze while a GUI is up in single-player. This is true in an unpatched MC as well. The fact that this affects custom GUI animations is an unfortunate side effect.
I'm just about to update to 1.4.7 and came to say 'many thanks' again for your continued support...when I saw this. I'm most probably not understanding this point correctly, but all the animations on my GUIs work fine up to 1.4.6. What am I doing wrong.
Just saw that. The way they did the watch and compass textures is just odd to say the least. How many frames will it take just to have a decent-looking compass needle? I guess you could make a digital watch though.
It's nice that animations can specify custom frame order and timing, but the .txt format they chose isn't very flexible. I use .properties files in MCPatcher because they're simple and it's easy to add new values to them later.
So yeah, tomorrow's going to be interesting. I expect all of MCPatcher's mods will greyed out due to the class file changes. It will take some time to sort through the changes and will likely be too difficult to support 1.4 and 1.5 with the same patcher. I may just bite the bullet and break backward compatibility at that point.
I'm dreading having to make a separate version of my pack...having to convert all my .properties files just to make my pack compatible with Mojang's version of HD and animation...and it all still seems so limiting. Just so long as you continue with your excellent work, kahr, then I can rest easy...apart from all the goodies you keep putting in...which I can't possibly keep up with!
Well I'm still sorting through all the new classes Mojang added in 13w02a, but I can already tell this update isn't going to be easy. Mojang chose a particularly strange way to implement the new texture pack format. Even though there are separate files for each tile, the game still assembles them into a "fake" terrain.png. Not sure why they did this as it seems to combine the disadvantages of both formats with the advantages of neither. Several features I was looking forward to adding in 1.5 will have to be scrapped unfortunately.
I am having an issue where the fire animations in some of my texture packs arent working. I have to log out, switch texture packs, switch back, then log back in, to get them to work. Is anyone else having this problem or know what could be causing it?
Hey kahr, there's something I'm worried about. Are you going to be forcing us to split up our ctm.pngs similar to our terrain.pngs? I don't want to have to rewrite hundreds of .properties
Well I'm still sorting through all the new classes Mojang added in 13w02a, but I can already tell this update isn't going to be easy. Mojang chose a particularly strange way to implement the new texture pack format. Even though there are separate files for each tile, the game still assembles them into a "fake" terrain.png. Not sure why they did this as it seems to combine the disadvantages of both formats with the advantages of neither. Several features I was looking forward to adding in 1.5 will have to be scrapped unfortunately.
I'll update when I have more progress to share.
Hi! I'm just here to say, "whaaaa?"
I'm just going to hope they're not done refactoring the texture pack code and this is just a temporary way of doing things.
Hello All,
I have been having problems with McPatcher 1.4.7
I made a fresh install of Minecraft and McPatcher. my bin/mincraft.jar file is not recognized by McPatcher. It tells me I need to configure a valid client PatchSource first. What am I supposed to do?
Edit:
I finally got McPatcher to partially work. It downloaded the new snapshot. But after it tried to change the minecraft jar, it listed a bunch of errors and erased the jar file.
When I tried to patch my minecraft.jar, I got an error message saying that my minecraft.jar could be corrupt or that it cannot be found etc. But I know that this isn't the case because I have no issues playing the game.
Why would this be happening?
Not sure if this was asked already, but are you going to be getting rid of the custom_water_flowing, etc. support and just using the new format? Or will the old one be supported still too?
I use your water biomes so I was just curious as to how it will work.
Here's the 13w02b progress so far. Mostly got the low-hanging fruit out of the way. If MCP updates to the new snapshot things should go a lot faster. Manually deobfuscating the dozen or so new classes I need is slow going.
HD Font - Done!
Random Mobs - Done!
Custom Colors - Done!
Better Skies - Done! Added a backward compatibility feature to use textures in /terrain folder if /environment folder is missing.
Animate any texture - Not done
CTM - Not done
Better Glass - Not done
Better Grass - Not done. Will probably fold this into a CTM option.
Here's the 13w02b progress so far. Mostly got the low-hanging fruit out of the way. If MCP updates to the new snapshot things should go a lot faster. Manually deobfuscating the dozen or so new classes I need is slow going.
HD Font - Done!
Random Mobs - Done!
Custom Colors - Done!
Better Skies - Done! Added a backward compatibility feature to use textures in /terrain folder if /environment folder is missing.
Animate any texture - Not done
CTM - Not done
Better Glass - Not done
Better Grass - Not done. Will probably fold this into a CTM option.
Held item rendering fix - Not done
Mipmapping - Not done
Custom compass - Not done
What's this I'm hearing about mip mapping? How do you actually use it, cus I've not found it anywhere...
I assume you mean 13w02b? MCPatcher isn't compatible with this snapshot. That should be the reason why you get error messages.
While using the 1.4.7-jar you can specify the path to your minecraft.jar in the top part of the MCPatcher window.
In Original it should say: "]Program path]\bin\minecraft-1.4.7.jar"
And in Output: "[Program path]\bin\minecraft.jar"
If there's something wrong it could be the reason for your problem.
Are the paths for the source and the output correct? (See above about how they should look like)
AFAIK, the last version of minecraft that I have is 1.4.7 that is displayed when I open the client. I have a minecraft.jar in the bin folder, but no minecraft-1.4.7.jar file. There was an update to mcpatcher last night.
Am I supposed to create a minecraft-1.4.7.jar?
Edit: Created a minecraft-1.4.7.jar.
I tried two things. 1) I made a custom path which resulted in a backup error. 2) the standard path resulted in a copy error (313, unmain) and did I want to proceed, a cancel resulted in a destroyed file.
Well, I'm glad that the connected textures and better glass works well with glass panes...it was strange that the glass blocks blended together without the lines of the individual blocks, but the glass panes were still vanilla style with the lines between each block...looks SOO much better!
Rollback Post to RevisionRollBack
Wisemen say forgiveness is divine, but never pay full price for late pizza.
I will start here as it is the busiest. Where does one report bugs or change requests for the current version of Connected Textures? I expect there will be a small flurry of activity with the moving to the new 1.5 concepts and I see something the developer would probably like to think about.
I have one texture pack in Texturepack folder. No mods.
I have the MCPatcher 1.4.7 - 12w02b shortcut on desktop. I have Minecraft 1.4.7 fresh install. When I click on MCpatcher, I get a small box with 8 options. a drop bar with minecraft version. a bar uder that says unknown version. A lock, a restore, help and custom, patch and patch/run. nothing will work right
as long as your game is not running you can do whatever you want with it...
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumit will automatically scale everything up to the largest resolution being used. there can be issues with bleeding and quality loss yes, but it doesn't happen very often when scaling up.
the only problem you would find visually is when the textures aren't cached... you might get white textures with black stripes, but switching to default and loading the world, then restarting minecraft usually fixes that.
All animations freeze while a GUI is up in single-player. This is true in an unpatched MC as well. The fact that this affects custom GUI animations is an unfortunate side effect.
Just saw that. The way they did the watch and compass textures is just odd to say the least. How many frames will it take just to have a decent-looking compass needle? I guess you could make a digital watch though.
It's nice that animations can specify custom frame order and timing, but the .txt format they chose isn't very flexible. I use .properties files in MCPatcher because they're simple and it's easy to add new values to them later.
So yeah, tomorrow's going to be interesting. I expect all of MCPatcher's mods will greyed out due to the class file changes. It will take some time to sort through the changes and will likely be too difficult to support 1.4 and 1.5 with the same patcher. I may just bite the bullet and break backward compatibility at that point.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'm just about to update to 1.4.7 and came to say 'many thanks' again for your continued support...when I saw this. I'm most probably not understanding this point correctly, but all the animations on my GUIs work fine up to 1.4.6. What am I doing wrong.
I'm dreading having to make a separate version of my pack...having to convert all my .properties files just to make my pack compatible with Mojang's version of HD and animation...and it all still seems so limiting. Just so long as you continue with your excellent work, kahr, then I can rest easy...apart from all the goodies you keep putting in...which I can't possibly keep up with!
I'll update when I have more progress to share.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHi! I'm just here to say, "whaaaa?"
I'm just going to hope they're not done refactoring the texture pack code and this is just a temporary way of doing things.
I have been having problems with McPatcher 1.4.7
I made a fresh install of Minecraft and McPatcher. my bin/mincraft.jar file is not recognized by McPatcher. It tells me I need to configure a valid client PatchSource first. What am I supposed to do?
Edit:
I finally got McPatcher to partially work. It downloaded the new snapshot. But after it tried to change the minecraft jar, it listed a bunch of errors and erased the jar file.
Why would this be happening?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI use your water biomes so I was just curious as to how it will work.
What's this I'm hearing about mip mapping? How do you actually use it, cus I've not found it anywhere...
AFAIK, the last version of minecraft that I have is 1.4.7 that is displayed when I open the client. I have a minecraft.jar in the bin folder, but no minecraft-1.4.7.jar file. There was an update to mcpatcher last night.
Am I supposed to create a minecraft-1.4.7.jar?
Edit: Created a minecraft-1.4.7.jar.
I tried two things. 1) I made a custom path which resulted in a backup error. 2) the standard path resulted in a copy error (313, unmain) and did I want to proceed, a cancel resulted in a destroyed file.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThank You
I have one texture pack in Texturepack folder. No mods.
I have the MCPatcher 1.4.7 - 12w02b shortcut on desktop. I have Minecraft 1.4.7 fresh install. When I click on MCpatcher, I get a small box with 8 options. a drop bar with minecraft version. a bar uder that says unknown version. A lock, a restore, help and custom, patch and patch/run. nothing will work right