secondlife / jira-archive

3 stars 0 forks source link

[BUG-225553] [FIXED] [EEP]The environment "Only to myself" is disabled when avatar crossing the border region #4322

Closed sl-service-account closed 9 months ago

sl-service-account commented 6 years ago

What just happened?

Actual result: The environment "Only to myself" is disabled when avatar crossing the border region.

What were you doing when it happened?

Steps:

  1. Login in the viewer.
  2. Open "World"-> "Environments"  > "My Environments..".
  3. Right-click on "New Day Cycle" and click "Apply Only to Myself".
  4. Cross the border of the region.

    What were you expecting to happen instead?

Expected result: The Environment looks the same when your avatar crosses the border to a region with different Environment settings.

Other information

Note: This behavior reproduces time to time.

Attachments

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-225553 | | Summary | [FIXED] [EEP]The environment "Only to myself" is disabled when avatar crossing the border region | | Type | Bug | | Priority | Unset | | Status | Closed | | Resolution | Cannot Reproduce | | Labels | whirly-eep | | Reporter | IgorL ProductEngine (igorl.productengine) | | Created at | 2018-09-27T15:12:52Z | | Updated at | 2020-06-15T15:23:11Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2018-09-27T13:26:59.884-0500', "Is there anything you'd like to add?": 'Note: This behavior reproduces time to time.\r\n', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'Actual result: The environment "Only to myself" is disabled when avatar crossing the border region.', 'What were you doing when it happened?': 'Steps: \r\n1. Login in the viewer.\r\n2. Open "World"->"Environment"->"My Environments..".\r\n3. Right-click on "New Day Cycle" and click "Apply Only to Myself".\r\n4. Cross the border of the region.', 'What were you expecting to happen instead?': 'Expected result: The Environment looks the same when your avatar crosses the border to a region with different Environment settings.', } ```
sl-service-account commented 6 years ago

Dan Linden commented at 2018-09-27T18:27:00Z

Rider and I are not able to reproduce this. Needs more info.

1) Does this reproduce with a default New Day Cycle? 2) Does "World menu > Environment > Use Shared Environment" become checked after crossing into the next region? 3) Are you able to repro this bug between EEPTesting <-> Animesh2 regions?

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-09-28T19:56:58Z, updated at 2018-09-28T19:59:38Z

I can reproduce this consistently on Second Life Test 5.1.10.520017 (64bit)

Observed

Expected To still be seeing the default day cycle locally after crossing back into EEPTesting region.

Test system


Second Life Test 5.1.10.520017 (64bit)
Release Notes

You are at 248.8, 63.8, 23.0 in EEPTesting located at sim9903.aditi.lindenlab.com (216.82.33.218:13004)
SLURL: secondlife://Aditi/secondlife/EEPTesting/249/64/23
(global coordinates 342,521.0, 343,616.0, 23.0)
DRTSIM-351 18.09.25.519968
Release Notes

CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (3491.95 MHz)
Memory: 16268 MB
OS Version: Microsoft Windows 7 SP1 64-bit (Build 7601)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 750/PCIe/SSE2

Windows Graphics Driver Version: 23.21.13.9135
OpenGL Version: 4.6.0 NVIDIA 391.35

Window size: 1920x1021
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.125
Render quality: 2
Advanced Lighting Model: Disabled
Texture memory: 512MB
VFS (cache) creation time: September 26 2018 09:25:17

J2C Decoder Version: KDU v7.10.4
Audio Driver Version: FMOD Ex 4.44.64
Dullahan: 1.1.1080 / CEF: 3.3325.1750.gaabe4c4 / Chromium: 65.0.3325.146
LibVLC Version: 2.2.8
Voice Server Version: Vivox 4.9.0002.30313

Packets Lost: 170/147,328 (0.1%)
September 28 2018 12:56:41
sl-service-account commented 6 years ago

Dan Linden commented at 2018-09-28T23:22:22Z

That doesn't repro for me either, Whirly. Maybe I need a longer server ping time to see the bug.

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-09-29T12:05:11Z

This is odd. I can't reproduce it either now. I'm using the same viewer version, Second Life Test 5.1.10.520017 (64bit) and running through exactly the same repro steps as above. There must be another step to the repro or some condition to trigger it that isn't obvious. I'll update when I find it.

My current Ping Sim is 184ms (I'm in the UK)

sl-service-account commented 6 years ago

DmitryS ProductEngine commented at 2018-10-02T15:12:14Z

Investigated in the scope of IQA-5881 task:

This behavior was observed in estate managers.

Parcel owners did not reproduce the bug.

Also, estate managers reset their environment settings to regional ones when ‘Region/Estate’ floater is opened (see ‘Region_Estate floater.mov’)

sl-service-account commented 6 years ago

Dan Linden commented at 2018-10-03T19:09:57Z

The "estate managers reset their environment settings to regional ones when ‘Region/Estate’ floater is opened" can be filed as a new bug.

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-10-03T20:09:00Z, updated at 2018-10-03T20:10:25Z

I filed a related issue to that at BUG-225564 I suspect it's expected behaviour for EMs to have environment revert to region environment if they open the Environment tab of Region/Estate though - but it shouldn't get stuck after closing the Region floater.

sl-service-account commented 6 years ago

Dan Linden commented at 2018-10-06T20:57:15Z

BUG-225564 should be fixed in 5.1.10.520192, which has not shipped yet. When that or subsequent build ships, this (BUG-225553) should be tested again.

sl-service-account commented 6 years ago

IgorL ProductEngine commented at 2018-10-08T09:53:37Z, updated at 2018-10-08T09:56:16Z

Cannot Reproduce on Second Life Project EEP 5.1.10.520322 (64bit) in the scope of IQA-5895. Pass in QA.