LL: Please fix the 'random return' soon? My build is decaying...

Didn't re-rez the objects that were returned from the 'random return' bug last night, and now, a set of NEW objects were 'random returned', eating further into my build.

This is getting pretty serious, guys. I currently have 61 prims available on my land, and things are still being returned. I have a feeling if I wasn't constantly replacing objects, everything on my land would be returned.

Same. My house in Natoma is slowly being eaten away. Yesterday it was just some of the upstairs stuff and a piece or two of wall. Now the entire internal second floor is gone, along with most of the furniture and several pieces of the outside structure and roof.

I'm very, very curious as to what will be done to restore the builds, and/or otherwise help us deal with the pain of having to dig out all these objects and put them back. Aligning textures on walls and so forth is tedious and annoying work and I am not relishing doing it again because of this bug at all. No offense guys but your patches are killing the prolific builders and scripters...using my online time to fix this stuff is no fun at all.

I'd seek a response from bug reporting...but the response I got had no text from LL at all, just that confusing "respond here but not here" stuff.

It's strange, I'm having more and more stuff that was placed in 1.0 returned... alongside stuff that was placed in 1.2. It actually seems to stagger; a 1.2 object, a 1.0 object.. a 1.2 object, another 1.0 object...

Strange, strange logic in this one. Not only is it returning things when I have an -increasing- prim allocation (i've been trying to cut corners and clean up to 'satiate' the bug, but it doesnt seem to work) - the order in which it returns things is messed up, too.

So, tcoz, it looks like this is going to be a continual decay until the next patch, because the bug doesn't seem to even have a 'false' limit... Or perhaps internally our object limits are set at 0... if that's the case, though, then how come everything wasn't returned at once?

Either way, it seems that if let to run its course, we'll end up with nothing on our land. I have half a mind to let that happen, just to kind of say, "see, *everything* on my land has been returned"...

But then on the other hand, maybe they have it figured out. If they do though, I don't know why they haven't released a 1.3.5 to fix it - as it's a rather serious bug, im my (And your, I presume) opinion.

The patch to make sure men don't sit like girls happened quicker than this -- but maybe they're still trying to figure out exactly what's going on. It could have something to do with arrays going out of bounds, values wrapping around, who knows.

Maybe after this is fixed, (when and if? ) - the Lindens can explain what happened... It's a bit worrisome since it doesn't seem to be effecting very many people... i've only talked to four or five folks in world who have had the problem, but the symptoms are always the same, and definitely since 1.3.4... Intermittent 'sometimes it happens, sometimes it doesnt' bugs are always harder to eradicate than ones that happen universally and are easy to replicate.

Here's hoping for a new download soon.

Well, hm.

/3/6d/12784/1.html


... Maybe there's more complex buggyiness than first expected.

Bits and pieces, huh? My WHOLE build is gone including the landscape. 2700+ prims just popped into my inventory. Oh wait, you guys have a bug. I uh, kinda took mine down myself.