Note: This issue can still be reproduced and has been several times. It is still present in the current pre-release (1.8-pre2) and can still be tested easily with the revised test steps I have listed. The test steps I provided when this bug was last tested were more unclear, not specifically mentioning to maintain a low render distance, not specifying a distance to travel away, and not specifying which chunks to conduct the test in. I have included all those now, and hopefully it will be much easier to see.
Contents:
1. Armor Stands, Item Frames, and Paintings
Explanation
Test
Further Testing
2. Mobs
Explanation
Test
Armor Stands, Item Frames, and Paintings:
When armor stands are placed or summoned with or without a custom name within a constantly loaded chunk (i.e. spawn chunks or entity processing chunks loaded by chunk loaders) and the player moves out of the chunks, then returning to the chunk with the armor stands, the armor stands will be unable to be seen but still be present. Armor stands become visible again upon exiting and reentering the world.
This is the same with item frames and paintings.
Occurs only in constantly loaded chunks.
Test:
1. Spawn a new world, preferably superflat so that it is easier to see, and at the exact point you spawn, place an armor stand. Record those coordinates. Set your render distance to smallest (2). (Further testing shows that render distance 2 to 5 all cause this issue if the player moves 100 blocks away and back)
2. Travel exactly 100 blocks in any direction, and remember those coordinates. Place another armor stand there.
3. Return exactly 100 blocks back in the direction of the first armor stand to find that it is gone.
4. Teleport to the armor stand(s) (for example: /tp @e[name=Bob] or /tp @e[type=ArmorStand,c=-1]) to see that the armor stands are indeed still present but completely invisible.
Teleport to item frames/paintings to see that they are present but completely invisible.
5. Travel exactly 100 blocks back to the second armor stand to find that it too is gone.
6. Teleport to the armor stand(s) (for example: /tp @e[name=Bob] or /tp @e[type=ArmorStand,c=-1]) to see that the armor stands are indeed still present but completely invisible.
Teleport to item frames/paintings to see that they are present but completely invisible.
7. Exit out of the world and enter it again and the armor stands/item frames/paintings reappear.
8. (Optional) Test with travelling more than 100 blocks from spawn, placing armor stands every 100 blocks. You may find that upon returning to the first armor stand, it is still visible, but then repeating step 1 to 4 causes it to disappear again.
Further Testing:
1. Create chunk loaders and spread them in any way you like. Make sure you make entity processing chunks by surrounding a chunk with 2 layers of chunks.
2. Repeat the very first test's procedures, placing the armor stands/paintings/item frames inside the entity processing chunks.
Further Notes: I tested this with putting one armor stand at the exact point I spawned in a new world. Then I moved 100 blocks away and placed another and kept doing this. At some point, if I move too far out then fly back to spawn, the original ones are visible still. However, if I continue and follow the test procedures again and move only 100 blocks out, they disappear again.
Mobs
Mobs are also disappearing when the player moves away from them, but the distance the player must move from them is different. From my tests I found them to be disappearing upon moving approximately 60 blocks away and coming back to them. It seems also to only occur in always loaded chunks, but of the lazy chunk variety.
Test:
1. Create a new world, superflat is preferred to see what is occuring. Set your render distance to 2.
2. /summon <mob> ~ ~ ~ {NoAI:1b}
2. Move exactly 50 blocks straight in any direction.
3. /summon <mob> ~ ~ ~ {NoAI:1b}
4. Move 60 blocks further in the same direction. /summon <mob> ~ ~ ~ {NoAI:1b}
5. Move 60 blocks back in the opposite direction to return to second mob. /tp @e[type=<mob>,r=10] to see that it is indeed still there but invisible.
6. Move 60 blocks in the original direction to find that third mob is still there.
7. Move 60 blocks back in the opposite direction to find mob is still invisible. Continue 50 more blocks to first mob to find that it is still there.
8. Exiting and entering the world will make invisible mob visible again. Note: dropped items do not seem to have this problem.
Related issues
is duplicated by
Attachments
Comments
migrated
onnowhere
The glitch is horribly troublesome and annoying, as all of the armor stands and paintings and item frames I place keep going invisible and I keep having to unload and reload the world. I have them used in a map I'm working on, and the map is pretty much useless with this glitch since players can't even see the armor stands if they unload...
migrated
Confirmed, seems to only happen on low render distance though.
michael
We can't reproduce this issue with the steps you described. Please provide a world download that reproduces this issue.
onnowhere
I believe it may only occur at the world spawn point. And it happens with all the new worlds I make.
onnowhere
I added an extra bit to the steps, maybe try it now?
migrated
This is still an issue in 14w34d - attached video shows proof.
onnowhere
Attached a video "Mc-66683.mp4": Clear demonstration of the bug using my test in a completely new world in 14w34d
migrated
There are two videos showing this hasn't been resolved. It needs to be reopened. Thanks!
onnowhere
And three other linked issues that relate...please reopen mods and/or try it yourselves too! It's still very much here and annoying as ever.
onnowhere
Still present in 1.8 pre-release. The problem isn't resolved and has been reproduced several times, including through video and several bug posts, and can be easily redone multiple times following the new steps I wrote using any new world's spawn chunks. Could any mod please try themselves and confirm this to show that this issue is not 'resolved'?
migrated
You aren't doing what Searge said to do:
Please provide a world download that reproduces this issue.
onnowhere
It can be done with any new world. Providing a world download wouldn't really make sense...I could send any of my worlds and they would all do the exact same thing....I mentioned to create a new world in my revised test steps....you could try it yourself too...
migrated
I don't enjoy this bug either, but please stop editing your comments. Every time you edit it, it sends a new email.
migrated
If you don't want to get notified, stop watching the issue.
Pepijn96
I have had this issue as well (in 1.8-pre1). But when I tried reproducing the problem, it worked in the beginning but later on I couldn't get it to work anymore. It didn't work after I loaded a lot of chunks I believe, so it might be only happening when not a lot of chunks are loaded in the world.
[Edit]
I have a world where I can keep reproducing the bug, but it's one of my projects... so I rather not give a world download in a 'public' comment section. Here is what I do to reproduce the bug:
http://imgur.com/a/d0iEb
(If any of the mods still wants the world download, you can contact me at [email protected])
onnowhere
Yeah, I mentioned to set your render distance to small in the revised steps. When you make the render larger, you are able to move further away from the armor stands, and somehow if you move far enough, they sort of re-render when you get back. I don't know why. It works for me with every new world I make to test the bug.
Render distance of 2 and moving 100 blocks away always works, at least for me.
Also, sorry about editing my comments so much 😛.
onnowhere
Still here in 1.8 pre 2...mods please check this, it's still here an still actually not resolved as ever...
onnowhere
I am working on a map that is centered around spawn chunks, and I have chunk loaders spread across the entire map to keep the whole thing loading so that I can always control all the item frames and armor stands that I use to make the map possible. I'm using item frames as a collection mechanic and for decor and using armor stands for decor and creating a 'custom' mob (i.e. Slenderman). With this bug, if players were to play it, they would just be missing many of the item frames/not seeing many of the armor stands since they go invisible, making the map pretty much useless. All the chunks are loading so that means the bug is present in the entire map, not just the spawn chunks, with a low render distance.
onnowhere
Still here in pre 3
migrated
I'm also currently working on an adventure map, and this happens to me whenever the chunk with the armor stand in it unloads. When I go back to where the armor stand is, reloading the chunk, it completely disappears. The weird thing is, I thought maybe they were becoming completely invisible for some reason, but they don't show up in Spectator mode either.
I've kept my render distance at about ten, which I think is relatively average, and the issue continues, so I do think it has something to do with the chunk unloading.
migrated
Confirmed In Pre Release 3
migrated
For me only the item frames facing north and south disappeared, the east/west were still there.
I change my statement. I placed item frames all around that empty chest on a log in the middle of the image http://i.imgur.com/kacGANx.png to confirm my theory, but they all went invisible (and undetectable).
Every chest in this image has a item frame on them. You can cleary see not all went invisible though.
onnowhere
Still in 1.8
onnowhere
I have been testing, and it appears this also occurs with mobs, not just armor stands, item frames, and paintings. Dropped items do not seem to be affected though.
I added a mob section to the explanation.
kumasasa
This ticket may explain the "invisible" part of MC-65040
migrated
Yes.. We have in MC-65040 done a total analysis of this with over 1000 tests of different sorts.
It is the exact same bug. Video in this report confirms that.
and.. @unknown As we have explained several times in MC-65040, the invisible part is the only part that should be in that bugreport. The other parts are introduced by you.