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
Related issues
is duplicated by
relates to
Attachments
Comments


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

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.

Confirmed for 1.9.1 Release.

Confirmed for 1.9.3 pre-2.

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

Confirmed for 16w21b.

Confirmed for 1.10 pre-2 + pre-1.

Confirmed for 1.10.1

Confirmed for 1.10.2

Confirmed for 16w32a.

Confirmed for 16w32b.

Confirmed for 16w33a.

Confirmed for 16w35a.

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

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)

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.

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.

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 };]
Due to the fixes of other armor stand related bugs, this issue is back in 16w44a.
Can confirm for 1.13-pre3

Happens in the latest snapshot (19w09a).

Confirmed it's still happening in 1.16.3. Really hoping this ever gets fixed again.
Can confirm in 20w48a.

Can confirm in 1.16.4
Can confirm in 21w03a.
Can confirm in 21w05b.
Can confirm in 21w06a.
Video attached.
Can confirm in 21w07a.
Can confirm in 21w11a.
Can confirm in 1.16.5 and 21w14a.
Can confirm in 21w17a.
Can confirm in 1.17.
Can confirm in 1.17.1.
Can confirm in 1.18.1.
Can confirm in 1.18.2 and 22w15a.
Can confirm in 1.19.

Can confirm in 1.19.1

Can confirm in 1.19.2.

Can confirm in 1.19.3.

Can confirm in 1.21.4.