Jump to content

Miriel Enfield

Resident
  • Posts

    12
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. DanielRavenNest Noe wrote: Also the 250K triangle budget is based on a region full of mesh objects. A PC on the low setting has a draw distance of 64m, and can only actually see 20% of a region at a time. The combined effect of these penalties ensures that parcel costs of mesh range from high to absurd relative to sculpts. Agreed. And I know I've hammered on this before (even if I did mess my math up a bit in the other thread), but penalizing meshes compared to sculpts isn't doing anyone on an older computer any favors. If you make it cheaper to use sculpts instead of more efficient meshes, you'll get more sculpts instead of meshes.
  2. Count me as another one of the people who thinks the current PE costs are a problem. Or, to be more specific, the PE costs are a problem when compared to other prim costs. Let me give an example. A few years ago, I made a little grove of three beech trees using megaprims and five sculpted prims. That's, per tree, 1 2/3 prims and - I'll round up - 3414 triangles. Tonight, I made a nearly identical mesh tree, a single copy of which weighs in at 800 triangles and 16 PE. If I decide to be scrupulously fair and link three of them together, the whole thing comes in at 47 PE, saving me the equivalent of one whole prim. I've gone from 2048 triangles per prim with the sculpties to a little over 17 triangles per prim with the mesh trees. Per triangle, the mesh trees cost over 120 times more than the sculpties. Now, I haven't done custom LODs for that tree yet, so maybe that's skewing things. As is, however, I view this as a broken system. In addition to making mesh less usable, with all the problems attendent in that (an uglier SL, frustrated creators, etc.), it sets up perverse incentives. To get back to my tree example, in terms of load on the viewer's computer, the mesh trees are over four times more efficient. The PE doesn't reflect this, however, and in fact heavily favors the sculpted trees. Even if I'm being an especially conscientous builder and decide to take the prim hit in exchange for a less laggy build, most people won't do that, either out of preference, necessity, or ignorance. A properly done mesh build will run much better on an older computer than an identical one made of sculpties, but how many of those are there going to be if mesh is so much more expensive than sculpties?
  3. How disappointing. I was away from SL for... what, nearly two years now, and mesh tempted me back. I've been messing around in Blender the past few days. And now I find that PE makes it effectively unusable? Sigh. Look, I know meshes have a streaming cost higher than sculpties and especially prims. Making them cost a bit more than sculpties or regular prims? Okay, fine. I won't say I like it, considering the savings you can get in polygons and texture sizes, but it's not unreasonable. Twenty times more is not "a bit." 125 times more is definitely not "a bit." Why even bother developing mesh if it's going to be so costly, PE wise?
×
×
  • Create New...