[#VWR-12933] After Login Textures take a long time to Load.

1. Second Life Viewer - VWR

After Login Textures take a long time to Load.

Created: 22/Apr/09 01:14 PM Updated: 21/May/09 11:24 AM

Return to search

Component/s:

Graphics

Affects Version/s:

1.23 Release Candidate, 1.23 Public Nightly

Fix Version/s:

None

File Attachments:

Snapshot_001.bmp (1.12 MB)

Image Attachments:

1. realoded textures.png
(2.53 MB)

2. Skat_beach.png
(1.58 MB)

3. TextureConsoleStuck.png
(168 kB)

Environment:

« Hide

Second Life 1.23.0 (117724) Apr 17 2009 21:19:23 (Second Life Public Nightly)
Release Notes

Built with MSVC version 1400

You are at 242029.9, 255332.5, 351.6 in Eros Ousia located at sim2863.agni.lindenlab.com (216.82.19.106:13001)
Second Life Server 1.26.2.117266
Release Notes

CPU: Intel Core 2 Series Processor (1595 MHz)
Memory: 2047 MB
OS Version: Microsoft Windows Vista Service Pack 1 (Build 6001)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 7300 GT/PCI/SSE2
OpenGL Version: 2.1.2

libcurl Version: libcurl/7.18.1 OpenSSL/0.9.8j zlib/1.2.3
J2C Decoder Version: KDU
Audio Driver Version: FMOD version 3.740000
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.23374 (Mozilla GRE version 1.8.1.21_0000000000)
Packets Lost: 4676/139847 (3.3%)

Issue Links:

Relates

This issue Relates to:

~~VWR-11420~~ Textures are removed from viewer memory too aggressively

VWR-8503 Meta-Issue: Poor texture loading and freezes indicate larger chain of bugs

This issue is related to by:

VWR-13486 Texture rendering fail

VWR-12915 Menu icons load slow

~~VWR-13019~~ Textures Slow To Load

~~VWR-13418~~ Texture cache not working

Last Triaged:	21/May/09 11:24 AM
Linden Lab Issue ID:	DEV-32682

Description

« Hide

After login all textures from terrain upwards take a while to load in relation to the 1.22.11 viewer. Textures also take a little more time in general to load when moving to another region.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Baloo Uriza added a comment - 24/Apr/09 02:42 AM

I suspect this is a duplicate of VWR-8503, please close as such if true (otherwise, feel free to fix the link)

[ Permlink | « Hide ]

Ellla McMahon added a comment - 27/Apr/09 03:04 PM

It may be helpful to the LL Developers to add further details to this issue. Please see VWR-8503 dan linden added a comment - 06/Jan/09 06:57 PM

Make sure your Texture Memory is not set higher than 512 MB. Preferences > Graphics > Hardware Options > Texture Memory (MB)

Paste the information from the Help > About Second Life window.

Attach a screenshot (use Attach file over there on the left) that shows your texture console. To display the texture console, first toggle on the Advanced menu (ctrl-alt-shift-d), then toggle on the texture console, (ctrl-shift-3). In SL, click the Snapshot button, choose Save to hard drive, click ">> more", check "Show interface in snapshot", set format to PNG, and save it.

Thank you : )

[ Permlink | « Hide ]

TriloByte Zanzibar added a comment - 30/Apr/09 12:10 PM

Why couldn't all the votes on the other issue been carried over, if it's a duplicate?

My computer has 512MB texture memory, and SL is set to only use 256MB texture memory. Textures are slow to load, and frequently are 'lost' and need to be re-loaded after turning around. This affects both the public nightly and the release candidate.

[ Permlink | « Hide ]

Yann Dufaux added a comment - 09/May/09 02:29 PM

i have noticed this on the last public nightly.

–
Second Life 1.23.1 (119600) May 7 2009 21:21:41 (Second Life Public Nightly)
Notes de version

Built with MSVC version 1400

Votre position : 226686.7, 303693.1, 21.9 in Kanda located at sim4312.agni.lindenlab.com (216.82.53.216:13000)
Second Life Server 1.26.3.118673
Notes de version

CPU: Intel Core 2 Series Processor (2304 MHz)
Memory: 2048 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8600 GT/PCI/SSE2
Windows Graphics Driver Version: 6.14.0011.8250
OpenGL Version: 3.0.0

libcurl Version: libcurl/7.18.1 OpenSSL/0.9.8j zlib/1.2.3
J2C Decoder Version: KDU
Audio Driver Version: FMOD version 3.740000
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.23783 (Mozilla GRE version 1.8.1.21_0000000000)
Packets Lost: 801/2799394 (0.0%)
–

confirmed for me

[ Permlink | « Hide ]

Sunn Thunders added a comment - 09/May/09 05:07 PM

My experience lately has been that texture loading gets "stuck" after a while (an hour maybe?). I've attached a picture above to show the Texture Console in its stuck position. The white colored textures shown at the top of the image just freeze up and seem to clog the whole texture-loading system. Once this happens, remaining unrezzed textures within the field of view remain gray indefinitely. In the past I could remedy this by zooming way in with the camera to force-load textures, but this trick doesn't seem to unclog things like it used to. Sometimes I've noticed a texture listed on the console as either BAD or MIS--not sure if that triggers the clog.

[ Permlink | « Hide ]

Sunn Thunders added a comment - 09/May/09 05:11 PM

Snapshot of texture console in "stuck" position--no useful texture loading occurring...

[ Permlink | « Hide ]

Sandor Balczo added a comment - 11/May/09 12:43 AM

I have noticed the same behavior described here on an iMac with the following features:

CPU: Dual i386 (Unknown) (3060 MHz)
Memory: 4096 MB
OS Version: Darwin 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce 8800 GS OpenGL Engine
OpenGL Version: 2.0 NVIDIA-1.5.36

I have also noticed that transparent or semi-transparent (alpha) textures and sculpties seem to be more affected by this problem, which generates an overall drop in the frame rate. I attach a snapshot (Skat_Beach.png) showing the look of a sculpted palm tree and a shadow for about five minutes after login. In the 1.22 viewer, textures and shadows load almost instantly.

I am aware that LL has reported issues with textures in a few regions two days ago and declared it has been solved, but either the region I am in (Skat) is still affected or I was particularly unlucky because I have experienced the same behavior almost everywhere I went.

Sandor