SL Target Audience (was RE: [sldev] branches/shadow-draft missingllrender.cpp)

Bruce Tong tongb at ohio.edu
Wed May 28 15:00:34 PDT 2008


I would certainly be willing to help out, though I don't have a
consciously repeatable test case. If I take my old hardware to a
crowded sim, the viewer will likely crash within 10 mins. WL might not
even be the cause in my case.

I assumed that the crash reports send back whatever the viewer folks
wanted to see and that it just hasn't risen to the top of the pile.

I've not yet looked at the source code to the application y'all use to
report crashes, so I hope you'll pardon a question asked in ignorance.
I suspect you're sending back a stack trace. If so, is there already a
handy way to get the stack trace from what it collected? (A command
line option, perhaps?)

Regarding perceptions of WL, I think the approach to supporting older
hardware is reasonable. I don't have any expectation for older
hardware to support more advanced features. Letting older hardware
"play" as long as possible with it's targeted feature set is perfectly
apropos.

On Wed, May 28, 2008 at 11:03 AM, Soft <soft at lindenlab.com> wrote:
> Perceptions aside, some objective data would be really helpful. A
> great way to deal with WL issues would be to create a meta JIRA for
> supported hardware configurations that perform worse under the
> released version of the WL-enabled viewer, and to define some
> objective tests for these issues.
>
> The Lab doesn't have every combination of hardware out there, and so
> far as I know WL performs similar to - or better than - previous
> viewers on the hardware we do have. Some specific benchmarks and test
> scenarios identifying specific rendering problems on hardware we don't
> have are guaranteed to help more than talking a graphics heavyweight
> off of heavyweight graphics work.

-- 
Bruce Tong
Software Engineer
Office of Information Technology
Ohio University


More information about the SLDev mailing list