[#VWR-12536] Depth snapshot capture broken in latest 1.22.11 RC

1. Second Life Viewer - VWR

Depth snapshot capture broken in latest 1.22.11 RC

Created: 22/Mar/09 06:39 AM Updated: 26/Mar/09 02:59 AM

Return to search

Component/s:

Graphics

Affects Version/s:

1.22

Fix Version/s:

None

File Attachments:

None

Image Attachments:

1. Snapshot.png
(87 kB)

2. UI.png
(1.04 MB)

Environment:

« Hide

Second Life 1.22.11 (113976) Mar 6 2009 16:05:03 (Second Life Release Candidate)

You are at 240990.1, 274024.8, 22.2 in Sunbeam located at sim2092.agni.lindenlab.com (216.82.16.97:13002)
Second Life Server 1.25.6.113484

CPU: Intel Pentium M Series Processor (1995 MHz)
Memory: 1023 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: ATI MOBILITY RADEON X700
OpenGL Version: 2.1.8494 Release

Issue Links:

Relates

This issue Relates to:

VWR-7709 Meta: Snapshot malfunctions (RC 1.20.x)+

VWR-12080 Meta-Issue: Issues with ATI Catalyst 7.12-9.10

Description

« Hide

Taking snapshots in Depth capture mode is broken on the latest RC viewer (1.22.11):

1. Click on Snapshot;
2. Whichever resolution;
3. Select Save to your hard drive;
4. In Capture, select Depth;
5. Press Refresh Snaphot - the in-world preview looks broken (attaching screenshot of it);
6. Press Save - the snapshot on the hard drive is broken (attaching snapshot).

Thank you for your attention good luck!

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 22/Mar/09 11:39 AM

Does not reproduce for me using a nVidia graphics card, maybe an ATI problem?

[ Permlink | « Hide ]

Fax Fellini added a comment - 26/Mar/09 02:59 AM

Reading the related Meta-issue VWR-12080 (Issues with ATI Catalyst 9.1/9.2) and other issues from there, I tried disabling Catalyst AI (was set to standard), to no avail.

I will wait for the 9.4 version of the driver, unless I find time to install 9.3 meanwhile. In the meantime, is there any more info I can provide? The issue is clearly not closed, but I wouldn't want to reopen it without new helpful info.

Thanks