1  |   Order by default

Feb 9, 2001, 5:53pm

Alright...

Yup it's me again... stepping in to solve an argument.

This is how it works - a reflectivity code native to the browser and
renderware environment would probably use Direct X 7.0 and OpenGL code... It
would also require that the world in which it is used has a defined border
to calculate what it is reflecting based on it's position.

So.. what does this mean for AW in codeing?

Roughly, it means that the worlds in the AW Universe need defined borders
for the ends of the worlds as well as AW doing a bit of studying into OpenGL
and Direct X coding.

While they're at it, AW could even make the ends of the worlds, (defined)
render the connecting land from the opposite side of the map so that the
worlds are really spherical... maybe.

The idea is that AW needs to actually sit down and get creative...
Reflectivity (mirrors) are a business addition because it makes things more
realistic (which is the point isn't it?) from a subtle reflection in a
window or water to a full length mirror... it's the small things that trick
the user into thinking it's realistic.

The more realistically a product is shown in 3D the more a user will think
it's serious and not just a "chat environment". Believe it or not AW as a
program is much more powerful than people know... it just takes the right
talent to bring out the best in it :)

1  |   Order by default