[BUG-37653] Every time I delete Cache and Relog, my Saved Appearances do not load and I am left as a White Cloud in Second Life Viewer 4.0.7.318301 #11991
Comments
Whirly Fizzle commented at 2016-08-13T14:13:24Z, updated at 2016-08-13T14:40:45Z Heya ItalianTony, Ouch yes, I can reproduce this on Second Life 4.0.7.318301 (Second Life Release) pretty consistently. Also note that Loki also mentioned on BUG-37610 that he had a persistent problem getting his avatar to rez on Maint-RC but not on the then current release.
In addition to the cloudy avatar problem on the new release, there is also this problem with attachments that appears to be new on this build: BUG-37646 On Second Life 4.0.7.318301 (Second Life Release), if you clear cache and login and wait for your inventory to fetch, your skin, shape, system hair and system eyes do not populate in the Current Outfit folder, so your avatar will never rez. However, if you clear cache & login on 4.0.7.318301 and while inventory is fetching, you expand the Current Outfit folder quickly before the contents have started to fetch , this appears to stop the problem from happening & system layers and the 4 base body parts get worn and your avatar will rez. Something has definitely gone seriously wrong with COF & avatar appearance on 4.0.7.318301. In addition, when your inventory has finished fetching & you are still stuck as a cloud, the usual trick of replacing outfit does not fix the problem. 2016-08-13T14:15:16Z WARNING: LLAppearanceMgr::updateAppearanceFromCOF: COF info is not complete. Version 171085 descendent_count -1 viewer desc count 21
2016-08-13T14:15:16Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: Could not put on outfit.
The outfit folder contains no clothing, body parts, or attachments. Second Life 4.0.7.318301 (Second Life Release)
Release Notes
You are at 79.0, 83.9, 21.9 in Testylvania Sandbox located at sim10234.agni.lindenlab.com (216.82.49.156:12035)
SLURL: http://maps.secondlife.com/secondlife/Testylvania%20Sandbox/79/84/22
(global coordinates 332,623.0, 306,260.0, 21.9)
Second Life RC BlueSteel 16.08.01.318271
Error fetching server release notes URL.
CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (3491.92 MHz)
Memory: 16268 MB
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 750/PCIe/SSE2
Windows Graphics Driver Version: 10.18.0013.6881
OpenGL Version: 4.5.0 NVIDIA 368.81
J2C Decoder Version: KDU v7.2
Audio Driver Version: FMOD Ex 4.44.31
LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32)
Voice Server Version: Vivox 4.6.0017.22050
Packets Lost: 0/32,066 (0.0%)
August 13 2016 07:13:01 |
Whirly Fizzle commented at 2016-08-13T16:35:35Z I did quite a few cache clears & relogs on the previous Second Life 4.0.6.315555 release & I cannot reproduce this bug. |
ObviousAltIsObvious commented at 2016-08-13T20:51:21Z Happening here too, the changing outfit spinner never stops in the appearance floater, so that route to uncloud is never available. Dragging an outfit folder on to the avatar from the inventory floater seems to be bypassing that to unstick it here. |
Steps to Reproduce
Performing any act and then deleting cache and relogging in the latest version of Second Life Viewer
Actual Behavior
With the latest Release of Second Life Viewer (Second Life 4.0.7.318301), every time I delete cache and relog, when I relog, my Saved Appearances fail to load and I am left as a White Cloud until I relog again. Then the Saved Appearances are loaded successfully after I relog twice, and I am rezzed properly with the Saved Appearance I last had on before I deleted cache and relogged originally. I have not tried to see if the Bug occurs with any of my Alts or asked if anyone else is experiencing this Bug as well on the latest release of Second Life Viewer.
Expected Behavior
I should expect my Saved Appearances to fetch after I relog just as the rest of my Inventory fetches properly.
Other information
Attachments
Links
Related
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: