Broken by update: PDS HomeSecurity Orb & PersonalSecurity HUD

Currently two of my main products "HomeSecurity Orb" & "PersonalSecurity HUD" are broken by the SL update. A hacked fix has been put out for the HUD but this might not fix all the problems. It's recommended that you do nothing at this stage and we wait and see what the fix is from the Lindens.

The problem seems to be related to teleports, changing sims and other causes for sensors.

There is conflicting reports on how to solve these issues (with llSensorRepeat()).
Joe Linden in IRC has said the fix will be put in "tonight" but reportedly Adam Linden has said that scripts using sensors need reseting.

** DO NOT RESET THE HOMESECURITY ORBS SCRIPTS THEY WILL SELF-DELETE **

I am at work currently and will be for many more hours, so I cannot come into SL to fix these issues. I am hoping that tomorrow, my first day off, I can put out fixes for these issues.

For now tho do nothing except send Lindens bug reports.

Quality control; who needs it?

UPDATE: Lindens doing sim restarts to fix llSensor() problems this might fix the llSensorRepeat() problems my products are having.
/3/20/122750/1.html#post1162083

LATEST UPDATE:
Everyone needs to:
1) Log off SL and start SL again
2) Check that the version number on the lower right says 1.11.0(11) or higher
3) if it doesn't you will get a prompt
4) You MUST choose DOWNLOAD
5) Then login again

6a) If you have a v3.00 to v3.31 PS HUD send it to me for a swap even if I am offline and send me an IM.
6b) Update the HomeSecurity Orb to v8.007

Deleted

Why do you make a product that self-deletes when anyone tries to reset it back to its default state?

thats a good question!!!

The Orbs cant be simply replaced with another one because for security reasons each one is identified by a portion of its UUID called a HSID. The HSID would change when u replaced the Orb to the new version. Then everyone would have to reconfigure the networking each time they got an update plus they would obviously loose all the settings and names.

This was all solved by using Update Disks.. since anyone at any time can get an Update Disk from my servers this means they can always get copies of the new scripts endlessly and potentially make free Orbs to use for free and re-sell.

The only way that SL has to stop getting endless copies of scripts free is to have the update disks send over the new scripts to the Orbs using llRemoteLoadScriptPin() then using the start_param as a secret "PIN" number which allows the move to happen. Then when the new script starts up it checks the "PIN" number used was valid. If the number is not valid the script asumes it has been moved manually for nefarious purposes and so deletes because it may have been stolen.

So lets say the valid start_param was 89 when the script starts the script checks the start_param it was started with was 89... if it was then it keeps running happily.

The problem occurs when u reset a script the start_param "PIN" number then becomes zero which is also what the "PIN" number would be if someone steals the script from the update disk to make free Orbs for use or re-selling.

There is no way in a script to tell the difference between stealing scripts from an Update Disk or a reset of the script itself.

So we have a choice: no update disks and re-set up networks, names and settings every update or never being able to reset the scripts. The later is marginally better.

Yes the scripting language sucks for sophisticated purposes.

So why not simply make the scripts all no transfer?

no transfer would mean the scripts could never be deeded to groups which is needed if u want to use unsit, land eject and TP on group owned land. It also allows a person to make endless copies. Also I am unsure if no transfer would allow the update disk to send scripts to another object, it certainly wouldnt for a Group owned Orb.

Lindens doing sim restarts to fix llSensor() problems this might fix the llSensorRepeat() problems my products are having.
/3/20/122750/1.html#post1162083/3/20/122750/1.html#post1162083

GL psyke, were counting on ya.

EDIT: i think the problem effects anything using a sensor. I created a AvDetector that spills out everyones name in your area into chat when you touch it. It isn't scripted to do that when you teleport but it's doing it anyway... >.>

It is really strange how it behaves differently from sim to sim.

For instance, I have some sliding doors that use a sensor repeat to open when someone is close. In some sims, they stopped working and I had to reset the script. In other sims, they work just fine.

Yea sensors are going sicko. i script a lot, and know what i'm doing. I built a weapon detector that was working fine before this patch, now it's flooding chat, and yelling at people for rezzing default cubes. o.o

LATEST UPDATE:
Everyone needs to:
1) Log off SL and start SL again
2) Check that the version number on the lower right says 1.11.0(11) or higher
3) if it doesn't you will get a prompt
4) You MUST choose DOWNLOAD
5) Then login again

6a) If you have a v3.00 to v3.31 PS HUD send it to me for a swap even if I am offline and send me an IM.
6b) Update the HomeSecurity Orb to v8.007

1.11.0(9) made llSensor() re-trigger after region changes, even sim crossings.

1.11.0(11) was supposed to fix this, but it overdoes it - sensors stop triggering at all after a region change.

I fixed this in Otter Monitor and I'm going to make another post with more details in its own thread. If you're using Otter Monitor, you can get an update in my stores (check my picks) or from any of your friends who have already updated it since it's freely redistributable.

the new PS hud seems to work fine. Is there a update for the HS orb yet? i'm running version 8.006 right now. i updated (probably foolishly) after the patch to 1.11. Also thx!

Click Update and get 8.007

Psyke.. I love when you talk techie and all... but could you please print an English version of all that.. TY Kisses Pet

Which part are u refering to and if u love it then what incentive do I have to stop?
And when did I submit??

Actually, you can deed a no transfer object to group. You just have to be careful when you do a return, because then it gets deleted.
As for endless copies, you can make the main object itself no-copy, and the scripts inside no-transfer. Try it. It works.
And as for updating, if you are the owner, simply buy it back to yourself, update, and then redeed to group.

Oh, and yes, no transfer does allow you to send scripts to another object, as long as you are the owner of both objects.

I will look into this.. ty