Well, I know, it's a duplicate issue, which I found here already, where someone made cylinder blocks (non-blocky)
But then they told him just not to do it.
But this issue happens every time, you create a model for a non opaque block.
It could also be a lack of feature.
But it would be rad, if you could fix it anyway =)
Linked issues
Attachments
Comments 4
I already know that! But what I want to say, there should be the possibility to change the non opaque to opaque when creating that model.
Really, I did know that already, which is the cause, I was posting this.
The feature was made, so texture artists have more possibilities. And I just want this feature to use it's full potential.
It basically cuts down lots of possibilities and opens ways for misuse.
And don't get me wrong, but by changing the model of the workbench, no computer will melt down. But you could count with massive lags, if you would change the model of dirt or stone. (around 2 fps, yeah, I checked it, and I must say, it COULD BE WORSE)
And the reason, I am saying, it's a lack of feature is because even if the model system is awesome, you can't choose, if it's opaque or not. (Which is pretty annoying when creating texture packs anyway! presenting the half opaque glass block) But then it's a bug too, because adding this new feature makes misuse possible and does stuff, which is absolutely not intended by adding this feature.
So PLEASE open this again, or explain me, why this is a bad idea. (And I don't think, it is!)
I'm sure the reason why they don't want us to decide if a block or a single model can have the isOpaque = false flag is:
They don't want to get hundred of support requests about how Minecraft is laggy because 100% of the times will be caused by a resourcepack changing too many blocks to isOpaque = false.
This property is resource intensive if too many blocks are on screen. Imagine if grass, stone and others are changed to isOpaque = false. All their faces must be rendered.
Maybe I'm wrong, but that's the only reason I can think of, other than they're lazy.
You should remember that if it had to render all sides of every block, with around 15,000 in each chunk, the game would be rather laggy, and this is less of a bug with minecraft, and more of a bug with your resource pack, which should add a bottom texture, plus, why do you use resource packs like that if they bother you with bugs,
JUST STICK WITH MINECRAFT'S TEXTURES
THEY'RE FINE
**Also, if they fixed this bug, it would be like starting a new world every time you loaded a different resource pack, or worse, it could be like starting a new world every time you load the world if you had a resource pack if it didn't save the isOpaque data
If it had to change that many blocks, it would cause lag in itself from all the block updates, and it would also cause essentially 25% more lag from having to render 6 sides instead of 5, it may be closer to 10 or 15%, but nobody wants that simply to fix some resource packs
The game determines if a block is opaque. They probably of a list of transparent tiles, something like glass, water, etc.
If the block is suppose to be opaque, the game doesn't bother rendering blocks behind it (because you can't see them anyway).
This reduces the graphics rendering to be manageable by most computers.
It isn't really a bug/glitch, or a lack of feature. More or less something they put into the code to prevent peoples computers from melting themselves. If a block is suppose to be opaque it will be rendered as opaque even if the texture has alpha values on it.