[opensource-dev] Draw Distance

[Erik Anderson]

Just a quick/late comment for a thread that seems to have left the subject
line a couple days ago anyhow...

Requiring the draw distance to be changed that easily smells like a bad
paradigm that needs adjusting.  It reminds me of a database engine I was
using that required me to set the hash size of indexes in order to improve
performance.  Two major versions later and the engine was suddenly smart
enough to figure it out on its own and the hash size override was
deprecated.

Shouldn't the SL client be able to figure out what a good draw distance
would be?  Maybe have it start autodetecting draw distance based on rolling
average number of polygons visible or something?

On Sat, Aug 21, 2010 at 9:36 PM, Miro Collas <miro.collas at gmail.com> wrote:

> How about bbeing able to just type it in?  Why a slider, or mouse wheel,
> which is inaccurate? How about being able to type it in chat?
>
> On 08/22/2010 12:19 AM, aklo at skyhighway.com wrote:
> > !! YES !!  If all i had to do was mouse up over the camera widget and
> roll
> > the scroll button i would be *soooooo* happy!  Serious.  i mean, Henri's
> > Cool VL innovation is great!  And i think that even if it were a mouse
> > wheel scrollable widget it should still have some kinda additional text
> > box to it where numbers can be typed in.  But to be able to look around
> > like that would be MEGA-AWESOME!!  (Just like opening your eyes *really*
> > wide...!!)
> >
> > - AK
> >
> >    I probably use the draw-distance slider more often than any other UI
> > widget. I'd probably map it to my mouse's scroll-wheel, if I could.
> >
> > On 22/08/2010 10:31 AM, Suz Dollar wrote:
> >>> This is one concept that I have wanted for at least four years in SL. I
> >>> change draw distance multiple times a day depending on where I"m
> >>> visiting. Many of my own estate regions I can use a full powered 512
> >>> draw distance. Going to my public sandbox, however, requires an instant
> >>> drop to 128 or lower. Visiting my old 'hometown' of Caledon, mandates
> >>> the same. And I have to be honest, the places I can still use 512 draw
> >>> distance with viewer 2.x has dropped dramatically. I now usually can't
> >>> use higher than 256 yet have been assured since the first beta release
> >>> that there should be no performance difference between 1.23 and 2.x
> with
> >>> regard to graphics. An easily accessible way to change draw distance
> >>> would be awesome. I'm also frustrated that its so much harder with the
> >>> slider to hit the magic numbers: 64, 96, 128,  256.... you get the
> idea.
> >>> But if the slider were at least out on the main UI somewhere, my own
> >>> preference being up in the navigation area, but anywhere directly
> >>> accessible, would be AWESOME.
> >>>
> >>> Char
> >>>
> >>>
> >>> aklo at skyhighway.com wrote:
> >>>>> There was some talk lately about draw distance.  i mentioned that
> > from my
> >>>>> place if i have my draw distance turned up over about 150 i can
> almost
> >>>>> count on crashing when i tp.  i'm really sorry i can't describe the
> >>>>> problem any better than that.  If someone wants to tell me how i
> could
> >>>>> understand it better, i'd love to listen?
> >>>>>
> >>>>> Anyway, i mentioned in mail to this list that it would be really
> > cool if
> >>>>> there were an onscreen widget like the movement&   camera controls
> that
> >>>>> made draw distance a lot easier to change.  Please forgive me for not
> >>>>> having already figured out how to do that myself.  Just sayin' tho,
> it
> >>>>> would be really nice if, like for instance, Snowglobe had either a
> > mouse
> >>>>> gesture, keyboard short cut, or onscreen widget (all three?) for
> > rapidly,
> >>>>> easily changing draw distance,  i think it's a function that lots of
> >>>>> people would use heavily.  i know there's performance concerns, but
> if,
> >>>>> for instance, the onscreen widget included a simple performance bar
> >>>>> indicator that went down as the draw distance was turned up, that
> would
> >>>>> communicate pretty well to all the people who didn't know better for
> >>>>> whatever reason.
> >>>>>
> >>>>> The tp crash i get is just one more reason to make the setting easy
> to
> >>>>> deal with.  Besides, to me it seems like such a natural part of
> camera
> >>>>> controls that i don't know why it's not there already?  If it was me
> >>>>> adding the feature i'd put it in the camera controls widget.  i'd
> been
> >>>>> using SL for several months before i even realized that draw
> > distance was
> >>>>> configurable.
> >>>>>
> >>>>> Thanks for listening!
> >>>>>
> >>>>> _______________________________________________
> >>>>> Policies and (un)subscribe information available here:
> >>>>> http://wiki.secondlife.com/wiki/OpenSource-Dev
> >>>>> Please read the policies before posting to keep unmoderated posting
> > privileges
> >>>>>
> >>>>>
> >>> _______________________________________________
> >>> Policies and (un)subscribe information available here:
> >>> http://wiki.secondlife.com/wiki/OpenSource-Dev
> >>> Please read the policies before posting to keep unmoderated posting
> > privileges
> >>>
> > -- Tateru Nino http://dwellonit.taterunino.net/
> > _______________________________________________ Policies and
> (un)subscribe
> > information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> > Please read the policies before posting to keep unmoderated posting
> > privileges
> >
> > _______________________________________________
> > Policies and (un)subscribe information available here:
> > http://wiki.secondlife.com/wiki/OpenSource-Dev
> > Please read the policies before posting to keep unmoderated posting
> privileges
> >
>
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20100823/2151e11e/attachment-0001.htm