[MC-98146] Marker armor stand does not render in some cases

The bug

Marker armor stands, due to their hitbox being tiny and the new rendering methods being based on the hitbox location (I presume), cause them to easily stop rendering.

How to reproduce

```
/summon armor_stand ~ ~ ~ {Marker:1b}
```
Stand close to it and slowly look up
Armor stand stops rendering / disappears

Linked issues

is duplicated by 7

MC-130007 Marker Armor stands disappear if you look up Resolved

MC-131372 Standing in same block as marker armor stand while looking at it directly at eye level causes it to disappear Resolved

MC-156826 Marker Armor stands become invisible Resolved

MC-188917 Armour stands with the marker tag disappear Resolved

MC-190321 Armor Stands with the Marker tag stops rendering in certain player rotations Resolved

2 more links

relates to 2

MC-1058 A dragon head is invisible if the entity wearing it is not in view Resolved

MC-96853 Large block models stop rendering prematurely on ArmorStands/Entities when leaving player's field of view. (e.g.: Dragon Head on ArmorStand) Resolved

Attachments

MC-98146.mp4

Comments 41

SunCat 2016-02-27T09:51:09Z

Already mentioned in MC-96853, but probably it's better to have a separate ticket for it

Meri Diana 2016-02-27T16:56:18Z

Confirmed, like already mentioned in MC-96853
I'm assuming using a Marker-tag set to true is what mapmakers do more often than leaving it to false.

Thus, if it's possible to fix, and nobody of the mapmaking community can present reasons why it must not be fixed, it'd be great if it could be fixed before 1.9 release.

Meri Diana 2016-03-30T14:59:29Z

Confirmed for 1.9.1 Release.

Meri Diana 2016-04-27T20:33:52Z

Confirmed for 1.9.3 pre-2.

Meri Diana 2016-05-26T00:08:17Z

Confirmed for all previous versions I didn't confirm it for in here, up to/incl. the current 16w21a.

31 more comments

Meri Diana 2016-05-29T00:01:37Z

Confirmed for 16w21b.

Meri Diana 2016-06-07T16:26:43Z

Confirmed for 1.10 pre-2 + pre-1.

Meri Diana 2016-06-22T21:03:47Z

Confirmed for 1.10.1

Meri Diana 2016-06-23T12:52:41Z

Confirmed for 1.10.2

Meri Diana 2016-08-11T08:53:11Z

Confirmed for 16w32a.

Meri Diana 2016-08-11T15:39:56Z

Confirmed for 16w32b.

Meri Diana 2016-08-17T15:35:15Z

Confirmed for 16w33a.

Meri Diana 2016-09-03T06:56:09Z

Confirmed for 16w35a.

Meri Diana 2016-09-20T21:13:45Z

Confirmed in 16w36a, but apparently fixed for 16w38a?
Please do NOT mark this bugpost here as fixed rightaway, please read: MC-107172

user-f2760 2016-09-20T21:23:44Z

If it's fixed, it's fixed, we'll reopen the bug if it reoccures in a later version.
(And before you ask, yes, I did read the ticket)

Meri Diana 2016-09-20T21:27:28Z

The reason why I'm so cautious and say "please do not resolve it as fixed" is that it doesn't seem to be intended - okay, Devs not always assign themselves to a bugpost when they fix it, but at the least they MARK it as fixed, and it wasn't done here.

So my assumption/fear is that whatever got changed UNINTENTIONALLY fixed this bugpost here, and I just want to make sure that it does not reoccur, and the Dev can look into what he changed and thus figure out the reason for the fix, so it:
a) won't happen again and
b) he/she doesn't have more work, as they might have to search more after a while, when it reoccurs, and they maybe forgot what they did that it unintentionally fixed.

user-f2760 2016-09-20T21:33:54Z

A lot of times bugs are fixed without a dev marking them as such, simply by forgetting or not finding the ticket.

Don't worry too much about it, if it changed for the good, it's likely intentional.

Meri Diana 2016-09-20T21:37:46Z

Okay.. ;-;
I'm just scared it is not an intentional fix and we'd lose it again }xD

This fix is GREAT for the mapmakers, if it is intentional they totally should have bragged with it in the post and not forget it!
It's very much needed for better player immersion with also e.g. large block models etc.

I'll be cautiously happy now.. will blame you if it reoccurs };]