[#VWR-2901] Contents fail after installing the release candidate

1. Second Life Viewer - VWR

Contents fail after installing the release candidate

Created: 29/Oct/07 12:45 AM Updated: 07/Apr/08 04:14 PM

Component/s:

Building (in-world)

Affects Version/s:

1.18.3.5, 1.18.4 Release Candidate

Fix Version/s:

1.19.1.4

Time Tracking:

Not Specified

Environment:

« Hide

Second Life 1.18.3 (5) Sep 20 2007 11:41:23 (Second Life Release)

You are at 219220.0, 296459.1, 32.6 in Scepterd Isle located at sim5174.agni.lindenlab.com (8.2.32.175:13006)
Second Life Server 1.18.3.71877

CPU: AMD (Unknown model) (1838 MHz)
Memory: 2047 MB
OS Version: Microsoft Windows XP Service Pack 1 (Build 2600)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: RADEON X700 Series x86/MMX/3DNow!/SSE2
OpenGL Version: 2.0.6458 WinXP Release
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 0/1678 (0.0%)
Viewer Digest: 90685140-2f12-8f78-b80a-1d453326d7c2

Description

« Hide

This is a tough one I will admit...
After installing several 1.18.4 versions, I find that I am unable to see the contents of my own scripts and scripted objects. For example, the UUID of a script in inventory comes up as all zeros.

Not just in the release candidate, but also if you re-run (without installing) the released version (1.18.3)

As best as I can reproduce here are the steps:
1) Run happily with the released version
2) Install the release candidate and run until you find something that you don't like
3) Go back to running the released version - can't do much
(symptoms at this point for me is that the contents of objects don't get fetched - and if you shop, some vendors fail to show you the contents of your purchase)
4) relog has no effect
5) clearing cache has no effect

Good news is that reinstalling the released version does clear the problem. Bad news is that there is a migration issue (IMHO)

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Emileigh Starbrook added a comment - 29/Oct/07 12:48 AM

Some additional data that points to the viewer:

1) my main system is windoze XP. If I log in on my mac laptop, running the release version, all is happy.
2) If I log into my main system using an alt who has mod, the same bug occurs. If she logs onto my laptop, all is happy.

So (imho) it points to the system that the upgrade occurred upon, and is not related to the service

[ Permlink | « Hide ]

WarKirby Magojiro added a comment - 29/Oct/07 03:16 AM

There were asset issues last night which may have caused this.
Are you still seeing it ?

[ Permlink | « Hide ]

Emileigh Starbrook added a comment - 07/Apr/08 04:14 PM

Not reproducible in current release so closing