GetIsNight

Didnt see it anywhere.. so here goes

On the object that will rez the light object
______________________________________

//By Artemis Tesla
//With math help from Kanker Greenacre

integer iNightBegin;

default
{
    state_entry()
    {
        iNightBegin = TRUE;
    
        llSetTimerEvent(10);
    }

    timer()
    {
        vector vSunDir = llGetSunDirection();
        
        float fElevAngle = llAsin(vSunDir.z);
        fElevAngle = fElevAngle * RAD_TO_DEG;
        
        //If Night and begining of night
        if ((fElevAngle <= -10.0) && (iNightBegin))
        {
            llRezObject("light",<  PLACE POSITION  VECTOR HERE >,<0,0,0>,<0,0,0,0>,0);
            iNightBegin = FALSE;
        }
        if ((fElevAngle >= -10.0) && (!iNightBegin))
        {
            llSay( CHANNEL HERE,"LIGHTS OFF");
            iNightBegin = TRUE;
        }       
    }
}

on the light object
______________________________________

//By Artemise Tesla

default
{
    state_entry()
    {
        llListen(REZZING OBJECT CHANNEL HERE,"REZZING OBJECT NAME HERE", "REZZING OBJECT KEY HERE","LIGHTS OFF");
    }

    listen(integer channel, string name, key id, string message)
    {
        llDie();
    }
}

And thats it...

If you see any tweaks please let me know..

Artemis Tesla

Hm I just wonder because I always thought you could tell night much simpler. I thought if the z component of the llGetSunDirection() vector was negative then it was night, if it was positive it was day?

Does this measure some absolute sun direction? How is it affected by "Mouse Moves Sun" or "Force Sunset"?

As far as I can tell, Force Sunset and Mouse Moves Sun are clientside effects so that Joe User can play around with object lighting - the scripts would be reporting the official sun position as calculated on the sim, if my guess is right.

Maybe needs testing.

Yup, Force Sunset is client side and does not influence script execution.

You may want to turn the lights on a little early, as in vSun.z < 0.1 = turn lights on, vSun.z > 0.1 = turn them off.

Now combine this with an IS_ON, either clickable for regular lamps, or activated for vehicles, and we're in business.

All we need now, is to stop paying ridiculous energybills when the lights are not even on. llSetMaterial()...?

My guess is it reports the sun direction from the owner. The client needs to know the sun direction anyway because the client needs to calculate light etc...

Darwin, scripts don't run on the client, they run on the server, which is not informed if you misplace your local sun :)

This is what I've been using:

default
{
    state_entry()
    {
    }

    touch_start(integer total_number)
    {
        vector v = llGetSunDirection();
        float z = v.z;
        if(z >0){
            llSay(0,"It is day-time");
        }else{
            llSay(0,"It is night-time");
        }
    }
}