Yes some new assets are needed ( local fixed skies are now grid assets, clouds texture, default day cyle, etc )

uglysky robust should load them automatically, at least on some asset service modules.

there is a simple hack to import them to a HG grid, using a osgrid account :p

at osgrid, create a box and a new script:

    key a = "5646d39e-d3d7-6aff-ed71-30fc87d64a92";
    key b = "5646d39e-d3d7-6aff-ed71-30fc87d64a91";
    key c = "01e41537-ff51-2f1f-8ef7-17e4df760bfb";
    key d = "6c83e853-e7f8-cad7-8ee6-5f31c453721c";
    key e = "084e26cd-a900-28e8-08d0-64a9de5c15e2";
    key f = "8a01b97a-cb20-c1ea-ac63-f7ea84ad0090";

    key g ="1dc1368f-e8fe-f02d-a08d-9d9f11c1af6b";

default
{
    state_entry()
    {
        llSay(0, "Script running, but who cares..");
    }
}

    Hope im not missing any.

    wear the box and teleport to your grid. If all goes well the normal HG code will copy those assets to your grid.

    This are public assets, of course.

    (you should thank osgrid for this service also ;) )

( btw that is how i did update osgrid, that is also using a older robust ;) )

you will not have updated opensim library, but that only has 2 day cycles (assets above).

Note that most this uuids are hardcoded on viewers, so those that log at sl with clean cache and then opensim, will have them on viewer cache and viewer will use those (some are not exactly the same). A old problem...

Ubit



Hi, yes that setting is enabled, but i am also getting a message telling me
some setting is missing from the database every time I teleport in. Does
robust for an ugly sky region need to also be from the same code set? At
the moment I have robust running on 0.911. I can update robust, but i lost
your post detailing the changes needed to update from 0.911 Robust to 0.92
so i have been putting that off until release so far.

On Tue, Jun 30, 2020 at 1:00 PM <opensim-users-requ...@opensimulator.org>
wrote:

Send Opensim-users mailing list submissions to
         opensim-users@opensimulator.org

To subscribe or unsubscribe via the World Wide Web, visit
         http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
or, via email, send a message with subject or body 'help' to
         opensim-users-requ...@opensimulator.org

You can reach the person managing the list at
         opensim-users-ow...@opensimulator.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Opensim-users digest..."


Today's Topics:

    1. EEP & Ugley Sky (Sara Payne)
    2. Re: EEP & Ugley Sky (Leal Duarte)
    3. UglySky work branch (Leal Duarte)


----------------------------------------------------------------------

Message: 1
Date: Mon, 29 Jun 2020 15:47:37 +0100
From: Sara Payne <sarapayne...@gmail.com>
To: opensim-users@opensimulator.org
Subject: [Opensim-users] EEP & Ugley Sky
Message-ID:
         <
caovqx5utrxs6zczqtlgh5bmquy2axfu1ew8fuunuhsnq0lz...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Greetings All

Today I have been playing around with a pre-release version of Firestorm
with EEP on an ugleysky branch region of opensimulator (compiled today).

What an amazing start from Ubit on the Opensim side and Beq on the
Firestorm team side for making this viewer work with older Opensim code.

Anyway, i couldn't apply a new environment setting asset to the parcel,
only to myself. Does anyone know if this is still expected behaviour with
UgleySky? I guess I am wondering if I should put it on the OS Mantis or the
Firestorm Jira.

Does anyone know?

Thanks in advance

Sara


------------------------------

Message: 2
Date: Mon, 29 Jun 2020 16:05:51 +0100
From: Leal Duarte <ajldua...@sapo.pt>
To: opensim-users@opensimulator.org
Subject: Re: [Opensim-users] EEP & Ugley Sky
Message-ID: <f14ce406-6d33-dfdc-9102-df074e86c...@sapo.pt>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi

  ??? That is working fine for me. Did you allowed parcel override on the
region ?

Ubit


On 29-Jun-20 15:47, Sara Payne wrote:
Greetings All

Today I have been playing around with a pre-release version of Firestorm
with EEP on an ugleysky branch region of opensimulator (compiled today).

What an amazing start from Ubit on the Opensim side and Beq on the
Firestorm team side for making this viewer work with older Opensim code.

Anyway, i couldn't apply a new environment setting asset to the parcel,
only to myself. Does anyone know if this is still expected behaviour with
UgleySky? I guess I am wondering if I should put it on the OS Mantis or
the
Firestorm Jira.

