Talk:Second Life 2.0

Avatar is bigger than a normal human / SL 1.0 "meter" does not equal a real world meter

The standard avatar height does not match the size of average humans, in the measurement units used by the virtual world. The default avatar height is about 25% larger than a normal human. This may seems a small problem, but it affects the design of everything else in the virtual space.

Because all in-world objects have been built slightly larger than normal to compensate for the oversize avatar, this means the in-world measurement system cannot be used to accurately duplicate real-life objects; the resulting object is too small compared to the typical avatar. A house built using actual real-world measurements would be slightly too small compared to the avatar.

Due to this minor early design flaw of the avatar, the in-world definition of "meters" is meaningless. It would be better to stop calling them meters and use another SL-specific term (such as the "munge"), so that people don't confuse it with correct real-world measurements.

This isn't a bug or a design flaw. It's a social problem. People choose to have larger then average avatars which led to the average SL avatar being larger. Buildings were consequently made larger to compensate for peoples tastes in larger then average avatars. This isn't a technical problem. -- Strife Onizuka 12:26, 5 April 2008 (PDT)

Why would the people who started building in SL have chosen a "larger than normal" avatar? There is no reason for it. Space and distance means almost nothing in a virtual environment where nothing else exists as an initial reference point.

Assume you start in a sim with nothing but flat ground and an avatar. Set the avatar to the default male or female shape and begin building. If you follow the rules of normal meters, centimeters, etc, you soon discover that the avatar much bigger than the objects for some reason. It may not occur to people to shrink the avatar to fit, especially since it is the default size and shape as devised by Linden Lab. So instead they resize the objects to fit the avatar.

Regardless, this is a legacy problem that should never have been allowed to get this far since the measurement system is mostly useless for anything requiring real-world to virtual-world design precision.

Scalar Tardis 15:29, 5 April 2008 (PDT)

A few different responses I had to this.

• I don't dispute that it is annoying but it isn't a technical problem.
• The only "solution" to this is a procrustean solution. When it comes to procrustean solutions, they are only popular with those people who are holding the pruning shears.
• Why should a virtual world, where anything is possible, be bound by the limitations of the real world? When it comes to architecture, the design requirements are very different from those of the real world. The buildings can ignore gravity, security concerns & weather; not to mention there needs to be adequate space for the 3rd person camera to move around. You don't need bathrooms, closets, kitchens or even walls. In a world where the requirements and limitations of biology are nonexistent, it goes without saying that content that depends on those limitations will look out of place; they don't translate well.
• Depending upon the region of the world average human height can differer quiet dramatically. People will always use the avatar as a ruler but because differing preconceived notions about average height they will generate content to differing scales. There will always be content of differing scales.
• If you are to pick a new SL average/default size, how do we go about choose it? Regional average height can vary as much as 15% of the total height. Considering such a large variance it seem impossible to choose a single solution that fits all the preconceived ideas about average height.  Human_height
• The psychological aspect of this is something that could be very interesting to study.

-- Strife Onizuka 18:17, 5 April 2008 (PDT)

Visual object size doesn't match physical size

Physical and visual sizes don't match because of the problems inherit with detecting collisions of small objects moving at high speeds. The math looks something like: Probability = (A.Size + B.Size + buffer_size) * FPS / |A.Velocity - B.Velocity|. If you halve the buffer_size, then to maintain the same Probability you must either half the max velocity, double the min size, or double the FPS. If you remove buffer_size altogether the changes required are much more drastic. To put things simply, you cannot simulate physics in real time perfectly, you have to cut corners. This is SVC-1139. -- Strife Onizuka 12:26, 5 April 2008 (PDT)