"just" 100 MBit/s) it might take some time to flush all that data down the pipe for rendering, so some intelligent z-depth sorting and blur effect might help to get a nicer effect while loading happens.Ģ) Speed of rezzing/loading while on the moveĪ huge draw distance is nice, but i am just fine with a few imposters in the distance if moving around faster. Thats okay if i am stationary and just want to gaze into the distance.
#SECOND LIFE VIEWER FULL#
I think there are a few things to consider here:ġ) Speed of rezzing/loading the whole static scene.Īfter all, even with 256m draw distance, the viewer needs to ingest a huge amount of textures and meshes to render the full view. So some amount of blur over dusty places like cities is probably okay.īut i agree with others that a cutoff at 128m is a bit harsh on the eyes. heated air over asphalt roads), dust, fog and other particles in the air that cause light to bend. You may also get blur like effects due to air movements (e.g. The user could then select which ones they want via a viewer setting.Īnother thing to consider is selecting imposter distance based on the users relative camera altitude to the view.Ĭonceptually, in RL you get a blur when things are far away. Perhaps two imposters could be generated, one with and one without blur. If it helps with rendering avatars then it would seem like a good idea. As I've said previously I keep my viewer at 256sqm most of the time and get frame rates in excess of 30fps unless there are lots of avatars so that's doable.
At ground level 256sqm is more than adequate in my opinion. I think a 1024sqm distance is far too much unless you are at a vantage point such as a tower as in the picture. Would a normal user want to sort of see everything and have a sense of a much wider world at 30fps, or the current way it works with limited worldview and get 5-9fps? I enjoy the technical posting of both and Beauchamp a lot, I get to learn things.
I also agree that the blur while not the best, isn't as bad as suggested.
0 kommentar(er)
