Lioncat6
- Lioncat
- JIRAUSER572715
- America/Chicago
- Yes
- No
MCPE-106786
Whenever villagers go to sleep they will teleport to different locations
In the one of the attached pictures (the one in my Minecraft basement) you can see some villagers not aligned properly with the beds and some empty beds as well because the villagers teleported trough the wall and the two or three villagers standing up can't path find to their beds because of the villagers in the way
In the picture above my basement with the glass floor you can see villagers half on the beds
Whenever villagers go to sleep they will teleport to different locations
In the one of the attached pictures (the one in my Minecraft basement) you can see some villagers not aligned properly with the beds and some empty beds as well because the villagers teleported trough the wall and the two or three villagers standing up can't path find to their beds because of the villagers in the way that have teleported but the hitboxes are still their
In the picture above my basement with the glass floor you can see villagers half on the beds
whenever the villagers wake up they are still missing and only reappear when I relaunch the world
Minecraft 11_19_2020 6_56_07 PM.png
sometimes the villager "ghost" (as I call it) will stay their frozen during the day sometimes
In my testing the villagers will catch on fire on the client side but will not die, when I teleported the villagers back to my location after pushing the statures through the lava they were still there, however all but one were invisible, and I was not able to get the images of the villagers to reappear
No, that glitch is the result of entity cramming
I have tested this in 3 worlds and it was consistent in 2 out of the 3 I tested.
The first image is seed -2011628174 Coordinates: x1750 y53 z-1720 and is the one without the bug as it is on the very edge of a kelp biome
The second image is seed -828512159 at coordinates -859 50 -724 and has the bug present
The third image at seed 448577044 coordinates -724 51 1174 has the bug too
Game Version 1.16.201 - Minecraft bedrock
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX. Because of this, when the world preview screenshot is taken, its while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).
Steps to Reproduce:
- Get Any RTX resource pack ( I used[ Radiant Pack RTX |https://www.planetminecraft.com/texture-pack/radiant-shader/)]
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me I couldn't find this reported anywhere else...
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX. Because of this, when the world preview screenshot is taken, its while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).
Steps to Reproduce:
- Get Any RTX resource pack ( I used[ Radiant Pack RTX |https://www.planetminecraft.com/texture-pack/radiant-shader/)]
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me, I couldn't find this reported anywhere else...
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX. Because of this, when the world preview screenshot is taken, its while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).
Steps to Reproduce:
- Get Any RTX resource pack ( I used[ Radiant Pack RTX |https://www.planetminecraft.com/texture-pack/radiant-shader/)]
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me, I couldn't find this reported anywhere else...
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX. Because of this, when the world preview screenshot is taken, its while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).
Steps to Reproduce: (Attached is a video of me fallowing these steps)
- Get Any RTX resource pack ( I used[ Radiant Pack RTX |https://www.planetminecraft.com/texture-pack/radiant-shader/)]
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me, I couldn't find this reported anywhere else...
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX. Because of this, when the world preview screenshot is taken, its while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).
Steps to Reproduce: (Attached is a video of me f
allowing these steps)
- Get Any RTX resource pack ( I used[ Radiant Pack RTX |https://www.planetminecraft.com/texture-pack/radiant-shader/)]
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me, I couldn't find this reported anywhere else...
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX. Because of this, when the world preview screenshot is taken, its while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).
Steps to Reproduce: (Attached is a video of me following these steps)
- Get Any RTX resource pack
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me, I couldn't find this reported anywhere else...
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX.
Because of this, when the world preview screenshot is taken, its while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).Steps to Reproduce: (Attached is a video of me following these steps)
- Get Any RTX resource pack
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me, I couldn't find this reported anywhere else...
When Saving any world, Minecraft tries to take a screenshot of sorts for the world preview. When RTX is enabled, one of the game's steps while saving and exiting is Disabling RTX. Because of this, when the world preview screenshot is taken, it's while the game is disabling the rendering of RTX leading to these fragmented world previews (attached).
Steps to Reproduce:
- Get Any RTX resource pack
- Load up any world with RTX Enabled
- Press Save and quit
- Look at the world preview
I'm aware that this might be a duplicate, but for the life of me, I couldn't find this reported anywhere else...
![[MCPE Mod] Auldrick](../../../data/avatars/users/10122.svg){kind=small}
Lioncat6: I've seen hints about that in comments, but they haven't been explained clearly enough for me to incorporate into the observations. Could you explain in more detail? For clarity, please use the terms "statue" for the villager image and "ghost" for the invisible villager in the bed, and tell me what you did and what your friend saw. Note that "interacting" is too generic a term. Some of the ways you interact with a mob are detected by the client (the statue side), and some by the server (the ghost side).
Lioncat6: Thank you. I'm going to try to reproduce that myself using separate accounts on two devices.
Cody: The client does all rendering, including animations. Because the latter involve a lot of redrawing, the client controls them autonomously because if it had to take orders from the server to animate, it would be very jerky. So I think the client detects when something flammable is near lava and gives it the fire animation. It then informs the server that the object or entity is touching lava, but the server doesn't know of any such object or entity at that location so it ignores the information. Since the server keeps track of damage, your villager is burning but doesn't accumulate any damage. As for the rest, I can't explain why when morning comes it doesn't self-correct. But then, I'm not a developer and don't have access to the details of mechanics. For yours and other comments, I'm starting to be persuaded that not all the workarounds I included above are completely reliable.
Drew: The bell info is a good addition. I hadn't tried a bell before, but I did know that it normally causes villagers to immediately go to their beds. I found out it can also work as a workaround. I was in a flat world and floated a villager a good way out, then rang the bell. I watched as it spent a few seconds coming back to its bed, teleporting like an enderman.
Mari Marsh: After viewing your video, it seems certain that the cramped quarters are causing you to collide with the villagers in their beds long enough, and for enough time cumulatively, to make them float away as far as the client can send them. (There's a limit to how far the client can reach.) They always disappear when they get that far. If you chase after one and manage to find it out there, you'll glimpse it briefly, and then it will teleport back to its bed. All of that is covered in the documented observations above, although it's broken out in such detail that you'd have to put it all together before this behavior would become obvious.
Contrary to what the observations states, I was playing on a multiplayer world and another player was able to see me interacting with the villager image and could move it as well at the same time
Ok, so when the villager went to sleep normally in the bed I pushed the "statue" off of the bed and it started floating off and it stopped, my friend was able to see that , and from its stopped position my friend was able to push it the other way, and I was able to to the same to "statures" he pushed off the beds
This is indeed still an issue. I figured it wasn't a bug, but yes, no items emit light when held on Minecraft bedrock when using RTX.
Shaderpack being used:
Radiant Shader Minecraft Texture Pack (planetminecraft.com)
This is no longer still an issue, from what I've seen.
It seems I can no longer cause the bug to happen with any resource pack... Even with the one shown in the video.
Something else must have been going on.
When flying around in dark caves, when you get to a spot that isn't quite rendered in completely, it will appear that there is light from outside coming in, but once it renders in it returns to normal.
Steps to reproduce:
I'm not sure if there is that much to be done about this, as it just seems to be part of the rendering process.
Video of this happening:
https://www.mediafire.com/file/oignommgfbapwnd/Minecraft+2022-01-03+09-13-46.mp4/file
Edit:
afterward, I did try again with a resource pack that didn't make ores glow, and received a similar result. The glowing ores seems to magnify this affect a bit
Yep, This is still an issue, it seems to happen randomly after playing multiplayer for while... certain parts of skins get placed in random places on the player's body
Game version 1.18.10
Yep, This is still an issue, it seems to happen randomly after playing multiplayer for while... certain parts of skins get placed in random places on the player's body
Game version 1.18.10
Yep, This is still an issue, it seems to happen randomly after playing multiplayer for while... certain parts of skins get placed in random places on the player's body
Game version 1.18.10
Pack I was using: https://www.planetminecraft.com/texture-pack/radiant-shader/
Still affects 1.18.30
This Seems to still happen, but there is no recognizable pattern about what causes it. 1.18.31 is affected. For me, it only really happens if you close the game with alt+f4 but It can also happen at seemingly random times when launching the game with RTX enabled.
this doesn't seem to be an issue on the hive, but the one server where I see it the most is Mineplex
RTX pack I use: https://www.planetminecraft.com/texture-pack/radiant-shader/
I have one issue, however. PBR textures don't seem to affect entities...
I can confirm that this still affects 1.19.2
If you set the metalness to nothing and the roughness to 100% on the MER texture and the opacity of the color map to 1% white, it appears correctly in-game, as for the item in the Hotbar, you can set it to use a separate unmodified carried block texture (though I've yet to get the carried texture to appear right).
Update: I fixed the carried textures (forgot waxed copper stuff exists lol)
Fix will be included in radiant pack rtx if you want to see how I implemented it
I'm pretty sure the reason this happens in the first place is I believe the game only ever generates the texture altas when loading into a world, hence the 'loading resource packs' section of the loading screen. When rtx is disabled, it doesn't load any pbr textures into the atlas, so whenever you enable it after this point, the game can't load them and it gets incorrect texture data from somewhere in the atlas. This is just my theory on what's happening though. Could be fixed by either always loading the pbr textures into the atlas, or adding a way to reload the resource packs in-game, simular to Java (would only happen the first time rtx is enabled).