I made the mistake of uploading AM V.13alpha and had problems right off the bat. One problem was the inexplicable error message that popped up informing me that the light file c1-ico-f2(20) was an invalid light file. After I deleted V.13, and reinstalled V.12, the message persisted. On a whim, I tried a couple of the other light files, and they worked fine.

Any ideas why c1-ico-f2(20) is acting up? And yes, I did delete all the skylight files and installed them again clean, but still the error pops up.

I looked around the light rig files and found different variables set for the different rigs. Things like this boolean>
[ACTIONOBJECTSCONTAINER]
Modified=10/30/2000 8:54:22PM
Expanded=TRUE
were in the 52 light rig but not the 20 light rig under action objects container, but was found in different locations inside the file. However, files like the 337 light rig never contained that boolean at all. Mind boggeling! It seems my observations have turned up more questions for Yves when he get's to this thread.

v13 changes the file format. When you save a v12 (or any previous version) project file in v13, it warns you if any linked file (object, light, action, material, etc) comes from a different A:M version and asks that you, the user, take the explicit decision to save the files with the "save As..." command.

If you save a file in v13 format, you won't be able to load it in previous versions of A:M afterward.

Concerning the "expanded" flag, it is only related to how the folder is displayed in the PWS. It does not affect the operations.