Flattened and twisted

There are some threads in the forum describing how to make shapes larger than 10m along some directions.

I find this technique very valuable as it only uses "legal" objects (i.e. no mega nor tortured prims) to save you prims count and should no pose any issue of future compatibility.

I just have a question on possible rendering lag. Some of those will be rendered with a lot of twisted (and possibly hidden) polygons could this introduce some lag or it is no worse than with regular prims?

Also, has anybody published a catalog of those shapes?

Rael

If I'm not mistaking, the 3D is rendered by the client, so it doesn't create any lag.

Simil, I believe Rael is asking about client side lag, not server lag, so while your observation that what he's asking about is a rendering issue is correct, your definition of "lag" in this context is a bit off.

Rael, any and all polygons rendered consume processor power and memory. The more polys that are on your screen, even if they're hidden, the harder your computer has to work to create and track them all. So, yes, in that sense, a twisted prim is more "laggy" than an untwisted one. To see how many polys are added by twisting, go into wireframe view, and compare a twisted cube with an untwisted one. You'll see that the twisted one has many times more polygons in it, just as you had assumed.

I thought that lag was a term employed only for network.

In SL, people tend to define "lag" as anything that noticeably slows performance. We've therefore got "client side lag", "server side lag", "network lag". It's all in there.

Thanks for the answers. Sorry I might have been imprecise in using the term "lag" in the sense of "noticeable delay or slowdown due to an increased demand of server, client or network resources".

I'll try to using sparingly anyway, just in case ...

Now I only need to check if someone collected the parameters for this prims somewhere

Rael

I'm not sure it's possible to assemble a complete list. The amount of polygons drawn will depend on your graphics settings, and your camera distance from the object. If you're really interested in a count, I'd suggest turning on wireframe view so you can see the polys, and then count them by hand. You'll notice that it doesn't take much distance for a significant potion of them to disappear.