primemods - OUT NOW: "Line Bug" Fixed! & New Bedrock Textures + Java Fixes
infoAbout This Title
Sike - I know I said the next time you'd hear from me it would be with new textures; but "The Line Bug" has finally been cracked, and it was essential that a hotfix come out immediately.
Since an update had to come out anyway, I decided to include a couple more things I had been working on, including ports of a couple of the missing textures into the Bedrock pack, and a handful of other fixes for both Java and Bedrock.
The next section gets a bit messy and goes into detail about how I managed to fix this specific issue, for the like three people that are going to be interested. If you want to skip the nerdy stuff, feel free scroll past it to "Wilderness Bound", which is followed by the changelog for this update at the bottom of the page.
The Line Bug
If you're a Java pack user, or just out of the loop, I'm referring this rendering issue that could appear on certain devices running the 32x resolution of the Bedrock pack:
It has been present since the port's launch, and affected a sizeable amount of users.
For the past week I've had no luck in getting anywhere closer to solving it, as it could not reliably be reproduced, and there was no documentation about it anywhere online.. until this morning. While porting the command blocks over (also included in this update), the bug mysteriously appeared on my system. Up until this point it had only been seen on mobile devices.
Although I first assumed something in the command block files was causing it, but after some testing I learned it wasn't the command blocks in particular, but the fact that I had added any files at all; as removing any couple textures would revert the game to the non-bugged state.
The only thing I could see total texture volume directly affecting was the game's texture atlas. An easy way to think about this, is that when loading a resource pack Minecraft first takes all the textures in the pack and combines them into a single sort of image. Then when rendering a block, it pulls from the part of the image that that block's texture is located.
Another important mechanic to understand here is "mipmapping", a feature in games which reduces the resolution of a texture the further it gets away from the player to save on performance.
Now my hunch about the texture atlas turned out to be correct, as after looking into atlas related issues I found bug MCPE-240144.
You see up until this point, Minecraft has included a couple pixel buffer in between each texture on the atlas, to prevent any textures "bleeding" into each other when the resolutions are reduced through mipmapping. That is until Bedrock 26.30, where Mojang seemingly randomly removed this feature.
This is unnoticeable in most cases; but occasionally when you either have a highly complex pack (like PHDT), or are loading multiple packs at once, at a resolution that is both larger than vanilla, yet low enough as to not correct itself, and are on specific hardware; you can overload the atlas causing textures to bleed over into their atlas neighbors into small strips. Which is exactly what was happening here.
This bug has been present for 3 months, and Mojang has yet to fix it - fortunately, there is a temporary solution. By manually lowering the mipmap levels within the pack (which thankfully is something I can do), we can push the atlas out of it's overwhelmed state. Although this may slightly reduce the overall "smoothness" of textures at a distance (although probably not very noticeably), it is a trade-off I believe is clearly worth it. As well, the change has only been applied to the 32x version of the bedrock pack.
Wilderness Bound
Assuming this hotfix works for everyone, and I won't need to cook up a quick 56.2.1 - the next thing on the agenda is beginning on the new Wilderness Bound textures!
Development Council tier members were able to vote the other day on the prioritization of features, and here's the results:
Therefore it looks like the first textures to be completed will be the poplar trees, followed by the new bed and maps, the cushions and poplar wood stuff, and finally the new mushroom and shrub :)
Update 56.2 Changelog
JAVA
Fixed the nether star in every pack being a resolution below what it should be
Fixed the pink petals (item) in every pack being a resolution below what it should be
Fixed broken bamboo sign
BEDROCK
Ported over all command blocks from the Java pack
Ported over all beds from the Java pack
Ported over all shulker boxes (and shulkers) from the Java pack
Fixed bug where some users would get a parallel line rendering issue in the distance when using the 32x pack on some devices
Fixed the nether star in every pack being a resolution below what it should be
Fixed the pink petals (item) in every pack being a resolution below what it should be
Fixed bug where the main menu panorama would become de-saturated when vibrant visuals were enabled
Sike - I know I said the next time you'd hear from me it would be with new textures; but "The Line Bug" has finally been cracked, and it was essential that a hotfix come out immediately.
Since an update had to come out anyway, I decided to include a couple more things I had been working on, including ports of a couple of the missing textures into the Bedrock pack, and a handful of other fixes for both Java and Bedrock.
The next section gets a bit messy and goes into detail about how I managed to fix this specific issue, for the like three people that are going to be interested. If you want to skip the nerdy stuff, feel free scroll past it to "Wilderness Bound", which is followed by the changelog for this update at the bottom of the page.
The Line Bug
If you're a Java pack user, or just out of the loop, I'm referring this rendering issue that could appear on certain devices running the 32x resolution of the Bedrock pack:
It has been present since the port's launch, and affected a sizeable amount of users.
For the past week I've had no luck in getting anywhere closer to solving it, as it could not reliably be reproduced, and there was no documentation about it anywhere online.. until this morning. While porting the command blocks over (also included in this update), the bug mysteriously appeared on my system. Up until this point it had only been seen on mobile devices.
Although I first assumed something in the command block files was causing it, but after some testing I learned it wasn't the command blocks in particular, but the fact that I had added any files at all; as removing any couple textures would revert the game to the non-bugged state.
The only thing I could see total texture volume directly affecting was the game's texture atlas. An easy way to think about this, is that when loading a resource pack Minecraft first takes all the textures in the pack and combines them into a single sort of image. Then when rendering a block, it pulls from the part of the image that that block's texture is located.
Another important mechanic to understand here is "mipmapping", a feature in games which reduces the resolution of a texture the further it gets away from the player to save on performance.
Now my hunch about the texture atlas turned out to be correct, as after looking into atlas related issues I found bug MCPE-240144.
You see up until this point, Minecraft has included a couple pixel buffer in between each texture on the atlas, to prevent any textures "bleeding" into each other when the resolutions are reduced through mipmapping. That is until Bedrock 26.30, where Mojang seemingly randomly removed this feature.
This is unnoticeable in most cases; but occasionally when you either have a highly complex pack (like PHDT), or are loading multiple packs at once, at a resolution that is both larger than vanilla, yet low enough as to not correct itself, and are on specific hardware; you can overload the atlas causing textures to bleed over into their atlas neighbors into small strips. Which is exactly what was happening here.
This bug has been present for 3 months, and Mojang has yet to fix it - fortunately, there is a temporary solution. By manually lowering the mipmap levels within the pack (which thankfully is something I can do), we can push the atlas out of it's overwhelmed state. Although this may slightly reduce the overall "smoothness" of textures at a distance (although probably not very noticeably), it is a trade-off I believe is clearly worth it. As well, the change has only been applied to the 32x version of the bedrock pack.
Wilderness Bound
Assuming this hotfix works for everyone, and I won't need to cook up a quick 56.2.1 - the next thing on the agenda is beginning on the new Wilderness Bound textures!
Development Council tier members were able to vote the other day on the prioritization of features, and here's the results:
Therefore it looks like the first textures to be completed will be the poplar trees, followed by the new bed and maps, the cushions and poplar wood stuff, and finally the new mushroom and shrub :)
Update 56.2 Changelog
JAVA
Fixed the nether star in every pack being a resolution below what it should be
Fixed the pink petals (item) in every pack being a resolution below what it should be
Fixed broken bamboo sign
BEDROCK
Ported over all command blocks from the Java pack
Ported over all beds from the Java pack
Ported over all shulker boxes (and shulkers) from the Java pack
Fixed bug where some users would get a parallel line rendering issue in the distance when using the 32x pack on some devices
Fixed the nether star in every pack being a resolution below what it should be
Fixed the pink petals (item) in every pack being a resolution below what it should be
Fixed bug where the main menu panorama would become de-saturated when vibrant visuals were enabled
Comments (0)