Recently a fix for updating of our inventory in ADITI (preview/beta) grid rolled out. Some people are working with it now. I started writing about the changes being made this last December in: Second Life’s ADITI Inventory Update Change.
Today is the first time I’ve logged into Aditi since the change rolled out. So, my inventory has yet to update. I am hoping for a Friday morning update.
Basically, inventory updating was a process of replacing the Aditi preview grid inventory with a copy of your Agni main grid inventory. That had problems. But, we had some control over it. Change your Second Life™ password and the system updated your Aditi inventory by wiping out all you Aditi inventory and replacing it with a copy of your inventory from Agni. Anything originally created in Aditi was lost.
The change is from a replacement process to a synchronization process. Now the day after you log into Aditi the system will synchronize Aditi with Agni, I understand about 6 AM PDT/SLT. This is a one way sync, Agni to Aditi. Nothing you create or change in Aditi will affect or appear in your Agni inventory.
Sounds good. But, we are running into some problems. I’ll use a hair-do as an example. Pretend I have one called ‘My CFM Blond’ and I set the color to blond. Aditi updates and I have that a copy of that blond hair in my Aditi inventory. I put the hair on and it is blond, just as I would expect. While in Aditi I change the color to red.
I go back to Agni and the hair is still blond, as I expect. Tomorrow the Aditi inventory is re-sync’d. I go back to Aditi after the sync and what color do you think the hair is? Blond or red? I am expecting red. But, what I find is it is now blond. But, the sync process is not supposed to overwrite things done on the Aditi grid… or so we thought. Seems things are bit more complex than expected.
But, it seems anything that doesn’t get a new inventory UUID is assumed to be the item in Agni and apparently a new Agni inventory copy is written over the Aditi inventory entry at the next sync and that ends up pointing at the Agni asset.
I think that would change the Agni asset… but I am told not. I’ll have to test once I have some sync’d shared items.
The problem is only in shared assets, the Agni item copied to Aditi. An item copied from Agni has an Agni inventory item and asset ID (UUID). The assets for Aditi and Agni are in the same assets database, if I remember correctly. It is only the Aditi and Agni inventory lists that are different.
So, any change of a shared asset that does not get a new inventory ID number when changed will be undone on the next sync.
So, if I want the hair to stay red, I have to rez it and then take it. If it is No-Copy, I’m screwed.
I am NOT at all confident I understand the current process. I’ll get to test the process… some time. Then I’ll have a better idea of what is and isn’t working.
Your take away should be to be careful with your Aditi changes of items coming over from the main grid.
Slow Inventory Loading
Also, there are instances of inventory taking hours to download. Also, items created on the Aditi grid one day may not be in inventory the next, after a sync run. You can however clear cache and they come back. But, then you’re waiting hours for inventory to reload.
Also logging in, attempting to log in, using Last Location in Aditi is horribly slow for some people, actually a lot of people and me included. It takes me 5 to 8 minutes from password until the progress bar disappears. Some have figured out that they need to type in the region name then log in, which is then about the same time as for Agni login.
Using the region name my log into Aditi takes about a minute.