guycalledfrank
commented
3 years ago Hmm do you mean you want it to automatically check/uncheck the "export scene" checkbox based on changes (or lack thereof)? This is possible. I'll take a look.
Moving a light or a camera shouldn't trigger the "scene changed" flag. What does is:
-
From your pic: simply a different scene was baked last time. Scene geometry data is exported to the temp folder, and the files are overwritten every time. So as soon as you bake another scene, cached scene geometry is replaced. It is possible to have uniquely named geometry caches for every scene, but not sure if it's worth it, it could bloat the temp folder's size even further. You can also just set a different Temp Path for each scene, then the cache is not shared, and it'll work (costing you some more disk space).
-
Any change to atlasing which is computed during scene export. If some objects were packed differently (point to different lightmaps or different location inside the lightmap atlas), it will detect it as scene change. Packing is different if scene geometry actually changed or any packing parameters were changed (e.g. texels per unit).
-
There is a bug in the Asset Store version of v1.71 where it says that atlasing did change even if it didn't. Github version has it fixed.
laurentopia
scene export takes up a lot of time so I have export off by default but it doesn't work automatically.
also what is the mechanism that Bakery uses to detect that its internal data doesn't match the scene? it looks like even a simple change like moving a light or a camera causes a mismatch (and it shouldn't since neither are geometry data)