MC-28145Iron bar top improperly vanishing
The top of a iron bar disappears when there is a block above it to avoid z-fighting. However, there are some cases where it doesn't do this right.
A lower iron bar will hide it's top if there is a block above and to the side the part is on if there is a) a iron bar above it, and b) a block to the side of the bar.
This works right, otherwise you'd have stripes thru your bars.
However, you may place a block that the bar doesn't connect to.
Then, it hides the top, even though there is nothing above, creating a minor graphical glitch.
Linked Issues
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
Created Issue:
Iron bar top improperly vanishing
The top of a iron bar disappears when there is a block above it to avoid z-fighting. However, there are some cases where it doesn't do this right.
A lower iron bar will hide it's top if there is a block above and to the side the part is on if there is a) a iron bar above it, and b) a block to the side of the bar.
This works right, otherwise you'd have stripes thru your bars.
However, you may place a block that the bar doesn't connect to.
Then, it hides the top, even though there is nothing above, creating a minor graphical glitch.
Attachments2
duplicates
Both the OP and my comments clearly describe that this is an issue with the models system.
In the OP (right at the start): With 3D models and interblock culling enabled
In my first response: mine is about culling itself erroneously culling different block states of models (custom included, so the entire system, not just default behavior) .....
but culling was just removed from the default iron bars/glass panes rather than fixing the fundamentals of how culling works.
I'm not sure how to get more clear than that, so it seemed to me that you or Mustek didn't read the description but just assumed it was exactly the same issue with the same scope.
Your response ticked me off because not only did it seem like you didn't read the issue or the comments, but after I added a 21b screenshot and further explanation of why I was using my pack in my Second response:
Culling is a feature of the model format, which does not work properly on iron bars or glass panes because if culling is applied it applies when different block states are next to each other even though they don't line up. The issue is still there, default just no longer enables culling for those blocks so you can't see it.
You edited your statement to be bolded. To me at the time it seemed intentional as to undermine the issue, and maybe that wasn't the case. But hey, I write my issues further than "duh huh, iron bars are borken!!!1!" I'd appreciate it if the mods would read it first before marking it as "duplicate" to a fixed issue that in the back-end isn't really fixed. And if the mods here don't understand it or have the time to read it they should leave the issue alone.
a)I think I did a perfectly fine job of stating this was a model issue
b)this is apparent with any iron bars model with the top/bottom textures with cull:true set on those faces placed with different variants/rotations on top of each other, including default which just switched culling off on those faces.
Don't act like you can't guess where I'm coming from on this. It's clear the issue wasn't read, and you should be able to see why you going and bolding your comment right after I've already explained myself multiple times, paired with my disgruntled view of the bug tracker, would make me go off on a rant.
Most technical issues, ones not likely to be reported by normal users (especially if small or not prevalent with vanilla resources) don't get any attention if they're lucky. Things like this (the bug is now a duplicate even though it is not fixed, paired with mods deciding for Mojang that something is WAI) add a minefield for technical issues to traverse, to further cement their death before they can even get to an ignored state. So really the bug tracker seems to boil down to 90% of its value fixing major bugs that can be found with minimal testing, with occasional major issues for specific cases that take a while to notice, but are annoying or even feature breaking. So really it comes down to the bug tracker is mostly for things 50+ people are going to dupe. Why should I be happy about that, specifically when something like this happens?
EDIT: And looking through the issues that this is supposedly a dupe of, this issue is clearly different. MC-16587 and MC-19461 are specifically a torch somehow causing the top face to be improperly culled (which could be related to this issue, but why would a torch cause it?), MC-28145 and MC-18229 actually aren't this issue either (I thought it was at first, but just realized it's different), because the block is needed to cause culling on 1 legitimate face, which causes adjacent faces to be culled.
So those issues are caused by miscalculation somehow that results in too much to be culled. This issue is caused by blocks with different variants and rotations causing culling for other variants and rotations when they should not.