If an armorstand is first to render, elytra will render on it with additive blending, so will every armorstand and one entity rendered subsequently, if there's no items in the world.
Elytra on players will render with broken textures if they're holding an item and with their skin data if they're not enchanted.
Note: this is a complex issue and I'm not sure about whether all the details are correct.
From MC-107780:
The elytra texture is messed up when one of the hands are full it shows the textures of all the items in the shape of the elytra and with both hands empty it shows your skin in elytra shape
Related issues
is duplicated by
Attachments
Comments


The transparent part is MC-99353

You should try F3+t when this happens, and share the results.

@unknown in case you are referring to a forced crash, it is F3
+ C
for 10 seconds. But the crash report will very likely not show anything relevant.

Confirmed. Also, summoning zombies above the clouds with elytra equipped and the FallFlying tag set to 1, will make the elytra and zombie look bright white.

Marcono1234 I said what I meant, F3+t is for reloading all recourse-packs, including the default. The game sometimes picks the wrong texture/sound when the client is overloaded.

Oh ok sorry then. But it looks like that does not fix the problem.

Duplicates MC-107152

@unknown: That's not how it works. This is the first report for that issue.

Also renders the player skin too. No idea how it did though. It first rendered all the items textures, then loaded my skin as the model.

i have same proplem

I tried F3 + T but it did not
my english is bad 😞

This is happening to me too. It's weird. It shows the item textures when you're holding an item, but shows your skin texture when not.

Unable to reproduce with the following system details:
Minecraft Version: 16w38a
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_102, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 177265432 bytes (169 MB) / 346435584 bytes (330 MB) up to 2134114304 bytes (2035 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 16w38a
LWJGL: 2.9.4
OpenGL: GeForce GTX 850M/PCIe/SSE2 GL version 4.5.0 NVIDIA 372.90, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: No
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs:
Current Language: English (US)
Profiler Position: N/A (disabled)
CPU: 8x Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz

https://youtu.be/w7MdxLCqrSs
Might be easier to understand and it is reproducible.

How is this still not assigned?

Only the developers assign tickets and they only do it when they start work on it. It will get fixed and they are aware of this issue.

Still in 16w39b

Yikes, this got worse in the 16w39 snapshots. I'm getting the stitched-together mess seen in B.png

ye i am in snapshot 16w39b and I was gonna make a adventure map but then it just came up as this: http://imgur.com/a/8H3Ac and now I cant use the elytra cause of the texture is wrong

awww i liked it and its gone