When moving Lighting Scenario Levels and their associated Map Build Data Registry to a new folder within the Content Browser, the references within the Levels tab are updated as [MapName_BuiltData].
This in turn breaks the functionality of the suggested workflow when calling Lighting scenarios to load/unload via the Level Blueprint from the Persistent Level.
The only way I have found to fix this error is to select the individual [MapName_BuiltData] level and using the Remove Selected option. Then going to the levels dropdown and using the Add Existing option. You can then delete the old Map Built Data Registry that was duplicated in the main content browser.
1. Open attached project.
2. Press PIE.
3. Press the 'L' key to alternate between Lighting Scenarios.
4. Exit PIE
5. Move the Levels and Map Build Data Registry to the Maps folder.
6. Repeat steps 2 and 3.
Outcome The levels window has had the previously referenced names updated to the [MapName_BuiltData]. This is turn causes the level blueprint functionality within the Persistent Level to break when calling to load and unload the level.
Expected The maps and the map build data are moved to the folder and the level names remain constant.
I am not able to find world outliner how to enable it?
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
Delay nodes occasionally don't fire the "Completed" output in a nativized build
Bullet replication problem. The players sees each other but does not see the bullet
How to achieve HLSL Multiple Render Target in Material blueprints?
When I open UE4 4.24.3 it appears that. Does anyone know how to solve?
How does UMG set overlapping layouts?
Hey, why do i get this when i snap two similar meshes together?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-41487 in the post.