You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
llSetRegionEnvironment(vector position, list variables) creates a mask to be overlaid upon the current region environment windlight track at position, using all the variables available to llSetAgentEnvironment(). llSetRegionEnvironment() does not alter the underlying region windlight tracks. Instead, this mask is combined into one uniform update to be sent to an avatar whenever they enter the region or the function is called. Calling llSetRegionEnvironment() with a blank list will clear out the settings mask for that position.
This function longer requires an Experience, but instead requires PERMISSION_SILENT_ESTATE_MANAGEMENT to be granted. And just like llSetAgentEnvironment(), it is easily override-able by the user by not using the "Shared environment".
llGetEnvironment() should remain the same and not return the changed environment from llSetRegionEnvironment().
llGetRegionEnvironment(vector position) should return the sum of the changes made by llSetRegionEnvironment() for the windlight track at the position.
Why is this feature important to you? How would it benefit the community?
This function allows for tweaks and changes to existing environment settings at the region level. This is especially beneficial if several regions in a larger estate or microcontinent are trying to have a uniform dynamic experience.
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'How would you like the feature to work?': 'llSetRegionEnvironment(vector position, list variables) creates a mask to be overlaid upon the current region environment windlight track at position, using all the variables available to llSetAgentEnvironment(). llSetRegionEnvironment() does not alter the underlying region windlight tracks. Instead, this mask is combined into one uniform update to be sent to an avatar whenever they enter the region or the function is called. Calling llSetRegionEnvironment() with a blank list will clear out the settings mask for that position.\r\n\r\nThis function longer requires an Experience, but instead requires PERMISSION_SILENT_ESTATE_MANAGEMENT to be granted. And just like llSetAgentEnvironment(), it is easily override-able by the user by not using the "Shared environment".\r\n\r\nllGetEnvironment() should remain the same and not return the changed environment from llSetRegionEnvironment().\r\nllGetRegionEnvironment(vector position) should return the sum of the changes made by llSetRegionEnvironment() for the windlight track at the position.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
'Why is this feature important to you? How would it benefit the community?': 'This function allows for tweaks and changes to existing environment settings at the region level. This is especially beneficial if several regions in a larger estate or microcontinent are trying to have a uniform dynamic experience.',
}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How would you like the feature to work?
llSetRegionEnvironment(vector position, list variables) creates a mask to be overlaid upon the current region environment windlight track at position, using all the variables available to llSetAgentEnvironment(). llSetRegionEnvironment() does not alter the underlying region windlight tracks. Instead, this mask is combined into one uniform update to be sent to an avatar whenever they enter the region or the function is called. Calling llSetRegionEnvironment() with a blank list will clear out the settings mask for that position.
This function longer requires an Experience, but instead requires PERMISSION_SILENT_ESTATE_MANAGEMENT to be granted. And just like llSetAgentEnvironment(), it is easily override-able by the user by not using the "Shared environment".
llGetEnvironment() should remain the same and not return the changed environment from llSetRegionEnvironment().
llGetRegionEnvironment(vector position) should return the sum of the changes made by llSetRegionEnvironment() for the windlight track at the position.
Why is this feature important to you? How would it benefit the community?
This function allows for tweaks and changes to existing environment settings at the region level. This is especially beneficial if several regions in a larger estate or microcontinent are trying to have a uniform dynamic experience.
Original Jira Fields
The text was updated successfully, but these errors were encountered: