Description

When setting up a scene with a persistent level and any sublevel that contains a landscape that is loaded via load stream level node in the level BP can cause the ILC to not be correctly assigned for a movable object or any objects that use the ILC for their lighting.

I have a test scene attached that goes through several different scenarios in testing this with specific assets and ILCQ designations for volume or point.

This is some additional notes for what I've found while investigating this.

  • Only happens in PIE from my what I have found and not always consistent.
  • affects all or some objects that use the ILC for lighting.
  • Requires Sub-Level with object to be streamed in. Will not work if always loaded.
  • Increasing the number of Volume Light Samples in the World Settings will get rid of this problem.
  • Changing the ILCQ (movable actors details panel) to Volume will NOT cause the issue. POINT will will cause the issue.
Steps to Reproduce

1. Open UE4
2. Create a map (persistent) with one additional level (sub Level 1)
3. In Persistent Level BP set up an event begin play to load stream level for the sub level
4. Place a movable object in the sub level
5. Add a landscape (I used a very small one for this test)
6. Build Lighting (inclusion of LIV makes no difference)
7. PIE

Results: (more detailed notes in comments) This looks like the ILCQ for any foliage object using static lighting only or movable object using the ILCQ for lighting is not being loaded when a landscape is in the scene. This is not true if just using static meshes.

Expected: Movable objects and foliage object using the ILCQ for their lighting should load in properly when a map is streamed in.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-17784 in the post.

0
Login to Vote

Fixed
ComponentUE - LD & Modeling - Terrain - Landscape
Affects Versions4.74.84.9
Target Fix4.9
Fix Commit2610758
CreatedJun 26, 2015
ResolvedJul 6, 2015
UpdatedApr 27, 2018
View Jira Issue