Dear Unity Developers, I tried to update my LightSettingManager Asset for Unity5 and realized that I have to cut down the feature list back to the level of Unity3 due to the deprecated lockAtlas function and the missing LightProbes.asset file. As discussed in some other treads (here and here) there are some people who need those functions to support dynamic lightmap changes in a scene for baked GI only (e.g. on mobile devices). LightProbes.asset File This file made it possible to load the precomputed light information of lightprobes at runtime in Unity4. As it is not available now; replaced with an - "editor stuff only" - file (LightmapSnapshot.asset) which no one can use for loading or saving lighting data. This makes really no sense to me. If the light probe data is included in that file, please insert an option to export it to the old Unity4 format (LightProbes.asset) or create a function to load the LightmapSnapshot at runtime. Even the documentation is still talking about the file LightProbes.asset file. LightmapEditorSettings.LockAtlas The LightmapEditorSettings.lockAtlas function was very useful to manipulate static object (scaling has an impact on the atlas) when changing lightmaps at runtime (as all prerenderd lightmaps used the same atlas). Now there is no way of achieving this, because every lightmap get a new atlas which can't be changed or loaded at runtime. As Unity Technology member Kuba asked ("Are there any use cases that the above doesn't cover?") in here, I hope to have successful shown a usecase Unity developers didn't had in mind. Hoping on positive replies from Unity developers! Thank you and best regards.