Listeners or Timers - Lowest Lag solution for Multiple Object rotation?

Hello to Everyone

This is my first post to the Forums, and I hope someone can help me out:

I'm modding a wind farm to rotate the turbine heads into the wind, and I have 2 ways of doing it, but wanted to get your thoughts on the lowest lag implementation:


Option 1: A timer script in each turbine head, that checks the wind direction every x seconds (say 60 seconds) and adjusts the rotation if it has changed since the last check (e.g. was NW now E)

Option 2: Have a central controller monitoring the wind on the timer, and the turbines listen for updates. When there is a change, the controller sends a message (llRegionSay ?) with the new co-ords.

I have the core code for making the rotation changes (plus the code to vary the speed of the rotations based on the wind speed - Thank Nand Nerd for that

There will be between 15 and 20 turbines, and I may also add whichever solution into some flags (to improve the 'flutter' of the flexi-prim).

What would be the better of the 2 options in terms of reduced lag? any thoughts or better options gratefully received

Kind regards,

Geoff

Listening appears to be event driven, so nothing will be processed unless something is said on the channel, so less usage overall. On the other hand, they will all trigger at once with the listen, so you may want your first action on hearing something to be sleep a random period of time ....

I'm assuming here that it works as the documentation seems to indicate, I've never tested for lag.

Great stuff, thanks Jake

Any others with advice welcomed

On a related note - the WindSpeed and Rotation vectors returned are *very* specific (for example, the speed might be 5.207408 somethings (metres per second?)

How would I go about reducing the figure to 2 decimal places?

Also how about reducing it to a single digit (rounded up or down) ?

Many thanks in advance,

Geoff

llRound
llFloor (round always down)
llCeling(round always up)

Make a function to which you pass a float to return a string.

In your function:
Multiply the float by a 100 first to give you two dp places.
Then llRound to give you an integer (i).
Divide (i / 100) and cast to string for lhs of answer
Modulo (i % 100) and cast to string for rhs of answer
Then return lhs + "." + rhs

Probably heaps of better ways.

Edit: sorry did not see need for no dp, so use Osgeld's suggestions.

Thanks peeps

Just whizzed the 101 and 'Crash Course' on the RPGstats WiKi - should have done that earlier!

All makes a lot more sense now - and I have some nice new tricks to simplify the code I wrote

Thanks for the help,

Geoff