OAR making weirdness
Posted: Fri Jul 11, 2014 9:52 pm
I have a problem with a world I'm managing. We have a number of contractors etc building stuff for us, with the expectation of transferring ownership of their builds. We thought that taking OAR files would be a reasonable form of backup.
However, the report shows hundreds of objects that were not included because of "insufficient" perms. The builders insist that every single prim and texture has full next owner perms.
So, I went in as the world manager, took copies of some of the problem objects (I have edit rights on their stuff). The copies arrived in my inventory full perm. I rezzed them in world, and they rezzed full perms. I took them back and they were still full perms. I rezzed them out and took an OAR of the region. They appeared in the OAR file no problems.
What gives? What other perm is required for an object to make it into an OAR file? And how is it that taking a copy of a problem object fixed the problem (mysteriously granted the extra perm)?
It's going to take me a lot of time to fix hundreds of problem objects. To fix means (1) take a copy (2) note the exact position and rotation (3) delete it (4) rez my own copy, an (5) set the exact position and rotation to what the problem object had. That's a crapload of work for objects that should already be in the OAR file but are being rejected for unknown reasons.
I'd appreciate any help, as I'm frustrated, and the builders are offended that they're being accused by the system of not properly granting perms that they already have granted.
However, the report shows hundreds of objects that were not included because of "insufficient" perms. The builders insist that every single prim and texture has full next owner perms.
So, I went in as the world manager, took copies of some of the problem objects (I have edit rights on their stuff). The copies arrived in my inventory full perm. I rezzed them in world, and they rezzed full perms. I took them back and they were still full perms. I rezzed them out and took an OAR of the region. They appeared in the OAR file no problems.
What gives? What other perm is required for an object to make it into an OAR file? And how is it that taking a copy of a problem object fixed the problem (mysteriously granted the extra perm)?
It's going to take me a lot of time to fix hundreds of problem objects. To fix means (1) take a copy (2) note the exact position and rotation (3) delete it (4) rez my own copy, an (5) set the exact position and rotation to what the problem object had. That's a crapload of work for objects that should already be in the OAR file but are being rejected for unknown reasons.
I'd appreciate any help, as I'm frustrated, and the builders are offended that they're being accused by the system of not properly granting perms that they already have granted.