Some complaints

MANY graphical glitches on my Radeon 9800 Pro. At sunrise, sunset, and nighttime, the game looked AWFUL. http://md.pyoko.org/thebeach.jpg

The circle in the center is to be expected, that's my avatar's clothing. The... reflection... thing... is... The ocean trying to be reflective. I guess. You can see a small strip of land. Walking inside buildings missing random textures is absolutely surreal.

And object creation. There's no option to boolean two primitives in any way. Wouldn't that cut down on the overall poly count?

The semi-modifiable land is annoying as well. Is it already allowed to be modified to the extent of its height map? It seems as if there's the server's knowledge of the original height map, and that cannot be deviated from too much, which impeded my friends attempts to build on their land.

The readily available documentation on the scripting language was also inadequate. I couldn't understand how to make llListen work correctly. Additionally, the units used in several places (at least in llparticlesystem) needs to be better explained.

--Fearing I sound like a 9th grader.

The entire scripting community feels the same way (probobly). Catherine Omega and the Nexcorp/Tyrell Group set up a wiki (user-created/user-maintained documentation) on their webpage, http://www.badgeometry.com/

It totally rocks IMHO
If you can't find the info your looking for there, just post a question to the Scripts & Scripting forum, people (including me ) would be happy to help yah out.
==Chris

Yikes, double post, my browser lagged

turn off the moving water shader (i forget the exact name)

its quasi broken and doesn't 'dissapear' into the horizon properly, causing that really weird effect

I assume you're running the latest drivers, correct? The most recent ones apparently fixed several problems with your card and SL.



SL's "primitives" really aren't. They're actually parametric models. Rather than being defined as six vertices, a box in SL is defined by listing the position, rotation and dimensions, then deforming it.

Yes, it means that SL is rendering more polygons than it really needs to be, but it reduces the amount of data needed to represent the objects. It's a tradeoff between framerate and bandwidth.

There are obviously far more tricks that could be done to further conserve bandwidth and decrease polycount -- client-side vertex merging, instancing of linked objects, (why download the data to describe 100 prims when you can download the data to describe 10 of them and then just repeat it 10 times?) and so on.
The semi-modifiable land is annoying as well. Is it already allowed to be modified to the extent of its height map? It seems as if there's the server's knowledge of the original height map, and that cannot be deviated from too much, which impeded my friends attempts to build on their land.



Here you go.