The SetHoverHeight function was designed to make the avatar float without flying. The wiki page's own example script is described this way. Now, this function is broken because it is erroneously making the avatar fly, and no longer just standing still in the sky like it was before. https://wiki.secondlife.com/wiki/LlSetHoverHeight The reason for this error may have been the pressure the team faced with a bug that was occurring for everyone in Second Life. It seems that the fix was made provisionally, because now SetHoverHeight has been replaced by fly. In other words, now SetHoverHeight is no longer floating without flying, it has been changed to literally fly, even activating the AO animation. Below is the link to the previous error: https://feedback.secondlife.com/scripting-bugs/p/inconsistent-behavior-of-llgroundrepel-across-region-crossings-compared-to-llset _______________________________________________________ One comment: The consequences of this problem will be discovered over time, but I can already mention some that are affecting me, and are probably affecting other people, who are probably confused, since the problem is difficult to understand (I was just lucky enough to catch AO being activated while my equipment was breaking): 1- Equipment that uses the llSetHoverHeight language is not AO equipment. The llSetHoverHeight script is inside an object attached to the avatar, and has its own rules about activating or not animations (written inside it). Keeping this error would be like forcing a link between the object that has llSetHoverHeight and AO. Imagine how many people have designed products with their own animations for llSetHoverHeight, and now they will have a conflict with AO. So now they will have to create bizarre rules like: "please, deactivate your AO while using this HOVER equipment". 2- It's not just an animation, because Second Life also computes that your avatar is flying. You can even get banned from a land where flying is prohibited, since you can override the browser before you see that you can't do it. It happened to me, because I was testing the bug, and forgot to disable hover when I went to an unknown land. I got an automatic eject as if I was flying, when in fact I was just suspended in the air and forgot to turn it off. Second Life people are not friendly to clarifications, I would probably turn into a troll or something similar at the first suggestion to solve a problem (laughs).
