The Meaning of Life, the Universe, and Everything.
Location:
California
Join Date:
9/16/2011
Posts:
43
Minecraft:
HunterBlackbrick
Member Details
I've been working with texture/resource packs since 8/23/2011 so I understand a lot, but admittedly not everything. Especially as of late, I feel a bit lost at times. So here I am, asking for assistance.
So my first and main question for now is in regards to sounds. Back when they changed to the codes rather than straight files I was immediately lost. I understand now how to retrieve them, but reading into topics on the forums I'm seeing that the means of replacing sounds may have changed as well. I saw in one article someone mentioned setting the sounds.json to say "replace" to overwrite default sounds. If anyone h as time at some point to maybe help address the current method of sound/music replacement, that would be amazing.
I have some other questions as well (some of which are evaiding my mind at the moment so when I remember what they were I'll update this topic) One question is in regards to CTM. For whatever reason, now I'm not sure what changed between updates, but for whatever reason the CTM on the underside of all of my blocks are repeating weirdly. I'm not really sure how to explain it other than it's supposed to be like every other block face with a set repeat CTM in a 16x16 alignment of textures, but the bottoms are misbehaving and are breaking up into odd columns.
I have some other questions as well (some of which are evaiding my mind at the moment so when I remember what they were I'll update this topic) One question is in regards to CTM. For whatever reason, now I'm not sure what changed between updates, but for whatever reason the CTM on the underside of all of my blocks are repeating weirdly. I'm not really sure how to explain it other than it's supposed to be like every other block face with a set repeat CTM in a 16x16 alignment of textures, but the bottoms are misbehaving and are breaking up into odd columns.
If I had to guess, I'd say it's because CTM fights with block models. A lot.
Let's assume for the sake of argument that you've already eliminated the random rotations and mirroring on stone. If you haven't, you should do so now. You can do this by changing the blockstate file.
But even without the randomness being inherited from the blockstate the bottom still looks wrong. The reason for this is that the bottom face of cube.json, the model all basic cube-type blocks inherit their shape from, is mapped so that the top of the texture is on the north edge of the block while the bottom of the texture is on the south edge of the block. Optifine, meanwhile, assumes that everything is always facing the same way. The top of the texture should be on the north side of the top and bottom.
This absolutely the fault of Optifine... but can be corrected in your pack by altering the cube.json model. Just know that this will also change the bottom face of absolutely every basic cube. Chances are this isn't a big issue since who really cares about the bottom of the block as long as it doesn't look wonky... but since it might cause your other blocks to look wonky I thought I'd point it out. (It'll also cause this very same problem to re-occur if it ever gets fixed in Optifine)
Really you should try posting a bug thingy on Optifines Github since this really is a bug. Don't know if it'll ever get fixed... but you can try.
I've been working with texture/resource packs since 8/23/2011 so I understand a lot, but admittedly not everything. Especially as of late, I feel a bit lost at times. So here I am, asking for assistance.
So my first and main question for now is in regards to sounds. Back when they changed to the codes rather than straight files I was immediately lost. I understand now how to retrieve them, but reading into topics on the forums I'm seeing that the means of replacing sounds may have changed as well. I saw in one article someone mentioned setting the sounds.json to say "replace" to overwrite default sounds. If anyone h as time at some point to maybe help address the current method of sound/music replacement, that would be amazing.
I have some other questions as well (some of which are evaiding my mind at the moment so when I remember what they were I'll update this topic) One question is in regards to CTM. For whatever reason, now I'm not sure what changed between updates, but for whatever reason the CTM on the underside of all of my blocks are repeating weirdly. I'm not really sure how to explain it other than it's supposed to be like every other block face with a set repeat CTM in a 16x16 alignment of textures, but the bottoms are misbehaving and are breaking up into odd columns.
Link to my resource packs for reference: https://www.dropbox.com/sh/i91y4ys74rk67kq/AABcse-fUs3HZuChHj-WD1WKa?dl=0
Thanks in advance for reading this long drawn out post, I know it's not too organized but I hope someone can help.
If I had to guess, I'd say it's because CTM fights with block models. A lot.
Let's assume for the sake of argument that you've already eliminated the random rotations and mirroring on stone. If you haven't, you should do so now. You can do this by changing the blockstate file.
But even without the randomness being inherited from the blockstate the bottom still looks wrong. The reason for this is that the bottom face of cube.json, the model all basic cube-type blocks inherit their shape from, is mapped so that the top of the texture is on the north edge of the block while the bottom of the texture is on the south edge of the block. Optifine, meanwhile, assumes that everything is always facing the same way. The top of the texture should be on the north side of the top and bottom.
This absolutely the fault of Optifine... but can be corrected in your pack by altering the cube.json model. Just know that this will also change the bottom face of absolutely every basic cube. Chances are this isn't a big issue since who really cares about the bottom of the block as long as it doesn't look wonky... but since it might cause your other blocks to look wonky I thought I'd point it out. (It'll also cause this very same problem to re-occur if it ever gets fixed in Optifine)
Really you should try posting a bug thingy on Optifines Github since this really is a bug. Don't know if it'll ever get fixed... but you can try.
I hope that helps you.