03-04-2004 09:24
As I teach a scripting class weekly and invite and get a lot of questions from new residents, I'm inclined to take the initiative to point out some bugs which most of us are quite familiar with to the point that we've gotten apathy about asking they be fixed.

One such bug is the llTargetOmega() rotation bug which resets the rotation every time the object is updated from the server.

I'm just curious if any effort has been spent to look into how difficult it would be to fix this very minor bug.

I've done programming for some time, so I'd like to assume I have some insight into the relative difficulty of problem solving certian bugs, so I hope I'm not being presumptious when I say that this seems like a simple problem to fix.

The simplest kludge would seem to be that upon recieving an object update from the server on an object that has an llTargetOmega() applied to it, that the current rotation not be overwritten, or that it's current value be stored in a temporary variable and then restored after the object is updated (and before the display is refreshed).

I know of at least one impressive build that's in progress which is being hampered by this bug, and so I'd like to ask for support for anyone else who has been hampered by this bug to report it, as I think many of us have just grown too used to it to to even consider it a bug anymore.

It seems that bugs are handled in a priority sorted by number of reports from residents, so I'd like to ask anyone who encoutners this bug to break the apathy barrier and just send in a quick little bug report about this issue.

I'm posting this because one particular new user seemed particularly heartbroken when his otherwise perfect build was being ruined by this glitch. He couldn't use the standard rotation because it would have been too visually jarring with the stepping motion with the type of build.

Thank you for reading, and I appreciate your feedback and support.

-- Kex =D