# Lightmap too large despite no static shadows set on foliage

**URL:** <https://forums.unrealengine.com/t/lightmap-too-large-despite-no-static-shadows-set-on-foliage/414176>\
**Category:** World Creation\
**Tags:** unreal-engine, Foliage, Lightmap, build-failed, question, static-shadows\
**Created:** [January 9, 2018, 10:44pm UTC](https://forums.unrealengine.com/t/lightmap-too-large-despite-no-static-shadows-set-on-foliage/414176 "2018-01-09T22:44:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tooroo](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Tooroo](https://forums.unrealengine.com/u/Tooroo)\
**Post date:** [January 9, 2018, 10:44pm UTC](https://forums.unrealengine.com/t/lightmap-too-large-despite-no-static-shadows-set-on-foliage/414176/1 "2018-01-09T22:44:46Z")

</div>

Hey guys,

The log under Lighting Results states:  
_“InstancedFoliageActor\_0 The total lightmap size for this InstancedStaticMeshComponent is large, consider reducing the component’s lightmap resolution or number of mesh instances in this component”_  
and the **lightmap does not compute**.

I know there is a gazillion threads about this warning/error but the funny thing is that **none of my foliage has static shadows turned on**.

It’s an archviz project. I don’t want to disable static lighting entirely because I need it for my building. So back to the foliage:

- At least 95% is painted using the foliage painting tool.
- All of it is set static but with Cast Static Shadows off
- For trees and bushes Cast Dynamic Shadow is set to on, for patches of grass, it is set to off

**Any ideas what could be causing this error?**

I have also tried setting all of the foliage to Movable but it doesn’t help much. I’ve tested it on a cut-down version of the scene (to the point when the lighting builds) and it speeds up the building about 30%.  
But should foliage even be set to Movable despite it’s not going anywhere? I thought that setting it to static would have some performance/optimization benefits.

---

<div class="post-metadata">

**Author:** ![alenwesker](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@alenwesker](https://forums.unrealengine.com/u/alenwesker)\
**Post date:** [May 20, 2019, 4:03am UTC](https://forums.unrealengine.com/t/lightmap-too-large-despite-no-static-shadows-set-on-foliage/414176/2 "2019-05-20T04:03:08Z")

</div>

See this, I think this is buggy.

> **[Foliage + Lightmaps is broken/bugged/dysfunctional - Detailed explanation](https://forums.unrealengine.com/questions/560394/foliage-lightmaps-is-brokenbuggeddysfunctional-det.html)**
>
> So I’ve been looking into this issue for a the past few days now and have come to the conclusion that either foliage with baked static lighting is currently fundamentally broken due to what seems like some design oversights, or that I’m missing...

Foliages in one landscape component can only have one lightmap(If you paint will foliage panel), which is not enough in most cases.

The best solusion should let foliage use landscape lightmaps, which should not be so difficult, and that is what the engine used in my project supports. Go do it, Unreal guys.