Hi @lars,
On paper it is a great idea and very ambitious one; I was not aware that Editing Snapshots means being able to access all the data I we have chosen NOT to save with the original Snapshot. Now I see why even with Sun positions only, the giant bloat happens.
It would be great to have the flexible Edit if this was not happening, but with this implemented as-is, given the user unlimited flexibility to edit snapshots and access data they didn’t initially save, makes this approach impossible to work with on larger files, which are pretty much 100% of our projects. I’d rather see ceding some responsibility to the user - if they want to save ALL info, check all boxes, and then restore selected as needed, but if saved only Sun, Camera, or other non-per-object-based data, Edit should not allow to go back on this decision making, and at the same time bloat the files beyond control…
Maybe adding a sticky checkbox at the bottom to Always store all data could leave both options on the table; for those who want unlimited editing at the cost of bloat, and the responsible ones ( 
) who prefer lighter, faster files?
Something like that:
Hope this makes sense. Thanks for looking into it!
–jarek