BUG? Lightmap assignments cumulative -- How are lightmaps associated with scenes?

Hi,

We have a major memory issue in our live app, and it appears that lightmaps are part of the problem.

We’ve got multiple scenes - these were all created with Save As, one from the next.

When saving, we’d delete all geometry (which is lightmapped) from the scene, add new geometry, bake new lightmaps.

Going through profiler memory snapshots, I can see that each successive scene appears to be loading the lightmaps from the previous scenes – ALL of them, including lightmaps from an early test scene which isn’t even in the game.

So while each scene#s final draft should have 4 Directional Lightmaps (i.e. 8 total), the third created scene has 22 lightmaps in memory. (!).

Can someone explain if this is known or expected before I go out of my way to file a bug report, as we really need to nail this so we can update our app.

Thanks

Resolved!

It appears we changed a loader scene to LoadLevelAdditive to get around an unrelated issue, and the loader scene itself was made from a scene that had once had lightmapped data inside - no idea why, but they’d the geometry but forgotten to click Clear Lightmaps (so the connection to the lightmaps still existed).

May this lesson help others.