Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

BUG: Draw distance drop unreliable

Shack Dougall
self become: Object new
Join date: 9 Aug 2004
Posts: 1,028
06-16-2005 10:07
Sorry for the duplicate post. I had it all described nicely, but accidentally overwrote it with an edit. :o

So I've been having some unusual clientside performance issues. And I couldn't explain it with server stats. And I couldn't explain it with client side effects such as network congestion.

What I've discovered is that the SL client doesn't drop the draw distance in the way that I'd expect. Looks like a bug, but maybe someone will explain how it's a feature. :D

So two snapshots.

First, a picture of me in Selby. As you can see, I have draw distance set to 192 and I've specified that it should drop the draw distance if FPS < 10. If you look at the mini-map, you will see that it's dropped the draw distance to 64m, but the client FPS is still less than 10. Also, note that the building in the distance is more than 64m away. It's grayed out, but it's still being displayed.

I would also note that if I manually set my draw distance to 64m, relog, and fly all around the sim, then I maintain a constant FPS of 45!

The second snapshot is me flying around in the crippled state. Notice the building in the distance. Also, more than 64m away. And it didn't exist in my original view. As I started flying toward it, it rezzed into view...even tho it's supposed to be outside my dropped draw distance! It's grayed out, too, but still putting load on my client. My FPS has now dropped to 5.5!

So, what's going on guys?!? it looks like the draw distance drop feature is totally borked!
_____________________
Prim Composer for 3dsMax
-- complete offline builder for prims and sculpties in 3ds Max
http://liferain.com/downloads/primcomposer/

Hierarchical Prim Archive (HPA)
-- HPA is is a fully-documented, platform-independent specification for storing and transferring builds between Second Life-compatible platforms and tools.
https://liferain.com/projects/hpa
Chromal Brodsky
ExperimentalMetaphysicist
Join date: 24 Feb 2004
Posts: 243
06-16-2005 10:41
Yeah, I believe I noticed this in v1.4.x. The auto-draw-distance control will determine how many objects are sent to be drawn on your video card, but the non-graphical procsesing for all of those objects will still occur. So, you'll often find that an autodraw set to, say, 256m but only drawing 128m will be slower than a non-auto draw distance locked to 128m.

How is autodraw useful? Presumably only if your graphics card is slower at drawing than your main CPU is at the non-graphical object updates. Or so I'm guessing. Anyone else care to weigh in on this?