Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

[BUG-225825] [EEP] Rainbow and Halo use wrong textures #4532

Closed
sl-service-account opened this issue Nov 16, 2018 · 0 comments
Closed

[BUG-225825] [EEP] Rainbow and Halo use wrong textures #4532

sl-service-account opened this issue Nov 16, 2018 · 0 comments

Comments

@sl-service-account
Copy link

sl-service-account commented Nov 16, 2018

What just happened?

The Halo uses Rainbow texture and the Rainbow uses Halo texture.

What were you doing when it happened?

  1. Login to EEP region with EEP Viewer as Estate Manager;
  2. Take a copy of the box from the secondlife://Aditi/secondlife/Product%20Engine%20Apollo1/14/151/31
  3. Apply the environment setting from the object content to the region;
  4. Observe the Sky.

What were you expecting to happen instead?

Rainbow and Halo use correct textures.

Other information

Attachments

Original Jira Fields
Field Value
Issue BUG-225825
Summary [EEP] Rainbow and Halo use wrong textures
Type Bug
Priority Unset
Status Closed
Resolution Accepted
Labels eep, whirly-eep
Reporter RomanK ProductEngine (romank.productengine)
Created at 2018-11-16T14:17:07Z
Updated at 2020-06-15T15:23:31Z
{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'The Halo uses Rainbow texture and the Rainbow uses Halo texture.',
  'What were you doing when it happened?': '1) Login to EEP region with EEP Viewer as Estate Manager;\r\n2) Take a copy of the box from the [secondlife://Aditi/secondlife/Product%20Engine%20Apollo1/14/151/31]\r\n3) Apply the environment setting from the object content to the region;\r\n4) Observe the Sky.',
  'What were you expecting to happen instead?': 'Rainbow and Halo use correct textures.',
}
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant