Scripts going inactive at SIM boundary?

I've noticed somthing odd that didnt seem to be happening about a week ago. I have noticed that the in the overlapping region of sims that running scripts just go inactive in an object.

Example:
Sphere object, script set to go into an 200 second loop activated by a touch, in the loop you stick a "say" command with the loop counter (So you can watch the scripts activity). Start the loop and slide the object into the sim overlapping region... loop stops spitting out Say's... slide the object back into one of the sims... the loop continues as if nothing happened.

Has anyone else experienced this? I tried it at multiple sim boundaries with the same results.

Thanks,
-Phid

Is the land you move it into No Script or does it happen everywhere?

Nope Scripts work on both sides of the boundary, just not on it.

If an object is manually slide across the scripts work just fine on the other side as well. I will be experimenting with other boundaries than the two I already tested a little today to understand this better.

This wasnt the case about a week or so ago (dont know the exact time I noticed the change. I had a pet object follow me just fine through multiple sims a while back but now it goes into a coma at the boandary and needs a manual slide to get it across the sim. I thought it had somthing to do with the coordinate system but after some basic testing it seems all scripts just "freeze" until the object is out of that specific slice of the region.

-Phid

**Update**
Doesnt seem to be every boundary, but there is at least one that is doing it. (Not sure how many more, I'll post that location here in case any Lindens want to check it out)

**Update**
The specific boundary I have observed this is Periwinkle/Hikuelo.

**Last Update**
Yep... upon turning on the "property line" options I see there is a sliver of "goverment" land with scripting turned off at that location, It just happened to be at the sim boundary. Mystery solved.. the other observations were nothing more than a sensor glitch that resembled this area where scripting was disabled.