MC-167243Beds renders white on the side where the second part should be
Beds renders white on the side where the second part should be. This isn't case with other second-part blocks that I saw.
Linked Issues
Created Issue:
Beds renders white on the side where the second part should be
Beds renders white on the side where the second part should be. This isn't case with other second-part blocks that I saw.
Attachments2
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
relates to
is duplicated by
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
is duplicated by
The bug
Certain textures no longer can be retextured with a texture that is partially transparent. This affects textures that are completely opaque in the vanilla resource pack, such as:
Signs(20w06a)- Paintings
- Item frames
- Shields (WAI, see
MC-165403) - Beds (Won't Fix, see
MC-167243) - Beacon beam
- Book on the enchanting table
- Conduit
- Trident (entity form)
This list may be incomplete.
Yeah MC-167243 was marked as Won't Fix
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-167243, which has been marked as Won't Fix - while this behaviour is not desirable, the developers have said that they will not or cannot fix it.
Please use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Thank you for your report!
We're tracking this issue as MC-167243, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit
Relates to: MC-176095 MC-199660 MC-208679 MC-250985 MC-271303
May also relate to: MC-159560
The bug
The texture files for beds all contain an unused row of black pixels at the very bottom, and an unused column of black pixels at the very right. This affects all colours of bed except red (although in Programmer Art, all 16 colours are affected).
In addition, every bed has 72 pixels which are used by the model, but can never be seen without clipping inside of the bed, corresponding to where the feet meet the bottom of the bed. While removing these does change the way beds look on the inside in Spectator mode and such, it is not a concern at all given the resolution of MC-167243, and they look completely the same from the outside anyway.
How to fix
Remove all these pixels from the texture file. I have attached fixed versions of all texture files to this ticket - it should be as simple as replacing the default textures with these sixteen, and Programmer Art's with the other sixteen (included as a zip as to not exceed the weird 30-file limit).
The bug
Beds are considerably more resource-intensive to render compared to other blocks in the game, even those with more complex models. This is due to a multitude of factors:
- Beds still unnecessarily utilise block entities, which were previously used for distinguishing color prior to 1.13 but are no longer required due to separate alphanumeric IDs after this point. (
MC-122532) - Each whole bed renders six planes that are never visible in normal gameplay. Two of these correspond to the interior of the bed, across the edge of a block (
MC-167243), whereas the other four correspond to the top faces of each of the four feet of the bed. - When a bed is adjacent to a block of the exact same type, the occluded faces are still rendered, rather than culled as is done with most other correctly-modelled blocks. (MC-141306)
The negative effects of this can be felt quite easily in areas with large numbers of beds, such as villager breeding stations and large iron farms.
How to reproduce
Attached to this ticket is a zip file containing two worlds. A resource pack is also attached which creates equivalent bed models: copper grates are remodeled to the foot of a bed, and oxidised copper grates to the head of a bed. An item model for beds also replaces the cobweb item model.
- Download and apply the attached resource pack
- Set your render distance to 2 and FOV to default, and turn off VSync
- Open the "bed platform" world
- Use F3+2 to open performance graphs
/tp @s 8.5 -60 8.5 180 -22.5
- Observe
- Exit this world and repeat for the improved platform world, observing
Expected results
Beds would not hurt performance.
Actual results
They noticeably do.
How to fix
Should be simple enough: get rid of the block entities for beds and convert them back over to proper block models. Performance should increase considerably.
This would also permit resource pack creators to customize bed models once again, and would fix issues such as MC-69683 and MC-231102 for beds.
DelimanCZ please don't update reports that have been resolved as won't fix. They aren't considered valid bugs anymore.
Isn't this intended to be the mattress of the bed?
You would expect it to be like the 1.14.4 screenshot. Normally if you have a full 1x2 bed you can see through to the other side from the bottom. They probably resolved as Won't Fix because you normally do not expect to have a 1x1 bed piece.
Why is this Won't Fix? Can an explanation please be provided? This also affects custom textures that use transparency elsewhere, and has broken one of my resource packs.
Luke W yes, but they rather kick me from this issue, than fix this simple problem...