🪰 Viewer Bug Reports

• Use concise, precise descriptions• Do not include sensitive information. • Create a support ticket at https://support.secondlife.com for individual account issues or sensitive information.
After 22 years... why do textures take so long to rez?
"If the 2D don't work, the 3D don't work". I was at Sci Fi Con 17. All day long, no matter how many or how few avatars were on a region, textures took ruddy ages to load. Now one might say "There are so many textures at a big event it just takes a long time." But I'd walk into an enclosed room... where textures should be limited, yet the vendors on the wall just sat there and sat there and sat there. Textures RIGHT NEXT TO ME fail to load. One can stand there and stand there and stand there... and they still don't rez. I would click on a texture and tell it TEXTURE REFRESH... and it would ignore that instruction. I first reported texture issues and bottlenecks back in 2005. Now my computer and graphics card is hundreds of times more powerful... and textures still load at a snail pace. I will say the same thing I said back then: There is a texture bottleneck on SL. (Or, several texture bottlenecks, and it affects EVERYTHING.) With respect, I'm not asking for an explanation, nor excuses. I'm making a simple observation: After 22+ years online, Second Life should be able to very quickly load 2D textures in an enclosed room. Is this not correct? I suspect there will be people all too ready to give reasons why textures load slowly. To any and all such reasoning, I have one answer: Second Life needs to make textures load quickly. There's no argument, debate, discussion or excuse to that simple statement. Users need textures to load quickly enough that we don't get bored standing in a store (waiting for vendor textures to load)... and decide to go do something else. Like Netflix. ;D Because that's what it is: Second Life vs Netflix. Users have options on how to spend their time. When Netflix can stream entire videos realtime, surely Linden Lab should be able to send 2D textures across the Internet... yes? As a note: I'm not going to debate nor discuss or argue with those who are always ready to argue on these feedbacks. The feedback is posted, I've said what I came to say... and I have to believe the vast majority of SL users will agree with this: textures on SL need to load faster.
24
High Resolution snaps crashes viewer
Tp to http://maps.secondlife.com/secondlife/Le%20Monde%20Perdu/87/179/26 set settings to ultra Open Snapshot to Disk Set resolution to 7680x4107 Save (though it might take a few refresh/saves to repro) Results: Viewer crashes. This is a brand new high end pc, I should be able to take high resolution snaps Event Viewer log entries: Faulting application name: SecondLifeViewer.exe, version: 7.1.15.13558, time stamp: 0x6849ff57 Faulting module name: nvoglv64.dll, version: 32.0.15.7652, time stamp: 0x6824e4c4 Exception code: 0xc0000409 Fault offset: 0x000000000106e00d Faulting process id: 0x7DB0 Faulting application start time: 0x1DBDC4D62E127B4 Faulting application path: C:\Program Files\SecondLifeViewer\SecondLifeViewer.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2c61c4d89b199ea8\nvoglv64.dll Report Id: 66e51c40-46cd-4dde-b2a3-bb0c54d9c00b Faulting package full name: Faulting package-relative application ID: --------------------------- A TDR has been detected. The application must close. Error code: 7 (pid=32176 tid=15888 secondlifeviewer.exe 64bit) Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information. ------------------------------ Faulting application name: SLPlugin.exe, version: 0.0.0.0, time stamp: 0x6849fd08 Faulting module name: libcef.dll_unloaded, version: 118.4.1.0, time stamp: 0x651cb3d9 Exception code: 0xc0000005 Fault offset: 0x00000000046433f0 Faulting process id: 0x53EC Faulting application start time: 0x1DBDC4D702FA691 Faulting application path: C:\Program Files\SecondLifeViewer\SLPlugin.exe Faulting module path: libcef.dll Report Id: d393b7a3-1a0b-40ac-8190-ef4d9c3a1e90 Faulting package full name: Faulting package-relative application ID: I have the full sl log and the full event viewer log entries if needed. This repros with the previous version, I'd been trying document the crash when this morning I was prompted to update the viewer.
3
Load More
→