# Why is my mesh gets black?

**URL:** <https://forums.unrealengine.com/t/why-is-my-mesh-gets-black/1972395>\
**Category:** Off-Topic\
**Tags:** unreal-engine, question\
**Created:** [August 12, 2024, 6:51am UTC](https://forums.unrealengine.com/t/why-is-my-mesh-gets-black/1972395 "2024-08-12T06:51:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Quetzalcodename](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Quetzalcodename](https://forums.unrealengine.com/u/Quetzalcodename)\
**Post date:** [August 12, 2024, 9:50am UTC](https://forums.unrealengine.com/t/why-is-my-mesh-gets-black/1972395/2 "2024-08-12T09:50:28Z")

</div>

Hey @doaplz!

Are you having issues with the Megascans Trees: European Beech product? If so, check out this thread with a possible solution to the issue you are facing:

> [@Megascan Assets become Black in Ue5](https://forums.unrealengine.com/t/megascan-assets-become-black-in-ue5/570829/3):
>
> There’s a bug that if you have modified the base MS material, for example because of turning on the virtual textures, it sometimes doesn’t compile properly, but the editor won’t throw any warning until you open the base material (not just the material instance) and recompile it. Then you should check output log for errors regarding unsupported nanite features. I remember using one of the matlayerblend nodes which instead of the new get/set material attribute nodes uses the older break/make mate…

---

_[View the full topic](https://forums.unrealengine.com/t/why-is-my-mesh-gets-black/1972395)._
