llTargetOmega stopped working

One of my tenants tells me that the following script worked fine until the re-start in the last 2 days. It is for a swing that just goes back and forth. It seems pretty straight-forward to me and I can't get it to work either. It seems to just keep going around in one direction rather than swinging back and forth. Is this a new bug in SL? Can one of you experts help me out?


default
{
state_entry()
{
llTargetOmega(<0.0,1.0,0.0>,0.5,1.0);
llSleep(2);
llTargetOmega(<0.0,1.0,0.0>,-0.5,1.0);
llSleep(2);
llResetScript();
}

}


Thanks in advance for your help.

that actually works?

I guess I assumed spinrate was an absolute value.... does it still occur the same if you negate the vector instead of the spinrate?

I am experiencing the same problems...
What I have discovered so far.....

object is not spinning.... Start spin with script.... No visible effect...
Right click and edit object... Make no changes... close edit box... Object is NOW spinning...
Send command to reverse spin... nothing happens.... edit and close edit... spin NOW reverses...


This just started happening after the last upgrade.. I suspect a bug here....

I have a swing script that uses llTargetOmega and the same thing is happening. Only when you do get it swinging by using the put-in-edit trick, it goes full circle in one direction instead of swinging back and forth. :^/

This is an old bug that was fixed for a while but's now back.. Just right-clicking on a stalled llTargetOmega will start it up again.

I submitted a ticket on this. It is Ticket#4051-4448129.

Vote for http://jira.secondlife.com/browse/MISC-684 , too.

The original JIRA is: http://jira.secondlife.com/browse/SVC-54

This only happens on llTargetOmega when it is constantly changing, the work around is to change a prim property, like adding a llSetText with different numbers of blanks before every llTargetOmega.

After each llTargetOmega, do one llSetPos with small enough values, it will do the trick.

I've voted for MISC-684!! and read all of the associated links. Looks like this has been going on for a while off & on.

I've tried the llSetText workaround - problem still exists.

I've also tried the llSetPos workaround - problem still exists.

I guess we have to wait for the Lindens to put a real fix in. Hope it doesn't take too long. Any guesses for a date. AHHHH SORRY, that would be gambling

Last but not least, I'd like to thank everyone for you attempts at helping me!!!!!

Same thing here. Broke my products.

I find it ironic this is being looked at as a "Normal" request when it impairs quite a bit in SL.

Tracy

I think it's more than that - I've seen it on things that just had a simple rotation script applied, were working fine then stopped working.

To the above,

You are correct. I have just a rotator on light for a lighthouse, that won't spin either. Nor will my ceiling fans with llTargetOmega.

Borked....as ususal. This is why people leave SL. Works, then borked. People who buy the products don't understand, they just want it working. So, you have a choice, refund their money or not. I do in these cases to keep the peace. But honestly, this is why people leave, we are honest and give them the money back being it doesn't work. Now if Linden would do the same.


--Tracy

Oooh, I didn't notice this myself yet, but it's pretty serious. Many items rely on TargetOmega. Hope this gets fixed very soon.

Is the llTargetOmega problem *just* on the Havok4 beta regions? If so, this is a known isuse that is being worked on.

Or, is the issue also on the regions running Second Life Server 1.19.0? (Look at Help:About Second Life to find out the version your current region is running.) If so, has anybody submitted a JIRA about this issue since the 1.19.0 deploy?

I saw it this weekend on the mainland so it's not Havok4.. Dunno about the server version, though - I can check tonight unless somebody is bored and takes a run over to Digeut for me.

RC viewer - not Windlight, if that matters.

It is broken on the normal SIMS!!!!!

Second Life Server 1.19.0.79136

I submitted a Support Ticket on Saturday as per my post above (Ticket#4051-4448129)

It happens in Qinglong and in Oblayus on both the normal viewer and the WindLite viewer.

Second Life Server 1.19.0.79136

That is the server running at the location I'm having issues with.

--Tracy

I think they borked a lot of things in 1.19 that have no apparent conneciton to announced changes. See also /54/20/239110/1.html

Maybe we can ask that Linden revert the server to what last worked. I noticed the issue recently after the 3, count them 3, server reboots during the rollover. It's certainly a server problem and not with Havok4 on the beta grid. My question is why the server updates / upgrades are not tested prior to implementation? Surely we would notice that a prim won't even spin?

--Tracy

Havok4 is also on the main grid, Tracy. It's limited to private islands, though - no Havok4 sims on the mainland yet.

I'm not sure why this is 'certainly a server problem' but do agree that it's an annoying bug.

I've tested this with my own rocking chair script, and confirm that indeed this seems broken in 1.19.0.

We will look into it.

Ah, okay. I didn't realize they were moving that fast on Havok4 to have it implemented on Island sims. I don't recall reading this taking place at this point but might have missed the blog. At any rate, in two years nothing has been stable enough to work for any length of time. Something is always broke and not working.

Now we have mono, Havok4, Windlight, etc. etc. etc.. being worked on and yet to "Fix known Issues First". If Debian worked this way, there would be no Ubuntu. If Jelsoft worked this way, we wouldn't have a forum to complain on. Point being no matter how you look at it, it's still unstable and not working in a respectable manner. It doesn't take a brain surgeon to make a prim spin and it certainly shouldn't take one to see that it doesn't. When things don't work from one upgrade to the next.. Well... Might be time to move on.

--Tracy

Got a JIRA so we can all head over and harass you with votes, Prospero??

Yes, just noticed all my holovendors aren't spinning the items anymore :\ meh...