If there are numerous avatars sitting on a vehicle, lag and sim crossings will often cause one or more of them to lose connection with the vehicle- sometimes with second life totally. When this occurs, it will leave a 'ghost' that may or may not disappear. This ghost setting actually stays as part of the prim's settings, and I can find no way to clear it. To see what I mean.... Take a generic physical vehicle. (My friend used the scripts/sounds from the Hot Dog, a giant flying hot dog freebie. It goes all into one prim, and is commonly used.) Add the script included into four or five poseballs and attach them to the vehicle. Set up a computer with multiple copies of sl- three, four, five... however many it takes so that the avatars can move (with patience) but not handle a lot of input. Seat them all on the poseballs. Sit on the flight poseball yourself (you are on a separate system!) and now fly the vehicle through several sims, across sim boundaries. Push it a bit, and before long you will lose one or more of the multiple copies. They 'ghost'. Now, the poseball which has lost the ghost will report that it is having problems whenever a link change event occurs. It will give the key of the person who left and try to reset itself. (The reset fails.) It will also give you the key of the person in question when you touch it. If that person returns, it is possible that they will teleport directly onto the poseball and replace their ghost. But if not, and they are nearby, they will get requests to animate their avatar whenever the script runs the link change event handler (among other things, every time someone gets on or off the vehicle.) The script illustrates that llAvatarOnSitTarget is still returning the ghosted key. The llSensor event, however, does NOT find the person. The no_sensor event tries to fix it by using llUnSit (without success) and by resetting the script totally (again, without success). I have also tried clearing and changing the sit target using llSitTarget. No success. You can unlink the poseball from the vehicle, and it will still have the key recorded in it (somewhere!) You can link it to another vehicle or object. It is still there. Taking the poseball into inventory and re-rezzing it (either by itself or as part of the vehicle) will fix the problem- the incorrect setting will be gone. Is there any other way to fix this problem besides taking the offending object into inventory? (Note- as of this writing, I have three poseballs in this state at the location mentioned above. I unlinked them from the vehicles.)