Tour Guide Rezzer has FILLED MY PARCEL with vehicles!!!
complete
Cranston Yordstorm
This SEEMS isolated to Magnum and Ferrari servers (as far as I can tell) ... The issue is NOT occurring on Second Life Server regions.
I have a lazy floating tube tour that I have created for numerous clients, as well as having it on my own parcel. On Wednesday morning when my region was restarted, all of a sudden the tour guide rezzer (which rezzes a new version of itself AFTER someone sits on a tube and it floats a certain distance away) has begun spewing out versions of itself every 15 seconds ... ON ITS OWN! Everything was fine BEFORE the latest LL region restarts! WHAT IS GOING ON?!?!
Log In
This post was marked as
complete
Maestro Linden
tracked
Maestro Linden
closed
Maestro Linden
Cranston Yordstorm: we took a look at Emerald City, and the broken rezzers appear to belong to the family of content that was created by John Codesmith. John has pushed out fixes for these items, and you should update your region to the fixed items. Please contact John if you haven't already received the update.
Lessie DreamSeeker
Just leaving our experience here to say that we have experienced the same issue. We do not have access to the scripts involved but exhibit the same behavior. Every 5-15 seconds a copy of the object is rezzed that would have otherwise not been rezzed. This continues until either the parcel is full, the region is full, or the region hits 45000 scripts in use rendering the location inoperable.
We've noted the following objects exhibiting this behavior:
- Horse Carriage Tour Rezzer 3.202.1
- Cuddle Cloud Tour Rezzer 3.3
- Relaxed Couples Ice Skaters 2.3
- Relaxed Singles Skater 2.3
The first location was reported on August 7th:
Second Life RC LeTigre 2024-07-22.10048683488
The second location was reported on August 10th:
Second Life RC BlueSteel 2024-07-22.10048683488
As a temporary measure these items had to be returned to their owners to return their locations to an operational state.
Maestro Linden
Lessie DreamSeeker: Thanks for those details. Those objects seem to be the ones sold in this marketplace store: https://marketplace.secondlife.com/en-US/stores/254
The SL Support team was contacted about a few of that store's rezzers running amok late last week. We confirmed that there's a bug around the handling of llSensorRepeat() in those scripts (see my other comment for details), and have been in communication with the script creator regarding the issue. The creator (John Codesmith) indicated that he has fixed the bug on their end and has been rolling out updates over the weekend. I recommend that you update your rezzer objects as they become available - it should fix this bug.
Lessie DreamSeeker
Maestro Linden I appreciate the updates! I will inform the tenants to keep an eye out for any updates on those particular items.
Cranston Yordstorm
unfortunately ... I am not a scripter and the person who created the script pretty much disappeared about the time of the issue happening. I definitely remain convinced that the midweek LL restarts facilitated whatever is happening because before then things were fine and things went south within less than an hour afterwards (takes time for all those vehicles to rezz themselves.
Maestro Linden
needs info
Maestro Linden
Cranston Yordstorm can you please post the source code of the rezzer script, or (if you don't have modify permission) ask the creator to do so?
We saw a report of a different rezzer script misbehaving in 2024-07-22.10048683488. In that case, the rezzer script was doing the following:
- Running llSensorRepeat("object", NULL_KEY, -1, 20.0, PI, 10)
- In the no_sensor()event,llRezObject("object", ...)
The scripter's idea was that if the script couldn't find a copy of the object it was rezzing nearby, it would rez another copy of the object. The problem is that the https://wiki.secondlife.com/wiki/LlSensorRepeat
type
parameter was set to -1, which enables _all possible_ flags for that bitmask, including the new DAMAGEABLE
flag found in 2024-07-22.10048683488. The DAMAGEABLE
flag is defined as:"Filter for objects in world that have a script with on_damage or a final_damage event (able to process damage)"
Since the object the sensor was looking for was not damageable, the
no_sensor()
event would trigger on every scan, causing the rezzer to rez objects constantly. The same script is also filtering on as-of-yet undefined type
flags, so it would potentially break from those in the future - the proper fix is for the script to only specify the type
flags that are defined, rather than setting all possible flags.Cranston Yordstorm
Here's a video (gyazo) of exactly what is happening.
Cranston Yordstorm
The specific regions affected are called The Emerald City (Magnum) and Ivory Isle (Ferrari)
Load More
→