This is the documentation for Enlighten.
By default, the Enlighten data generated by the precompute is stored within each .umap file. You can't run the precompute and save the Enlighten data when the .umap is locked for editing by another user. This makes it difficult to collaborate on levels.
To resolve this, move the Enlighten data to a separate .uasset file.
File > Save saves only the current level. It doesn't save Enlighten data stored in a separate asset. Use File > Save All to save all modified assets.
To find the precompute data for a level, select its EnlightenSystemContainer actor. The Precompute Data value in the Details tab displays the name of the asset that contains the Enlighten data, or displays "In Level":
Enlighten data stored in asset | Enlighten data stored in level |
---|---|
If the precompute data is stored in an asset, you can use the
button to locate it in the Content Browser.When you add a sublevel, if the Enlighten precompute data for the persistent level is stored in an asset, the precompute data for the new sublevel is moved to a new .uasset file if necessary.
When you move precompute data to an asset file, the .uasset file appears in the same folder as the .umap file, named <mapname>_EnlightenData.
When you change the name of a level, the name of the .uasset file no longer matches the .umap. Enlighten gives you the option to automatically rename the .uasset to match.
After you move the data to match, choose File > Save All to save the modified assets.