llRezObject silent failure

Other than the rez location being too far away, are there any other conditions where this function will fail? I have llOwnerSays around it, and they both fire, but no object gets rezzed. I tried resetting the script, copying the script and object into a new rezzer prim - no difference. It was working yesterday, so I know the rez distance isn't too far away, and I moved the rezzer so it's only ~ 2m from the rez location.

Any ideas?

Could the land be over it's prim budget?

I've found that there is a several second delay between removing an item and the land allowing rezing again.

Hadn't thought about that. It's a pretty new sim that's still being built up, so it shouldn't be. And I can drag the object out of the rezzer manually, and that gets rezzed just fine. So that should rule out the prim limit issue, right?

And the rezzer is on a 2 minute cycle. I sat through 2 of those before I had to leave for work this morning. I got the llOwnerSays, both the one before the rez call and the one after the rez call, but no object rezzed.

Also try implementing the object_rez function to confirm that your object actually rezzes something:

// From the wiki..not mine :)
object_rez(key id) {
        llSay(0, "I made a bubu and its key is " + (string)id);
    }

Also, does the object you're rezzing have a script in it? Maybe the rezzer succeeds and the rezed object is deleting itself.

Does the land have autoreturn enabled? Also check other land options...maybe someone changed something like the create objects option.

Also, just try to rez a single-prim item using your rezzer - maybe rezzing a linked set at 2m away makes the whole set too far away to rez.

-2fast

Good suggestions, I'll try the object_rez event. I'm sceptical about the rest. Like I said, same object, same rezzer, same locations, was working last night. Yes, the rezzed object has scripts in it, and when I rezzed the object by hand, the script ran correctly. The script does have an llDie at the end though... but how could it be in a different part of its execution cycle if rezzed by llRezObject vs. dragged out of inventory by hand? Auto return... I checked the group.

I'll try the single prim idea and the object_rez handler tonight.

And try hardcoding the position once "llGetPos() + <0,0,2>" just to test for that. Worth a shot.

The position is an absolute vector now, but yes, I can try making it relative to the rezzer's position. The rezzed object is a train, so eventually it needs to rez on the track Oh, and I'm actually using llRezAtRoot, but the issues should be the same, right.

Did the perms of the object change? Distance and Perms are what usually get me.

Another thing I will check tonight, but I don't think so. The only perms issue I know of is if it's no-copy, and then it rezzes one copy and loses it from its inventory. The object was there in the rezzer's inventory this morning, it just wasn't getting rezzed.

Never mind, the rez distance was too great. And I have no idea how. The rezzer was working for days, and I don't remember moving it. The guys I was working with don't remember moving it either. And I don't remember changing the rez coordinates in the script. *shrug* Anyway, I'm relieved that there's no weird glitch here. Someone obviously did something they don't remember

Trying to rez something over prim budget fails, but not silently, I've found - you get a message from the rezzer.