Does anyone know?

Thanks in advance

Sara
_______________________________________________
Opensim-users mailing list
Opensim-users@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users

------------------------------

Message: 3
Date: Tue, 30 Jun 2020 12:37:31 +0100
From: Leal Duarte <ajldua...@sapo.pt>
To: opensim-users@opensimulator.org, opensim-...@opensimulator.org
Subject: [Opensim-users] UglySky work branch
Message-ID: <b740ff9b-b4d9-a92e-89f2-cb2b439bd...@sapo.pt>
Content-Type: text/plain; charset=utf-8; format=flowed

"uglysky" is a branch of? the OpenSim 0.9.2.0 dev code that should
provide some support for different region environment mechanism that new
viewers for OpenSimulator (OpenSim) will have. This viewers replaced
Windlight by the so called EEP (Environmental Enhancement Project) code,
basically a modified Windlight, with a few new features and different
low level rendering.

Up until uglysky work, the OpenSim environment had two basically
independent environment handling mechanisms: Lightshare (LS) and
Windlight (WL).

Windlight was just a blind storage of what was sent by a viewer to the
server when applying an environment on its UI. This storage had no
relation to the Lightshare one, and was just sent back to viewers for
users on arrival to a region. Most viewers could not display WL changes
made after arrival.

LightShare, only manipulated by scripts, was also sent to viewers at
login, in a independent way using its own lludp protocol. Viewers
supporting that protocol could see and update to changes made by a
script at anytime. Using LS and a viewer's WL UI together could be
confusing. This was due to history. Lighshare was introduced when a
viewer's environment was only local and the capability was never updated
when they started sharing region WL settings.

In addition there was a server side Sun module, that did ...something
... It was mostly only valid for very old viewers.

On uglysky the internal representation of the region environment was
unified, with the parameters and structure more suitable for the new
viewers (i.e. the so called EEP viewers). Viewers only get the
environment using a new protocol, or a subset of it using WL protocol.
Sun module was removed. LightShare (LS) scripts only create the simple
subset of EEP environments they have an effect on. LS lludp protocol was
removed.

When a script changes LS settings or WL settings are changed by a user,
new EEP capable viewers will see the change. Older WL viewers that could
already see WL changes (Firestorm for example) will also see them,
others will not.

Same applies for parcel crossings. The environment change will be sent,
some WL viewers will see it (so also providing per parcel environment
capability), others will not. And the same applies to the new OSSL per
avatar forced environment (if user is using region environment).

Several new settings can only be set with a new EEP capable viewer, like
day length, day offset, altitudes or parcel environment.

Unless a region is to be used only with new EEP capable viewers, some
restrictions are recommended to continue to support WL only viewers:

  ??? - keep day cycle as 4 hours (default - some viewers may have it
hardcoded)
  ??? - keep day offset -8 hours (default - some viewers may have
something hardcoded)
  ??? - use only altitude zero (there are no altitudes on WL)
  ??? - use only one "track" on water (WL water was not part of the day
cycle)

WL viewers can change the region environment by applying water and fixed
or day cycle. This will be converted to new region data, using defaults
for other the settings WL does not have. Note that estate sun, fixed sun
and sun hour are gone (false, false, 0 now). Those are now defined by
the selected day cycle.

Day and night duration:

WL viewers used a non-linear sun time, so nights ran faster than days
with a day/night relation of about 3 to 1. New viewers do not do that,
neither will older WL viewers on uglysky regions.

This may mean that when using a WL XML saved setting to apply an
environment or using a new EEP capable viewer to import a WL setting,
the day/night relation will be 1 to 1, if that was defined on the XML
source. Regions importing WL XML saved settings from WL viewers could
deform the day cycle timing. But new EEP viewer import does not.

In the uglysky OpenSim library you should find a 1 to 1 "default" day
cycle and a modified 3 to 1 day cycle (the default used by regions).

The viewer devs made a great effort to try to keep thinks looking the
same as before, with similar parameters, but one should expect some
differences. One case in fact is not even on the rendering engine, but
on parameters validation, that does seem incorrect. Hopefully they will
fix it.

This work branch will be part of main dev code soon.

Regards,

Ubit



------------------------------

_______________________________________________
Opensim-users mailing list
Opensim-users@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users


End of Opensim-users Digest, Vol 72, Issue 8
********************************************

_______________________________________________
Opensim-users mailing list
Opensim-users@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing list
Opensim-users@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users

Reply via email to