Does this happen only when mipmapping is turned on? Mojang's implementation of mipmaps leaves a lot to be desired, and I suspect they might just be throwing away pixels with a low alpha value.
Well I just checked again in your latest beta and the w39b snapshot, it appears to be happening with mipmapping on or off and with anisotropic filtering on or off as well. So basically it seems to be happening no matter what settings I use (I also checked all the lighting types, none made any sort of difference). I also noticed that it's not actually a specific distance either, I checked various distances and flying up and down (vertically) made the betterglass layer flash in and out, seemingly randomly, not at any specific height or distance as far as I could tell (although if the transition lagged behind at all it might've been happening more specifically than I noticed)
I can confirm the problem only occurs when mipmaps are enabled. Soartex water has low alpha values, so it disappears pretty often, unfortunately.
Another request. If there are a number of people experiencing this, it may be important. Would it be possible to determine the offset of bolded font? Minecraft renders bold by adding a second text layer with an offset, but because soartex font is thinner than default, the two layers separate.
Actually, it happens seemingly no matter what options are selected. Here's a Mojira issue about it. It used to affect rain and GUI, but now it just affects blocks, triggered and fixed based on a large number of odd factors.
The bold issue in that menu can be fixed. Try adding this to your .lang file if you have one for your pack:
Which will remove just the "bold" effect. If the .lang file is older, don't worry, just add those lines. The .lang files work similar in a way to resource packs in general or like character usage, Minecraft knows where to get something if it isn't all there. You can chop out a majority of the .lang files and Minecraft doesn't even care, it finds all the names from the original .lang file in the .jar.
Rollback Post to RevisionRollBack
"I'm an outsider by choice, but not truly.
It’s the unpleasantness of the system that keeps me out.
I’d rather be in, in a good system. That’s where my discontent comes from:
being forced to choose to stay outside.
My advice: Just keep movin’ straight ahead.
Every now and then you find yourself in a different place."
-George Carlin
I've got this little bug with 4.3.0-beta2: skyboxes only render partially at render distance 4 or 5 basically leaving huge triangular "windows" in the sky. At distance 6 the problem seems to disappear.
What "custom potion partcicls" mean?
I mean, how can I use it, add what does it do?
Also, mcpatcher will ever support using random arrow texture for the model? (Arrow1.png arrow2.png etc)
And door/snow cover block ctm?
Potion colors for each potion type can be customized in color.properties. The custom colors are applied to the particle effects that appear around players too.
No plans for random arrow textures, and I don't know what "door/snow cover block ctm" is.
By the way, animated CTM textures cause a crash. I have an animated random horizontal CTM nether bookshelf that trips the game up.
There is an error in your mcmeta files. In 80.png.mcmeta and 112.png.mcmeta, you have index 1, 2, 3, 4. Index is 0-based, so it should be 0, 1, 2, 3. The fact that it's crashing instead of reporting the error is probably Mojang's fault, so try making the same error in a non-CTM texture and see if it crashes without MCPatcher. If so, file a bug report in Atlassian about it.
Would it make sense, or be possible, to have an exemption list of textures from Mojang's mipmapping? I'd like to disable the mipmapping on the splash screen, options background, font and glass.
Not that this has much to do with MCPatcher, but I've also noticed Mojang's mipmapping turns tall grass edges black. Anyone else having problems like this?
Yes, MCPatcher's mipmapping implementation dealt with these problems, but shoehorning just those bits of it into Mojang's code isn't feasible.
So again, I'd rather people file bug reports for stuff like this. In general, if it's a legitimate problem that you can reproduce without MCPatcher, it's better that Mojang fix it themselves.
Well I just checked again in your latest beta and the w39b snapshot, it appears to be happening with mipmapping on or off and with anisotropic filtering on or off as well. So basically it seems to be happening no matter what settings I use (I also checked all the lighting types, none made any sort of difference).
Mojang has been tweaking the min-alpha threshold in the last few snapshots. I think it went from 0.1 to 0.5, then back to 0.1, and I don't know what it is now. I suspect they're doing it to try to fix the black outline problem. Trust me, I went down that road myself and it's not going to work.
I have a nother question to do with random mobs. I would love to make my wolf textures to spawn in different biomes with help of mob.properties but i wouldn't like if they would spawn undergrond(if that is even posible) couse i dont know the how the heights go and am asking you if there is anywhere any information about hights or anything, hope you understand my wierdly asked question ~ Thank you!
Just remembered, i have one more question In mob.properties can i unite weights and biomes ?
like this:
skins.1=2-6
weights.1=9 7 5 3 10
biomes.1=Forest Taiga
minHeight.1=55
maxHight.1=85
or like this:
skins.1=2-6
weights.1=9 7 5 3 10
minHeight.1=55
maxHight.1=85
skins.1=2-6
biomes.1=Forest Taiga
minHeight.1=55
maxHight.1=85
or any other?
The height option doesn't dictate whether a mob will spawn at that given height, it denotes at what height the texture will be applied. That's all randomobs really does, it doesn't have any control over the spawn algorithms, it just applies a new texture to the mob depending on the defined conditions. The heights, also, can be used together with weight and biome conditions, there's no real reason to keep them separate unless you're daisy-chaining properties files for a complex purpose. Your first example is probably the best approach for using those conditions together.
It's also not really necessary to use the heights for everything unless you specifically want a texture to be applied at a certain height, like if you want pure white wolves to occur on high taiga mountains, or black creepers to occur very deep underground. Leaving the heights out just has that texture occur across the whole biome that's defined, if one is defined at all.
I'm getting some really crazy issues with this. Like, random mobs glitching out; specifically the mobs jump through loads of different textures every other tick; not even the correct textures (i.e. sheep using pig skin, etc.). Also, on my 128 pack, and sphax's and misa's, the terrain blocks completely disappear. When I load a world, I can see nothing but the mobs and particle effects.
However, when I turned my render chunks down to 6, and turned off mipmapping and anistropic filtering, everything showed up. Then I could turn on mipmapping with no problems. Unfortunately, I can't get this fix to work consistently.
I'm on OS 10.7.5 with an ATI Radeon HD 2400 XT 128 MB graphics card, if that helps at all.
So i have some more problems with mob.properties! I am really bad at codes and stuff like that or am just dumb. Anyways the plan at the first place was to make different kinds of wolves spawning on different biomes. I don't know now if that is even posible right now with random mobs and prbably i thought wrong that it is or really is posible and i don't know hot to make it.
First the wolf.properties didn't worked but i realised why it didn't i putted wolf.properties file to /mob/wolf/wolf.properties and instead it should be in /mob/wolf.properties.
here is the wolf.properties file i made. I just need someone that understands codes a lot better than me and tell me about my stupidity and what i did wrong and if wolves can be spawned in different biomes.
Aside from that it looks fine. Now I don't know if it changed for the 1.7 version, but also the wolf.properties file typically would go in the wolf folder. The whole path under your resource pack would be: assets\minecraft\mcpatcher\mob\wolf\wolf.properties, but if it works outside of the folder then no biggie.
Now, like I said in my previous post, the Randomobs mod doesn't affect any actual spawning algorithm or code. It only changes the look of a mob, depending on the conditions defined in the properties file. It's not gonna make mooshrooms spawn in a desert or cats spawn in a taiga, it just makes a mob look different depending on the textures you have for said mob, and the conditions defined for it. So you can make zombies look like mummies in deserts, or give them miner clothes for a certain depth underground, but you can't change their spawning behavior.
Mojang has been tweaking the min-alpha threshold in the last few snapshots. I think it went from 0.1 to 0.5, then back to 0.1, and I don't know what it is now. I suspect they're doing it to try to fix the black outline problem. Trust me, I went down that road myself and it's not going to work.
Hrm, hope they come to a solution soon enough, I only use anisotropic filtering anyway so the only thing I care about is what they're going to lock the threshold at. Hope I won't have to change my glass!
Sounds logic I totaly forgot that wolfes can't spawn in deserts and so lol It would work with zombies but not with wolves. Thanks for reminding me that and thank you again for your help!
No problem, mate. :3 If ya got any more questions I'm more than happy to help.
Kahr, I just discovered that now when you're in shadow (under a tree or overhang), the renderer changes the sky fog color to a dark grey. Will we be able to change this in the future? And I apologize if this has been around awhile. I've been away, and only returned since the terrain engine update.
And do you and Misa have any sort of time frame for getting her proposed 256-column biome color map up and running? Or are we in hold mode waiting to see what Mojang's going to put out next?
Thank you for all of your hard work. It's very much appreciated.
I've been reading every single guide I can find everywhere -- and the general consensus is I have NO idea what I'm doing.
I'd like to make redstone wiring and redstone particles green. I made the mcpatcher folder in my pack-name-here/assets/minecraft folder, and then made the ColorMap folder within my mcpatcher folder. Within this I made 3 files since there was NO agreement on what filename to use -- custom_redstonecolor.png, redstonecolor.png, and redstone.png. They are all 16x1 horizontal pngs that go from dark green to light green.
When I slip the resource pack in my rp folder and patch for 1.6.4 -- booting minecraft up in that profile and entering a singleplayer map does absolutely nothing. Redstone wiring and particles are all still completely and totally default in color.
What am I doing wrong? No one on any forum can agree on whether to put it in the /misc folder or the /mcpatcher folder, nor whether to create a horizontal or vertical file, nor whether you need the .properties file (which doesn't even list redstone) or where to put it, or what filename to use for this image. I've tried every combination I can think of, even going as far as unpatching and uninstalling minecraft and re-patching a second/third/fourth time -- no dice.
Help?
Edit: I've made sure to check "custom colors" regardless of what else I try -- but I've done just that box, and every box on your list. Better grass worked -- changing the sides of my grass blocks, but redstone still hasn't budged.
Problem has been resolved! It was a matter of folder names. Thanks for your help!
I've been reading every single guide I can find everywhere -- and the general consensus is I have NO idea what I'm doing.
You should mainly be reading the guides in the OP of this thread. Regardless, that seems to be a pretty common condition for those starting out with this mod.
I'd like to make redstone wiring and redstone particles green. I made the mcpatcher folder in my pack-name-here/assets/minecraft folder, and then made the ColorMap folder within my mcpatcher folder. Within this I made 3 files since there was NO agreement on what filename to use -- custom_redstonecolor.png, redstonecolor.png, and redstone.png. They are all 16x1 horizontal pngs that go from dark green to light green.
The filename "redstone.png" is the correct one. Also, make sure you have all of the cases in your folders correct. It should be /colormap/ not /ColorMap/. Make sure this isn't your issue.
When I slip the resource pack in my rp folder and patch for 1.6.4 -- booting minecraft up in that profile and entering a singleplayer map does absolutely nothing. Redstone wiring and particles are all still completely and totally default in color.
Are you booting 1.6.4, or 1.6.4-mcpatcher? You should be using the later in your profile.
What am I doing wrong? No one on any forum can agree on whether to put it in the /misc folder or the /mcpatcher folder, nor whether to create a horizontal or vertical file, nor whether you need the .properties file (which doesn't even list redstone) or where to put it, or what filename to use for this image. I've tried every combination I can think of, even going as far as unpatching and uninstalling minecraft and re-patching a second/third/fourth time -- no dice.
Help?
Calm down.
For starters, you have to realize that a LOT of the guides you've probably been reading are out of date. A lot changed with Minecraft 1.5, and then immediately again in 1.6. Anything written for a version prior to 1.6 will be misinformation to you. This is why you should look mainly at the Information for Texture Pack Authors section in the OP of this thread.
And no, you don't need a .properties file for this particular mechanism.
Edit: I've made sure to check "custom colors" regardless of what else I try -- but I've done just that box, and every box on your list. Better grass worked -- changing the sides of my grass blocks, but redstone still hasn't budged.
I'm guessing that you just misspelled something, have something in the wrong folder, put a capital letter where it should be lower-case, or something equally easy to overlook. Tell me, can you get any changes to vanilla textures to work? If so, then you're on the right track. If not, your folder structure is probably off.
If all else fails, consider uploading your pack somewhere so I can take a look at it. Don't worry, we'll get this to work for you.
The filename "redstone.png" is the correct one. Also, make sure you have all of the cases in your folders correct. It should be /colormap/ not /ColorMap/. Make sure this isn't your issue.
Changed /ColorMap/ to /colormap/, but it still isn't working. Better grass is, but redstone isn't.
Alright, I'm calm. We're calm. Super calm. Calm as a cucumber. I've been trying to change the color of redstone since I started my Tartarus map, and I was never able to get it to work.
For starters, you have to realize that a LOT of the guides you've probably been reading are out of date. A lot changed with Minecraft 1.5, and then immediately again in 1.6. Anything written for a version prior to 1.6 will be misinformation to you. This is why you should look mainly at the Information for Texture Pack Authors section in the OP of this thread.
Noted. Some of my info I was pulling from a YouTube video posted in May, and the comments from only a week ago...
I'm guessing that you just misspelled something, have something in the wrong folder, put a capital letter where it should be lower-case, or something equally easy to overlook. Tell me, can you get any changes to vanilla textures to work? If so, then you're on the right track. If not, your folder structure is probably off.
All of my vanilla stuff works fine, so far as I can see. I'm still only 30%ish through my pack, but so far so good.
This is the pack's page, the download should work -- I just updated it with the file in what I think is the right place.
Thank-you-thank-you-thank-you -- even if it just isn't meant to be, I really appreciate it!
I just downloaded it. I'm guessing that PMC is taking a while to update the file, though, since the one I downloaded doesn't have an /mcpatcher/ folder in it at all that I can see.
I'll try re-downloading it in a few hours. If I don't get back to you by tomorrow, please feel free to poke me. I'm a busy/forgetful person sometimes.
That's MC-31681. It's most likely a bug (if it would be a feature, it would be a pretty stupid one). At least it needs fixing, so you better upvote this on the bug tracker.
I'm getting a crash when using this with FML (Not Forge). When I try to start a game:
Client> 2013-10-03 15:53:06 [SEVERE] [ForgeModLoader] A fatal exception occurred during the server about to start event
Client> java.lang.NullPointerException
Client> at cpw.mods.fml.common.Loader.serverAboutToStart(Loader.java:812)
Client> at cpw.mods.fml.common.FMLCommonHandler.handleServerAboutToStart(FMLCommonHandler.java:309)
Client> at net.minecraft.server.integrated.IntegratedServer.func_71197_b(IntegratedServer.java:117)
Client> at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:370)
Client> at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:583)
Client> 2013-10-03 15:53:06 [INFO] [Minecraft-Server] Stopping server
Client> 2013-10-03 15:53:06 [INFO] [Minecraft-Server] Saving players
Client> 2013-10-03 15:53:06 [INFO] [Minecraft-Server] Saving worlds
Client> 2013-10-03 15:53:06 [INFO] [STDERR] java.lang.NullPointerException
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at net.minecraft.server.MinecraftServer.func_71267_a(MinecraftServer.java:286)
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at net.minecraft.server.MinecraftServer.func_71260_j(MinecraftServer.java:331)
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at net.minecraft.server.integrated.IntegratedServer.func_71260_j(IntegratedServer.java:226)
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:462)
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:583)
Client> 2013-10-03 15:53:06 [INFO] [STDERR] Exception in thread "Server thread" java.lang.NullPointerException
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at cpw.mods.fml.common.FMLCommonHandler.handleServerStopped(FMLCommonHandler.java:468)
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:471)
Client> 2013-10-03 15:53:06 [INFO] [STDERR] at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:583)
Game ended with bad state (exit code 1)
And when I join a game.
---- Minecraft Crash Report ----
// Don't be sad, have a hug! <3
Time: 10/3/13 3:56 PM
Description: Ticking screen
java.lang.NullPointerException
at cpw.mods.fml.common.network.FMLNetworkHandler.getFMLFakeLoginPacket(FMLNetworkHandler.java:239)
at net.minecraft.client.multiplayer.NetClientHandler.func_72513_a(NetClientHandler.java:306)
at net.minecraft.network.packet.Packet252SharedKey.func_73279_a(SourceFile:40)
at net.minecraft.network.TcpConnection.func_74428_b(TcpConnection.java:387)
at net.minecraft.client.multiplayer.NetClientHandler.func_72551_d(NetClientHandler.java:252)
at net.minecraft.client.multiplayer.GuiConnecting.func_73876_c(GuiConnecting.java:45)
at net.minecraft.client.Minecraft.func_71407_l(SourceFile:1173)
at net.minecraft.client.Minecraft.func_71411_J(SourceFile:663)
at net.minecraft.client.Minecraft.func_99999_d(SourceFile:619)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at cpw.mods.fml.common.network.FMLNetworkHandler.getFMLFakeLoginPacket(FMLNetworkHandler.java:239)
at net.minecraft.client.multiplayer.NetClientHandler.func_72513_a(NetClientHandler.java:306)
at net.minecraft.network.packet.Packet252SharedKey.func_73279_a(SourceFile:40)
at net.minecraft.network.TcpConnection.func_74428_b(TcpConnection.java:387)
at net.minecraft.client.multiplayer.NetClientHandler.func_72551_d(NetClientHandler.java:252)
at net.minecraft.client.multiplayer.GuiConnecting.func_73876_c(GuiConnecting.java:45)
-- Affected screen --
Details:
Screen name: net.minecraft.client.multiplayer.GuiConnecting
Stacktrace:
at net.minecraft.client.Minecraft.func_71407_l(SourceFile:1173)
at net.minecraft.client.Minecraft.func_71411_J(SourceFile:663)
at net.minecraft.client.Minecraft.func_99999_d(SourceFile:619)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
-- System Details --
Details:
Minecraft Version: 1.6.4
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_40, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 264191744 bytes (251 MB) / 390070272 bytes (372 MB) up to 1897922560 bytes (1810 MB)
Mod Pack: Unknown / None
LiteLoader Mods: 0 loaded mod(s)
JVM Flags: 1 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: FML is installed
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML:
Launched Version: 1.6.4-Lite-FML-mcpatcher
LWJGL: 2.9.0
OpenGL: GeForce GT 430/PCIe/SSE2 GL version 4.3.0, NVIDIA Corporation
Is Modded: Definitely; Client brand changed to 'fml'
Type: Client (map_client.txt)
Resource Pack: Love & Tolerance 1.6 v3.zip
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
Somewhat of a new bug (13w39b):
The game doesn't take hardcoded biome colorings (Mesa and Swamp) and apply them to water (old), grass, or oak leaves (snapshot).
Jungle leaves/sugarcane and all tall grasses work fine. There is a similar existing bug in OptiFine with water, grass, leaves, sky, etc. for non-vanilla colors.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWell I just checked again in your latest beta and the w39b snapshot, it appears to be happening with mipmapping on or off and with anisotropic filtering on or off as well. So basically it seems to be happening no matter what settings I use (I also checked all the lighting types, none made any sort of difference). I also noticed that it's not actually a specific distance either, I checked various distances and flying up and down (vertically) made the betterglass layer flash in and out, seemingly randomly, not at any specific height or distance as far as I could tell (although if the transition lagged behind at all it might've been happening more specifically than I noticed)
-
View User Profile
-
View Posts
-
Send Message
Retired StaffActually, it happens seemingly no matter what options are selected. Here's a Mojira issue about it. It used to affect rain and GUI, but now it just affects blocks, triggered and fixed based on a large number of odd factors.
The bold issue in that menu can be fixed. Try adding this to your .lang file if you have one for your pack:
resourcePack.available.title=§r§nAvailable Resource Packs
resourcePack.selected.title=§r§nSelected Resource Packs
Which will remove just the "bold" effect. If the .lang file is older, don't worry, just add those lines. The .lang files work similar in a way to resource packs in general or like character usage, Minecraft knows where to get something if it isn't all there. You can chop out a majority of the .lang files and Minecraft doesn't even care, it finds all the names from the original .lang file in the .jar.
"I'm an outsider by choice, but not truly.
It’s the unpleasantness of the system that keeps me out.
I’d rather be in, in a good system. That’s where my discontent comes from:
being forced to choose to stay outside.
My advice: Just keep movin’ straight ahead.
Every now and then you find yourself in a different place."
-George Carlin
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYes, use blend=replace in the properties file, which simply replaces pixels rather than adding to them.
Potion colors for each potion type can be customized in color.properties. The custom colors are applied to the particle effects that appear around players too.
No plans for random arrow textures, and I don't know what "door/snow cover block ctm" is.
There is an error in your mcmeta files. In 80.png.mcmeta and 112.png.mcmeta, you have index 1, 2, 3, 4. Index is 0-based, so it should be 0, 1, 2, 3. The fact that it's crashing instead of reporting the error is probably Mojang's fault, so try making the same error in a non-CTM texture and see if it crashes without MCPatcher. If so, file a bug report in Atlassian about it.
Yes, MCPatcher's mipmapping implementation dealt with these problems, but shoehorning just those bits of it into Mojang's code isn't feasible.
So again, I'd rather people file bug reports for stuff like this. In general, if it's a legitimate problem that you can reproduce without MCPatcher, it's better that Mojang fix it themselves.
Mojang has been tweaking the min-alpha threshold in the last few snapshots. I think it went from 0.1 to 0.5, then back to 0.1, and I don't know what it is now. I suspect they're doing it to try to fix the black outline problem. Trust me, I went down that road myself and it's not going to work.
The height option doesn't dictate whether a mob will spawn at that given height, it denotes at what height the texture will be applied. That's all randomobs really does, it doesn't have any control over the spawn algorithms, it just applies a new texture to the mob depending on the defined conditions. The heights, also, can be used together with weight and biome conditions, there's no real reason to keep them separate unless you're daisy-chaining properties files for a complex purpose. Your first example is probably the best approach for using those conditions together.
It's also not really necessary to use the heights for everything unless you specifically want a texture to be applied at a certain height, like if you want pure white wolves to occur on high taiga mountains, or black creepers to occur very deep underground. Leaving the heights out just has that texture occur across the whole biome that's defined, if one is defined at all.
I'm getting some really crazy issues with this. Like, random mobs glitching out; specifically the mobs jump through loads of different textures every other tick; not even the correct textures (i.e. sheep using pig skin, etc.). Also, on my 128 pack, and sphax's and misa's, the terrain blocks completely disappear. When I load a world, I can see nothing but the mobs and particle effects.
However, when I turned my render chunks down to 6, and turned off mipmapping and anistropic filtering, everything showed up. Then I could turn on mipmapping with no problems. Unfortunately, I can't get this fix to work consistently.
I'm on OS 10.7.5 with an ATI Radeon HD 2400 XT 128 MB graphics card, if that helps at all.
Any ideas?
Well, I can spot a couple mistakes. For starters, skins 7 and 8 are missing the biome condition. You have it as:
When it should be this:
Aside from that it looks fine. Now I don't know if it changed for the 1.7 version, but also the wolf.properties file typically would go in the wolf folder. The whole path under your resource pack would be: assets\minecraft\mcpatcher\mob\wolf\wolf.properties, but if it works outside of the folder then no biggie.
Now, like I said in my previous post, the Randomobs mod doesn't affect any actual spawning algorithm or code. It only changes the look of a mob, depending on the conditions defined in the properties file. It's not gonna make mooshrooms spawn in a desert or cats spawn in a taiga, it just makes a mob look different depending on the textures you have for said mob, and the conditions defined for it. So you can make zombies look like mummies in deserts, or give them miner clothes for a certain depth underground, but you can't change their spawning behavior.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHrm, hope they come to a solution soon enough, I only use anisotropic filtering anyway so the only thing I care about is what they're going to lock the threshold at. Hope I won't have to change my glass!
No problem, mate. :3 If ya got any more questions I'm more than happy to help.
And do you and Misa have any sort of time frame for getting her proposed 256-column biome color map up and running? Or are we in hold mode waiting to see what Mojang's going to put out next?
Thank you for all of your hard work. It's very much appreciated.
I've been reading every single guide I can find everywhere -- and the general consensus is I have NO idea what I'm doing.
I'd like to make redstone wiring and redstone particles green. I made the mcpatcher folder in my pack-name-here/assets/minecraft folder, and then made the ColorMap folder within my mcpatcher folder. Within this I made 3 files since there was NO agreement on what filename to use -- custom_redstonecolor.png, redstonecolor.png, and redstone.png. They are all 16x1 horizontal pngs that go from dark green to light green.
When I slip the resource pack in my rp folder and patch for 1.6.4 -- booting minecraft up in that profile and entering a singleplayer map does absolutely nothing. Redstone wiring and particles are all still completely and totally default in color.
What am I doing wrong? No one on any forum can agree on whether to put it in the /misc folder or the /mcpatcher folder, nor whether to create a horizontal or vertical file, nor whether you need the .properties file (which doesn't even list redstone) or where to put it, or what filename to use for this image. I've tried every combination I can think of, even going as far as unpatching and uninstalling minecraft and re-patching a second/third/fourth time -- no dice.
Help?
Edit: I've made sure to check "custom colors" regardless of what else I try -- but I've done just that box, and every box on your list. Better grass worked -- changing the sides of my grass blocks, but redstone still hasn't budged.
Problem has been resolved! It was a matter of folder names. Thanks for your help!
-
View User Profile
-
View Posts
-
Send Message
Retired StaffYou should mainly be reading the guides in the OP of this thread. Regardless, that seems to be a pretty common condition for those starting out with this mod.
The filename "redstone.png" is the correct one. Also, make sure you have all of the cases in your folders correct. It should be /colormap/ not /ColorMap/. Make sure this isn't your issue.
Are you booting 1.6.4, or 1.6.4-mcpatcher? You should be using the later in your profile.
Calm down.
For starters, you have to realize that a LOT of the guides you've probably been reading are out of date. A lot changed with Minecraft 1.5, and then immediately again in 1.6. Anything written for a version prior to 1.6 will be misinformation to you. This is why you should look mainly at the Information for Texture Pack Authors section in the OP of this thread.
And no, you don't need a .properties file for this particular mechanism.
I'm guessing that you just misspelled something, have something in the wrong folder, put a capital letter where it should be lower-case, or something equally easy to overlook. Tell me, can you get any changes to vanilla textures to work? If so, then you're on the right track. If not, your folder structure is probably off.
If all else fails, consider uploading your pack somewhere so I can take a look at it. Don't worry, we'll get this to work for you.
Changed /ColorMap/ to /colormap/, but it still isn't working. Better grass is, but redstone isn't.
Booting up in my special MCPatcher profile -- 1.6.4-mcpatcher is the version that's booting up.
Alright, I'm calm. We're calm. Super calm. Calm as a cucumber. I've been trying to change the color of redstone since I started my Tartarus map, and I was never able to get it to work.
Noted. Some of my info I was pulling from a YouTube video posted in May, and the comments from only a week ago...
All of my vanilla stuff works fine, so far as I can see. I'm still only 30%ish through my pack, but so far so good.
YES, PLEASE -- WOULD YOU?
http://www.planetminecraft.com/texture_pack/blockstuck-resource-pack/
This is the pack's page, the download should work -- I just updated it with the file in what I think is the right place.
Thank-you-thank-you-thank-you -- even if it just isn't meant to be, I really appreciate it!
-
View User Profile
-
View Posts
-
Send Message
Retired StaffI'll try re-downloading it in a few hours. If I don't get back to you by tomorrow, please feel free to poke me. I'm a busy/forgetful person sometimes.
Thanks, Zombie! I'll do that.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd when I join a game.
Mods I work on and maintain:
TabbyChat | Mine Little Pony
My Blog
The game doesn't take hardcoded biome colorings (Mesa and Swamp) and apply them to water (old), grass, or oak leaves (snapshot).
Jungle leaves/sugarcane and all tall grasses work fine. There is a similar existing bug in OptiFine with water, grass, leaves, sky, etc. for non-vanilla colors.
Putting the CENDENT back in transcendent!