Justin,

Thanks for the clarification. I hoped it worked like you have stated, but previous answers said every asset was assigned a new UUID because it would be possible to duplicate UUID's between different servers.

This makes me wonder if with the current problem of OSgrid if they had simply brought up a new empty asset server and requested everyone upload any IAR's they had old, new whatever that it would go a long way in repopulating the lost data. I assume that if I have an asset in my inventory and say several hundred other users have the same item that if I replaced it, it would be there for everyone. I suspect your inventory itself is a record on the asset server so I guess if that record is lost then you basically have no inventory even if everything you previously had was on the asset server. It appears to be a no win situation. I am very fortunate because I have an IAR of my inventory made just hours before the grid went offline. My understanding of your statement is that it will not do any harm for me to upload my IAR back to OSgrid when it comes back as it will not add more data that may already be present.

I still do not understand why when I upload the same IAR to my standalone it duplicates everything in my inventory with another identical entry for the same item. If it finds the same item already in inventory and the asset server why does it make a redundant inventory entry? Since it is the same asset being loaded twice it has to be identical since the IAR is the same IAR. If I upload the same IAR 5 times I end up with five of everything in my inventory. As a test I uploaded my 12,000 item inventory five times and my inventory ended up being 60,000 objects in inventory.

Yes, I always use the -merge option.

Tom


-----Original Message----- From: Justin Clark-Casey
Sent: Wednesday, September 17, 2014 6:59 PM
To: [email protected]
Subject: Re: [Opensim-users] IAR Import question

This isn't correct. Currently, if an OAR or IAR is loaded and it references asset IDs which already exist, then these
will be used and assets will not be loaded again.

On 15/09/14 04:32, Thomas Ringate wrote:
That makes sense. That means each time you import an IAR you are adding more items to your asset database. I assume once an object is in the database it is there forever. Deleting it from you inventory does not remove it from the asset database only from my inventory I understand. On a private standalone it sounds like it would be a good idea to drop you database and start over rather then keep loading IARs of your inventory from OSgrid. It is a pain to delete the duplicates in inventory but the simple way I was using was to delete everything in inventory
and then load the new IAR.
That make it appear like I don’t have much but in fact I guess every time I do that my asset database grows in size by
some 12,000 items.
Tom
*From:* M.E. Verhagen <mailto:[email protected]>
*Sent:* Sunday, September 14, 2014 6:27 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [Opensim-users] IAR Import question
iar import will create new assets with new uuid's
since uuid's will need to be unique it is not possible to reuse uuid's cause different grid could give objects the same
uuid.

------------------------------------------------------------------------------------------------------------------------
_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users


_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users



--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users

Reply via email to